A commissioning pass is not the same as operational readiness.
Owners still carry RFS governance risk after Cx. IST and failover evidence, L0–L6 review, customer acceptance, MOP/EOP/SCP procedures, and CMMS/DCIM handover must all be governed before a hall goes ready-for-service — and stabilized after.
Everything an RFS has to coordinate.
One Readiness Room spans every workstream that must be true before a ready-for-service decision — each with owners, criteria, and accepted evidence.
Hall / pod / rack readiness
Campus, building, hall, pod, and rack readiness.
IST & failover evidence
Integrated systems test and failover outcomes.
Customer & tenant acceptance
Customer acceptance recorded against criteria.
MOP/EOP/SCP procedures
Methods, emergency, and contingency procedures.
CMMS / DCIM handover
Asset and monitoring handover to operations.
Spatial readiness
Spatial, security, and access readiness.
Staffing & training
Operations staffing and competency.
Post-RFS stabilization
Stabilization tracking after ready-for-service.
Three kinds of gate. One RFS decision.
A ready-for-service decision depends on distinct authorities. CitiriOS keeps the RFS board, regulatory evidence, and customer acceptance separate and traceable.
RFS board
The owner RFS board governs readiness of halls and pods against L0–L6 evidence and IST outcomes.
Beneficial use / AHJ
Occupancy and regulatory evidence — statutory, cannot be overridden by the owner.
Customer / tenant acceptance
Contractual acceptance recorded against criteria, with residual conditions.
The same platform — in RFS language.
Every CitiriOS module maps to how data center owners run an RFS.
Readiness Room
Every workstream, stakeholder, trial, issue, dependency, and gate for an RFS.
Ready Score
RFS readiness index by domain, with what is dragging it down.
Evidence Packs
Audit-ready RFS packages and L0–L6 evidence for customers and the RFS board.
Gate Authority
RFS, regulatory, and customer acceptance gates kept distinct and evidence-backed.
Dependency Graph
Power / cooling dependencies, change windows, and customer RFS windows made explicit.
Handover & Acceptance
CMMS / DCIM handover, conditions, and post-RFS stabilization to D+90.
Fit across RFS types.
Wholesale colocation RFS
Full RFS governance across halls, IST, and customer acceptance.
AI / HPC hall readiness
High-density power / cooling readiness and failover evidence.
Live power / cooling upgrade
Change-window governance with live-load interfaces.
Liquid-cooling retrofit
Procedure, spatial, and IST readiness for new cooling.
Tenant fit-out acceptance
Contractual acceptance and MOP/EOP/SCP readiness.
Another event type?
Configure a Readiness RoomWhen RFS is governed as evidence rather than status, owners aim to hit the RFS date, close IST issues faster, and record customer acceptance with a defensible package.
Outcome figures are shown as target use cases. Published proof carries an internal source, date, method, and approval record.
Assess your RFS governance before the next hall goes live.
Set up a working demo around your colocation, AI/HPC, or upgrade RFS — with IST, L0–L6 evidence, and customer acceptance loaded in.