Handover readiness, from the operate side
An assessment of the systems as built against what an operator needs to run them, producing the list of what has to be fixed, documented or owned before the contractors leave, or after they have.
Industries
Technology for infrastructure programmes in Saudi Arabia
A large development is built by contractors on a construction timetable and operated by an owner for decades. The technology inside it — connectivity, cameras, operations platforms, the systems that tie a site together — changes hands at handover, and that handover is where most of it stops working as designed. This page is for the programme role that owns the operate phase.
Sector guide Published 6 min read
01The terrain
Built on one timetable, operated on another
The technology in a large development is procured as part of construction: packaged into contracts, delivered against practical completion, and signed off when it works on the day. Then the contractors leave, and an operations organisation that did not specify the systems inherits them, along with the documentation the contract required and no more, the credentials someone remembered to hand over, and a support arrangement that expires with the defects period.
The gap is not the technology. It is that build-phase contracts are written to deliver a working system and operate-phase organisations need a runnable one, and those are different things: a runnable system has an owner per component, runbooks written from the system as built, monitoring that reaches a person, an upgrade path, and a way to change it without the original contractor. This page is about closing that gap, ideally before handover and honestly after it.
02Two phases
What the build phase delivers, and what the operate phase needs
The same system, seen from each side of handover. The right column is the operate-phase owner’s checklist, and every row of it can be written into the build-phase contract if someone is there to write it.
| System | What the build contract delivers | What the operate phase needs |
|---|---|---|
| Connectivity devices | Devices installed and working at completion, from whichever vendor the contract named | A supply line for replacements and expansion that does not depend on an import lead time. Interkey Semiconductor assembles CPE, ONT and related devices in Riyadh; the manufacturing page states what it builds today. |
| Camera estates | Cameras installed and recording, usually to a video management system chosen by the security package | An estate that does something: safety and zone monitoring on the cameras already installed, with a survey that says which views are usable and processing that stays on site. |
| Operations platforms | Building and site management systems, each with its own console, commissioned by its own contractor | One observability layer across them, so the operations team sees the estate rather than fifteen consoles, kept in-Kingdom, with alerts that reach a named person. |
| The joins between systems | Interfaces the contracts required, built by whichever party was nearer, documented to the contract’s standard | An interface inventory with an owner per row, produced from the systems as built, and the interfaces nobody can explain rebuilt on something a current engineer can maintain. |
| Custom applications | Portals, resident or tenant services and operational tools, delivered to the specification of the day | Source, artefacts and documentation owned by the operator, and a team in Riyadh that can change them in Arabic and English without the original contractor. |
| Operation itself | A defects-liability period and a support contract that expires | A named operator for every platform in year three: the owner’s own team with runbooks, or a managed service on an agreed scope with a defined way back in-house. |
03What Interkey brings
The capabilities behind the table
A device supply line inside the Kingdom
Connectivity devices assembled in Riyadh for the expansion and replacement a development needs for decades, on a quote per programme.
Platforms operated, or handed over runnable
The observability, integration and application layers operated on an agreed scope from Riyadh, or handed to the owner’s team with runbooks written from the systems as built.
04The order
How a handover becomes an operation
The sequence works before completion, when it is cheapest, and after it, when it is necessary. What changes is only how much of step one is a surprise.
-
Inventory the systems as built
Every platform, device estate and interface that exists, whoever installed it, with its documentation, credentials and support status recorded honestly. This list is usually longer and worse than the contracts suggest.
-
Assess against the operate checklist
Each system against the right column of the table above: owner, runbook, monitoring, upgrade path, changeability. The output is the remediation list and its price.
-
Remediate and document
The urgent items fixed, the runbooks written from the systems rather than from memory, and the interfaces nobody can explain either documented or rebuilt.
-
Name the operator and start
A named operator per platform, the change and incident process live, and the review cadence that keeps the inventory true as the development grows.
Not a technology list, and not a programme reference
This page does not enumerate the technologies a development could contain, and it names no development, developer or authority. The buying question it answers is narrow on purpose: when the contractors leave, who runs what they built, and was it built to be run. A programme whose question is different — which technologies to specify in the first place, say — is served by the practice pages directly, and the solutions index routes to them.
05Cheapest before completion
Writing the operate phase into the build contracts
Everything in the right column of the table can be a contractual deliverable if someone on the owner’s side is asking for it while the packages are being written: runbooks to a stated standard, an interface register as a completion document, monitoring integrated before sign-off, credentials handed over through a process rather than a spreadsheet. The cost of asking is small. The cost of not asking is the remediation list in step three.
Interkey’s role at that stage is the operate-phase reviewer: reading the technology packages from the side that will have to run them, and saying which deliverables are missing. It is a short engagement and it changes the contracts rather than the buildings.
Inheriting the technology of a development, or writing the contracts that will deliver it? Interkey assesses systems from the side that has to run them, and operates what it takes on, 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.
Can Interkey take over systems it did not build?
Where they are technologies Interkey implements, yes, after the assessment and remediation the sequence above describes. The assessment is not a formality: systems inherited at handover routinely arrive with expired support, no tested restore and monitoring that alerts nobody, and taking them into service in that state would be taking on an outage. The remediation is priced separately because its size is not known until the inventory is honest.
Is it too late if practical completion has already happened?
No, only more expensive. The sequence is the same after completion; what changes is that the inventory holds more surprises and the remediation is paid by the owner rather than written into a package. Starting now is cheaper than starting after the defects period ends and the contractor’s obligation with it.
Does this page cover which technologies a development should specify?
No, deliberately. That question is answered by the practice pages for each technology, and the solutions index routes to them. This page is about the handover of whatever was specified, which is a different buyer with a different problem.
Will Interkey name programmes it has worked on?
Not on this site. References are given in conversation with the counterparty’s consent. A sector page naming developments it has not cleared would be claiming something it has no right to claim.
From the insights library
Read next for this sector
Practice
Managed services
Operating platforms on an agreed scope, including the assessment that comes first for platforms Interkey did not build.
PracticeSystem integration
The interface inventory and the ownership problem, which is most of what a handover leaves behind.
ProductNetwork equipment manufacturing in Saudi Arabia
The device families assembled in Riyadh and the commercial model, for the replacement and expansion a development needs.
Solutions for this sector
Next step
Start with the inventory
Say where the programme is, before or after completion, and which systems worry the operations team most. The assessment starts from that list.
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