From structured cabling to enterprise networks — Convergent's IT Infrastructure Business Unit builds the connective tissue Saudi enterprises and government operations rely on.
PREVIEW MEDIA — REPLACEMENT REQUIRED. Controlled preview asset from the CT design pack. Not a photograph of a Convergent premises or project.
Cabling, network, security and operations are usually bought separately, from different suppliers, at different times. Each part performs. The estate as a whole does not.
An enterprise is not one site. It is a core, a campus, a set of branches, a set of operational locations that were never designed for IT, and a growing share of services that are not on any of them. The architecture has to be the same everywhere, or the exceptions become the estate.
Where compute, storage and the estate’s routing core sit. Everything else is measured by how reliably and how quickly it reaches this.
Dense wired and wireless coverage, floor distribution, unified communications, and the access layer most of the workforce actually touches every day.
Smaller footprints on the same architecture and the same security model, so a branch is not a separate estate running its own rules and its own exceptions.
Plant rooms, yards, remote facilities. Environmentally harder, often reached over fibre or wireless, and frequently carrying operational rather than office traffic.
Hybrid connectivity into cloud platforms and third-party services, sized, routed and secured as part of the estate rather than treated as an exception to it.
The Group standard applied to infrastructure work, scaled to the requirement. Scope boundaries are written down before anything is installed.
Current-state review: the existing cabling and network estate, traffic and capacity, security posture, and the operating constraints the environment imposes.
Current-state and requirements record
Architecture and security design developed against the relevant standards, with addressing, segmentation and resilience decided rather than inherited.
Design package and addressing plan
Cabling, active infrastructure, security and facilities scopes sequenced together, so cutover windows and dependencies are agreed in advance.
Programme and cutover plan
Installation, configuration, integration and testing of the agreed scope, with acceptance testing witnessed before service transition.
Test results and as-built records
Monitoring, incident response and capacity planning under the contracted coverage and service model.
Service model and reporting
This Business Unit is organised around seven technology domains. A project usually takes several of them; the value is that they are designed against one another rather than procured against one another.
Most infrastructure work happens on an estate that is already carrying production. The method is chosen per workload rather than for the project as a whole, and the cutover window is agreed before anything is touched.
The workload stays where it is and the platform beneath it changes. Lowest disruption, highest dependency on the current environment being accurately documented first.
The workload moves unchanged to new infrastructure. Fast, predictable, and appropriate where the application cannot be modified inside the programme’s window.
Data moved with consistency and rollback proved before cutover, and a defined position on what happens to transactions in flight.
Volumes relocated between platforms with performance and protection levels preserved, and the restore path tested rather than assumed.
The application is re-platformed with its integrations mapped first, because the integrations are what actually break on cutover night.
Equipment physically moved between rooms or sites, sequenced so the estate is never dependent on something that is currently on a truck.
Resilience is a design position taken deliberately, with a stated recovery expectation, and then tested. Otherwise it is an assumption that gets checked for the first time during an incident.
The failure modes that would actually interrupt the business, identified against the estate as built rather than as originally drawn.
Protection levels set per workload, with the restore path exercised so recovery time is a measured figure rather than a hope.
Redundant paths and failover mechanisms designed where the business case supports them, and proved by inducing the failure they exist for.
A written continuity position covering who decides, who is told, and what the estate falls back to — reviewed rather than filed.
Convergent’s Business Units meet inside the same buildings and on the same cabling. These are the seams that matter most often, and how each one is handled.
Active network, compute, storage, virtualisation and infrastructure security inside the room.
The room itself — power, cooling, containment, detection and facility monitoring.
How the seam is closedOne drawing set and a joint commissioning position for the space.
The network the systems run on, quality-of-service design, and the unified communications platform.
Room systems, displays, control and the experience inside the space.
How the seam is closedBandwidth, addressing and control-network requirements agreed at design.
Permanent infrastructure and connectivity at the venue.
Temporary production systems and live technical operation.
How the seam is closedA defined handover point between permanent estate and event installation.
Infrastructure design, delivery and the agreed operational scope.
Applications, data ownership and security policy.
How the seam is closedA written responsibility matrix issued before installation begins.
Tell us what you are planning, where the scope sits and the outcome that matters. Your enquiry is directed to the Business Unit that owns that field, and you deal with that team directly.
Most engagements are led by a single Business Unit working directly in its field. Where a requirement genuinely crosses disciplines, the Group coordinates the points where those specialist scopes meet, without diluting the expertise behind each one.
ISO 9001:2015, ISO/IEC 27001:2022, ISO 37001:2016 and ISO 45001:2018, within the certified scope of Data Centre Solutions and Services. The certified scope is stated on every page where the standards appear.
A consistent approach across every Business Unit, scaled to the requirement: understand the environment and constraints, engineer against the relevant standards, coordinate where specialist scopes meet, deliver and commission the agreed scope, then support it to the contracted model.
Company facts, capabilities and certified management systems are assembled for procurement officers and evaluation teams, with a controlled prequalification pack available on request through the Evaluation Center.
ISO 9001:2015, ISO/IEC 27001:2022, ISO 37001:2016 and ISO 45001:2018, within the certified scope of Data Centre Solutions and Services.
| Standard | Subject | Certified scope |
|---|---|---|
| ISO 9001:2015 | Quality management | Data Centre Solutions and Services |
| ISO/IEC 27001:2022 | Information security | Data Centre Solutions and Services |
| ISO 37001:2016 | Anti-bribery management | Data Centre Solutions and Services |
| ISO 45001:2018 | Occupational health and safety | Data Centre Solutions and Services |
Convergent's IT Infrastructure team works with CIOs, IT directors, and procurement teams from network design through commissioning to ongoing operations.
