A campus is a power plant, a cooling plant, a secure facility, a production network and a written promise to customers at the same time. Physical, cyber, environmental, contractor and grid risk all act on the same halls, and each one is watched by a different team on a different console.
One night shift at a colocation campus. Every system does exactly what it was bought to do, and every operator follows the procedure correctly.
The shift engineer files it against the open change record.
Filed to changeThe service desk confirms the customer signed it and books the escort.
Escort bookedAccess control grants both and security notes the anomaly for the morning report.
Logged for reviewThree teams, three queues, three correct procedures. The building management authentication log, the ticketing system and the access control record do not talk to each other, and nothing on the campus is responsible for the line that runs through all three. By the morning report the three items are read out separately, if they are read out at all. The pattern was never the problem. Ownership of the pattern was.
The same six domains resolve onto every estate. This is what they are when the estate is a data center campus.
Production, customer and out-of-band networks, alongside the building management and infrastructure management systems and the controllers under chillers, air handling, switchgear, UPS and generators. A plant alarm and a network alert are the same story more often than either console can tell.
Perimeter detection and cameras, lobby and visitor processing, mantrap and turnstile records, cage and cabinet access, and the badge record that says who was in which hall and when.
A track over the cooling plant, the generator yard or the fiber entry is a survey rather than a nuisance. Detection is the straightforward part. Deciding what the track means next to a badge event or an open maintenance window is not.
Escorted contractors, integrator remote sessions, inbound equipment and spares, and the firmware that arrives inside them. Access and supply are the same exposure viewed from two directions.
Utility and grid conditions, fuel held on site, heat and humidity in the hall, and storms or flooding on the roads that carry fuel and staff. That is one event acting on availability, not several unrelated tickets.
Where the campus sits, who its tenants are, the regime it reports incidents under, and the reporting that changes what a routine indicator means for one customer and not for another.
The same event matters differently on the floor, at the security desk and in front of a customer. One object, delivered at each altitude, with the clock that altitude actually runs on.
What changed in the power and cooling chain and on the floor in the last hour, and what to watch for the rest of this shift.
The ranked picture across domains, the converging set behind each item, and the option set with an owner attached, including who can stop an escorted visit.
What is being worked, what posture is recommended and why, and what the recommendation rests on if a customer or a regulator asks later.
Comparable exposure across sites, ranked by policy that was ratified rather than inferred by a vendor, in terms a customer commitment can be answered in.
Nothing here assumes a complete estate or a rip and replace. Sources are added as adapters against a common contract, and the score states the coverage it was computed on.
Onboarding is four things, in order.
Build the asset model for the campus, so a signal has something to attach to: halls, cages, cooling loops, the power chain and the systems behind them. Connect what exists and state what does not. Ratify the policy: the weights, thresholds and windows that decide what outranks what, signed by a named person rather than shipped as a default. Then run it against real traffic and compare the queue to the judgment of the people who already do this work.
Where a feed does not exist, coverage is disclosed on the object instead of the gap being quietly absorbed into a number.
We walk one real convergence case from your campus, and we name what is built, what is specified, and what is neither.