RFS Readiness Workbench — Methodology & Formulas

01 Purpose & engineering basis

The RFS Readiness Workbench is a gate-based commissioning audit tool for data center Ready-for-Service planning. It answers three operational questions: which commissioning gate each delivery unit currently holds, what evidence gaps and open defects are blocking the next gate, and when the project will reach RFS given the current defect and evidence load.

The methodology is user-driven: the operator configures delivery units, selects a facility archetype, ticks completed requirements, and logs defects. The engine returns a deterministic gate status, weighted readiness percentage, 7-term confidence score, and multi-component forecast for every unit — and a worst-case project RFS date. Gate definitions follow Uptime Institute commissioning level practice (L1 design through L5 IST/performance) and TIA-942 commissioning stages. Signoff matrices reference industry-standard roles (Cx Lead, Ops Lead, Customer Witness, Project Director).

02 Inputs

Three input categories — project configuration, per-gate evidence, and defect register — drive all engine outputs. Delivery units are user-defined (data halls, electrical blocks, mechanical plant, pods, campus infrastructure). The archetype selection controls gate-day multipliers in the forecast engine.

03 Calculation methodology

Four sequential calculations inside RfsGateEngine.evaluateGate(gateCode, unit) and RfsForecastEngine.forecastUnit(unit). Function names and source locations are given exactly as they appear in the inline script of rfs-readiness-workbench.html.

Gate readiness %

Two caps prevent a fully-evidenced but incomplete gate from showing 100%:

Gate status determination

Gate confidence % (7-penalty model)

RFS forecast engine — 7-component drag model

Checklist overall readiness grade

04 Constants & data sources

All constants live in RfsLibrary (deep-frozen object, inline in the page). Gate definitions (GATE_NAMES, GATE_BASE_DAYS, SIGNOFF_MATRIX) and severity thresholds (AGING_THRESHOLDS) are reproduced in full below.

Item weight tiers: W3 = weight 10 (hard, safety-critical — arc flash study, NETA energization, EPO test, customer acceptance); W2 = weight 7–9 (significant — FAT reports, performance tests, SOPs); W1 = weight 1–6 (informational/soft — design approvals, minor ancillary checks). Evidence source classes A–D indicate primary/independent testing (A) through secondary/unverified information (D); source class feeds the overlay uncertainty drag in the forecast engine.

05 Outputs

06 Worked example

Single unit "Data Hall 1", gate G3 (Startup & Individual Testing). Gate has 9 baseline requirements with a total weight of 78. Scenario: 5 requirements evidenced (W = 10+10+10+10+8 = 48), 1 open Critical defect, 1 open Major defect, 1 overdue Moderate defect (age 22 d), 1 pending sign-off role, 2 unconfirmed overlays (source B, hard). Trace every number against the inline scoring.

07 References & standards

• Uptime Institute (2021) — Data Center Commissioning and Verification: L1 design review through L5 integrated systems test methodology; stage-gate progression discipline; Cx team qualification standards.
• TIA-942-B (2017) — Telecommunications Infrastructure Standard for Data Centers: commissioning plan requirements, documentation package, tiered reliability basis for gate test scope.
• NETA MTS-2019 — Maintenance Testing Specifications for Electrical Power Equipment and Systems: acceptance testing procedures referenced for G3 energization requirements (MV switchgear, transformers, UPS, batteries).
• IEEE 1584 (2018) — Guide for Performing Arc Flash Hazard Calculations: basis for G1 arc flash study requirement (req_g1_001).
• NFPA 72 (2022) — National Fire Alarm and Signaling Code: fire detection commissioning requirements (G3 req_g3_008, G4 req_g4_005 EPO interlock).
• NFPA 2001 / NFPA 855 — Clean Agent Suppression and ESS: fire suppression design approval (G1 req_g1_007) and discharge test (G4 req_g4_004) basis.
• ASHRAE TC 9.9 (2021) — Data Center Power Equipment Thermal Guidelines: cooling performance test criteria for G3–G5 mechanical requirements.
• ISO 55001 (2014) — Asset Management: spare parts strategy, maintenance contract completeness, and CMMS operational readiness (G6 requirements).
• Project stage-gate practice — Stage-Gate® process (R.G. Cooper): phase-gate decision points with defined exit criteria, mandatory sign-off, and blocker classification (hard/soft) logic.
• Engine source — RfsLibrary, RfsGateEngine, RfsForecastEngine (inline JS in rfs-readiness-workbench.html). No external engine file — all logic is self-contained in the page.

08 Assumptions & limitations

Gate base-day durations (GATE_BASE_DAYS) are representative industry benchmarks for a well-resourced medium-sized data center build; they are not contractually binding schedules. The archetype multipliers are calibrated estimates — actual schedule must be confirmed against the project programme. The forecast is additive and optimistic in that drag terms do not account for parallel resolution of multiple issues; resolving a Critical defect simultaneously with a sign-off chase could reduce totalDays less than the formula implies. Evidence acceptance is user-asserted: the workbench trusts the operator's judgment on whether an uploaded document genuinely satisfies the requirement criteria — it does not parse documents. Defect closure is likewise operator-driven. This workbench is an engineering planning and audit aid; final RFS determination requires a qualified commissioning manager sign-off and, where applicable, customer and authority acceptance under the contract.