Safety monitoring as a rollout, not a pilot
The detection product is SquintPRO, Interkey’s own; the programme work is the survey standard, the site order, and the alert workflow that lands in each control room the same way.
Industries
Technology for manufacturing and industry in Saudi Arabia
A single plant can pilot almost anything. A manufacturer with several sites has a different problem: running the same technology across all of them, on systems that were installed at different times by different contractors, without a control room at each one. This page is written for the group role that owns that problem.
Sector guide Published 6 min read
01The terrain
One plant is a pilot; several plants are a programme
Most industrial technology on this site is described at the level of one site: the cameras a plant already owns, the systems it already runs, the control room it already staffs. The industrial safety practice is written that way on purpose, because detection is proved one site at a time. This page starts where that one ends: a manufacturer with three, eight or twenty sites, a group operations or IT role accountable for all of them, and the question of what can run across the estate rather than at the plant that happened to pilot it.
The multi-site problem has a shape. Each site has its own systems, installed by whoever built or last upgraded it, and its own boundary between the operational technology that runs the process and the information technology that runs the business. A programme that ignores that boundary is stopped by the plant engineer, correctly. A programme that respects it has to be designed twice: once for the group, once for each site’s reality.
Interkey works on both levels, and it also operates a production facility of its own in Riyadh through Interkey Semiconductor, which is not a reference but is a reason the questions on this page are asked from the plant floor’s side as well as the group’s.
02Two levels
What the site needs, and what the group needs
The same capability looks different from the plant and from head office. A programme that only answers one column is either a pilot that will not scale or a mandate the sites will quietly ignore.
| Capability | What the site needs | What the group needs |
|---|---|---|
| Safety monitoring | A camera survey of its own estate, its own zones and PPE rules, alerts into its own control room. The practice page. | One detection standard, site-by-site rollout in an order that proves it, and leading indicators comparable across plants without a supervisor’s eye deciding the count. |
| Plant systems observed | Its own plant IT — historians, MES, the systems around the line — visible to the people on shift. | The observability practice applied to the estate: one platform, in-Kingdom, with each site’s systems visible to the group without the group touching the process network. |
| Production data | Data that stays where the process runs and reaches the people who need it on site. | A data platform that brings production data together across plants for planning and comparison, with iblync moving the records without the sites re-engineering their systems. |
| The systems that have to talk | Its MES to its maintenance system to the ERP, on interfaces somebody can explain. | Integration as a programme: an inventory of every interface at every site, an owner per row, and the group ERP fed from all of them the same way. |
| Operation afterwards | Someone to call when the platform, not the process, misbehaves. | A managed service on an agreed scope, so the group is not staffing platform operations at every site. |
03What Interkey brings
The capabilities behind the table
Plant IT visible across the estate
One observability platform for the IT around the process at every site, designed to see plant systems without crossing into the process network, and kept in-Kingdom.
Interfaces owned, plant by plant
The integration inventory for a multi-site estate, and the interfaces that feed group systems from every plant on the same contract.
04The order
From one proven site to the estate
The sequence that turns a pilot into a programme. Skipping the second step is how a mandate from head office becomes a system every site works around.
-
Prove it at one site
One site, one capability, success criteria written before it starts, and the honest result. For safety monitoring this is the pilot guide; for platforms it is the same discipline.
-
Write the site standard
What a site has to have for the capability to work there — camera coverage, network reachability, the OT/IT boundary respected — so the next site can be assessed against a list rather than re-piloted.
-
Sequence the estate
Sites ordered by readiness against the standard and by value, with the ones that need physical work scheduled into their own maintenance windows.
-
Operate as one platform
Every site on the same platform, observed the same way, with a named operator for the platform layer and the site keeping authority over its process and its safety response.
The process network is not touched, and the page says so plainly
Everything on this page runs on the IT side of the boundary or reads across it in one direction: cameras as network streams, plant systems as sources of telemetry, historians as sources of data. Nothing here writes to a control system, replaces a safety-instrumented function, or asks the plant engineer to open the process network to a group platform. A programme that needs any of those is a different programme with a different risk owner, and it should be described as one.
05Authority
What stays the site’s, whatever the group buys
A multi-site programme succeeds when the sites want it, and they want it when it does not take their authority away. The group can own the platform, the standard and the comparison across plants. The site keeps the definition of what matters on its floor, the response when an alert fires, and the authority over its process that no technology vendor can hold for it.
Interkey’s role sits between the two: implementing the platform layer to the group’s standard, tuning it to each site’s reality, and operating it afterwards on the Saudi working week from Riyadh, in Arabic and English, for the shifts that actually use it.
Accountable for technology across several plants and tired of pilots that never leave the first site? Interkey writes the site standard, sequences the estate and operates the platform layer from Riyadh.
06Buyer questions
What buyers ask us
Direct answers to the questions that come up in real evaluations. Anything missing, ask us at the bottom of the page.
How is this different from the industrial safety page?
That page is about detection on one site: what cameras can see, how a pilot is scoped, what the product does. This page is about running a capability across several sites as one programme, of which safety monitoring is one case. If the question is “can our cameras do this”, start there; if it is “how do we do this at every plant”, start here.
Does any of this touch the control system?
No. Everything described runs on the IT side of the OT/IT boundary or reads across it in one direction. Nothing writes to a control system or replaces a safety-instrumented function, and a programme that needs to is a different programme with a different risk owner.
Can sites with different systems be brought onto one platform?
That is the normal case, and it is why the site standard exists: it says what a site has to have for the capability to work, rather than which vendor installed it. Sites are assessed against the standard, sequenced by readiness, and the integration inventory carries each site’s interfaces on their own terms.
Does Interkey publish what it has done for other manufacturers?
Not on this site. References are given in conversation with the counterparty’s consent. The group does operate a production facility of its own in Riyadh, which is stated as a fact about Interkey and not as a customer reference.
From the insights library
Read next for this sector
Practice
Industrial safety monitoring in Saudi Arabia
Detection on the cameras a site already owns: the single-site half of the programme this page describes.
Sector guideAI safety monitoring for oil and gas sites
The hydrocarbon case: classified areas, permit-to-work verification and contractor workforces.
PracticeData platform modernisation
Bringing production data together across plants, including the case for leaving a site’s systems exactly as they are.
Solutions for this sector
Next step
Start with the site that would go first
Say how many sites, which capability the group wants everywhere, and which site has already piloted something. The standard conversation starts there.
Or directly
+966-11-2180999 info@interkey.com.saTawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia