There is a new quality management standard being written for data centre infrastructure, and it is moving unusually fast. DCE 9000 went from working group to first unified draft in nine months. Release 1.0 is scheduled for Q1 2027. Most standards take three to five years.
If you manufacture, integrate, install, commission or maintain power, cooling or mechanical systems for data centres, this is the standard your customers will eventually ask you about. It is worth understanding now, while there is still time to prepare rather than react.
What DCE 9000 is
DCE 9000 is a quality management system standard for data centre physical infrastructure — power, cooling and mechanical systems — developed by the Telecommunications Industry Association (TIA) through the TIA QuEST Forum.
It covers organisations that design, manufacture, build, integrate, install, commission, operate, maintain or support that infrastructure. In practice: equipment manufacturers, their key suppliers, system integrators and installers.
The participant list is the part worth noticing. Google, Amazon Web Services, Oracle, QTS, Schneider Electric and Johnson Controls are named among more than 70 participating organisations. That is a standard being written by the people who buy, not only by the people who sell — which historically determines whether a sector standard gets adopted or ignored.
Where it comes from, and why that tells you a lot
DCE 9000 is built on ISO 9001 and organised using the ISO Harmonized Structure, with acknowledged influence from TL 9000, IATF 16949 and AS9100.
That lineage is not decoration. Each of those is a sector standard that took ISO 9001 and added what a particular supply chain actually needed:
- TL 9000 added required performance measurements — telecoms buyers wanted comparable data across suppliers, not just a certificate.
- IATF 16949 added core tools, supplier development and a much harder line on customer-specific requirements.
- AS9100 added configuration management, counterfeit-part control and first-article inspection.
The strongest signal about what DCE 9000 will demand is that the working group has a dedicated Measurements Sub-Team, alongside four technical teams, a Code of Practice Sub-Team and a Training Sub-Team. A measurements sub-team is the TL 9000 pattern, and TL 9000's defining feature is that certification requires you to submit defined performance data, not merely to hold a certificate.
If that carries across — and the structure suggests it will — then DCE 9000 will be a data standard as much as a documentation standard. That is a different kind of preparation from an ISO 9001 gap assessment, and it takes longer, because you cannot retrospectively generate twelve months of measurement history.
Why a new standard at all
The stated gap is a lifecycle quality framework that existing standards do not cover. A data centre is assembled from equipment made by many manufacturers, integrated by others, installed by others again and maintained by someone else entirely — and failures tend to appear at the handovers rather than inside any one supplier's scope.
An ISO 9001 certificate tells a hyperscale buyer that a supplier has a quality management system. It does not tell them whether that supplier's equipment performs consistently across sites, whether their installation practice is repeatable, or how they compare to the alternative. At the scale data centres are now being built, that difference matters commercially.
The other stated aim is reducing redundant audits. If you supply several hyperscalers today, you are likely audited separately by each, against overlapping but non-identical expectations. A common scheme is a plausible answer to that, and it is usually the argument that persuades suppliers a new standard is worth having.
Who is actually writing it
Unusually for a standard in development, the working group structure is public — and it tells you more about the likely content than any announcement does.
The group is chaired by Gino Tozzi, Global Head of Data Center Quality at Google, and the drafting is split across four teams that map onto the Harmonized Structure:
- Team A — Context, Leadership, Planning and Support. Led by Vijai Venkata, Quality Director for DC Americas at Modine.
- Team B — Design, Development and External Processes. Led by Jennifer Stepniowski of Johnson Controls, covering supplier qualification, design change management and external provider controls.
- Team C — Operations, Delivery and Installation. Led by Joseph Waggoner, QMS Audit Lead at Trane Technologies CHVAC Americas, covering production controls, commissioning, testing and field quality.
- Team D — Performance Evaluation and Continual Improvement. Co-led by Govind Ramu of Google and Chad Kymal of Omnex.
- Measurements Sub-team. Also led by Govind Ramu, tasked with establishing a consistent industry-wide approach to quality metrics.
Two things stand out.
First, the same person leads both performance evaluation and measurements. Govind Ramu is a Senior Technical Program Manager for AI Infrastructure at Google and heads both Team D and the Measurements Sub-team. When the clauses covering performance evaluation, internal audit, management review and continual improvement are drafted by the person also defining industry-wide quality metrics, the two will be connected rather than parallel. That is the clearest available signal that measurement will be structural rather than advisory.
Second, Chad Kymal of Omnex co-leading Team D is a strong hint about inheritance. Omnex's work is rooted in automotive quality and IATF 16949 — core tools, measurement systems analysis, supplier development. A sector standard whose performance-evaluation clauses are co-written from that tradition tends to ask for evidence of capability, not just records of activity.
Team leadership is also split across buyers and suppliers — Google on one side, Modine, Johnson Controls and Trane on the other. Standards written only by buyers tend to be unimplementable; ones written only by suppliers tend to be undemanding. That split is a reasonable sign of a workable outcome.
The timeline
- January 2026 — DCE 9000 Working Group launched
- September 2026 — first unified draft completed; workgroup met in Nashville on 16–17 September to review it
- Now — draft under refinement ahead of a formal comment cycle open to eligible QuEST Forum organisations
- Q1 2027 — Release 1.0 scheduled
- 2027 — full certification framework, with the Code of Practice Sub-Team defining the certification scheme and auditor competencies, and training courses in development
Note what that means practically: there is nothing to certify to yet, and anyone offering you DCE 9000 certification today is selling something that does not exist. The scheme itself is still being written.
What to actually do now
For most suppliers the honest answer is: not much, yet. But three things are worth doing in the next few months, and all of them are useful whether or not DCE 9000 affects you.
1. Find out whether you are in scope. Power, cooling and mechanical infrastructure is the initial scope. If you supply components into those systems rather than the systems themselves, you may be in scope as a key supplier to an equipment manufacturer — which is a question for your customer, not for you to guess.
2. Look at what you measure, not what you document. If the measurements pattern carries over from TL 9000, the constraint will be history rather than process. Field failure rates, on-time delivery, installation rework, warranty returns, time to restore — if you are not capturing those consistently now, you will not have a credible baseline in 2027. This is the single preparation with a real lead time.
3. If you are already certified, you are most of the way there. DCE 9000 is built on ISO 9001 and the Harmonized Structure, so a working ISO 9001 system is the foundation rather than something to be redone. Suppliers already holding TL 9000, IATF 16949 or AS9100 will recognise most of the architecture — sector standards built this way differ in their specific requirements, not in their shape.
And if ISO 9001 is on your horizon anyway, the 2026 edition transition is running at the same time. Doing that work with DCE 9000 in view is cheaper than doing it twice.
Whether to get involved
The draft is going to a formal comment cycle open to eligible QuEST Forum organisations. If you supply this market at any scale, participation is worth considering — not for the standard-writing itself, but because the organisations in the room shape what becomes mandatory, and the ones outside it find out afterwards.
That is the usual pattern with sector standards. IATF 16949 and AS9100 both look the way they do because particular customers were in particular rooms. DCE 9000 is being written by Google, AWS, Oracle and the major infrastructure vendors. If they are your customers, their requirements are being decided now.
The short version
A new sector QMS standard is coming for data centre infrastructure, built on ISO 9001, shaped by TL 9000's measurement thinking, backed by the largest buyers in the market, and arriving in Q1 2027. Nothing is certifiable yet. The one thing worth starting early is measurement history, because that is the only part you cannot assemble quickly when the scheme opens.
Sources
TIA, “DCE 9000 Is Moving Fast Because the Industry Can't Wait” and the TIA QuEST Forum sub-team progress announcement, which is the source for the working group structure and team leads; Quality Digest, “DCE 9000 to Strengthen Quality and Reliability Across Data Center Infrastructure”. Dates and participants are as published by TIA; a standard in development can change, so confirm the current position with TIA before making commitments.