Convergence as an operating discipline, not a delivery milestone
By SCI Editorial ·
Most projects treat convergence as a verification gate. The systems are integrated; the seams are tested; the converged operation is signed off; the project moves on. Then year three arrives and the estate has drifted back into something that looks like a federation of subsystems again.
Why drift happens
- Vendor upgrades land asynchronously and erode the integration assumptions silently.
- Operator turnover means the people who own the converged view rotate out faster than the documentation can be re-internalised.
- Change-control on setpoints and graphics gets delegated downward; the integration spec stops being a live document.
The discipline that holds
Converged estates that stay converged share three patterns: a named operations role that owns the integration spec as a live artefact; a quarterly convergence drill that proves end-to-end behaviour; and a change-control gate that includes integration impact in every BMS / EMS / EPMS update.
“If nobody owns the converged view, the converged view stops existing.”