We describe the mill as certification-ready and never as certified, and the distinction is not modesty. There is no third-party scheme that certifies an in-building AI mill as a product. What exists is a set of regimes, each with its own filing and its own signatory, that together govern whether a ten-kilowatt cabinet may be energised in someone else's room. The mill meets the electrical and fire regime of wherever it stands. India is the first market, so the first checklist we wrote is the Indian one: CEA (Safety) Regulations 2023, the National Building Code, IS 732, IS 2189, BIS CRS and E-Waste EPR. This note lays them out, says what each requires and from whom, says what the mill inherits from none of them, and explains what we do instead.
What certified would have to mean
For a data centre hall, certified usually means one of three things: an Uptime Institute tier certification, conformity to the TIA-942 standard, or ISO 27001 on the operator. All three certify facilities designed as facilities, with their own plant, their own perimeter and their own operations staff. None of them has a category for a self-contained cabinet installed as equipment in a store room of an office building.
So nothing is inherited. Not TIA-942, not Uptime, not ISO 27001. A mill does not get to borrow a certificate from the building it sits in, and it does not become certified because the components inside it carry marks. What it can be is designed, built and filed against every regime that does apply, with the paperwork complete before energisation. That is what certification-ready means when we use it.
Electrical: the CEA route
The Central Electricity Authority (Measures relating to Safety and Electric Supply) Regulations, 2023 govern any installation that takes supply from a licensee. The mill's intake is 415 V three-phase at twenty amps a phase, taken from the board that already feeds the floor with no new connection, so the installation sits inside the same regime as any other fixed load a building adds. Three things follow.
The work is done by a licensed electrical contractor. Every tie-in from the building's board to the mill's socket is carried out by a state-licensed electrical contractor, or under the direct supervision of a person holding a certificate of competency. We do that on every site, at every voltage class, as a matter of policy rather than only where the regulation's own threshold compels it.
An independent Chartered Electrical Safety Engineer inspects each site. Our compliance memo reads the requirement for an independent inspection by a Chartered Electrical Safety Engineer from the proviso to Regulation 33(1). The memo's reading is on file; the regulation is public.
The installation is tested and its report filed before energisation. Every installation is inspected, tested and self-certified before supply commences, with the test report submitted to the Electrical Inspector. Our memo maps the contractor's duty to Regulation 31 and the pre-energisation testing and filing to Regulation 45. The Inspector's own approval is a separate step, required only where the regulations trigger it; where they do not, the filing is the step.
The mill's incoming panel is a type-tested assembly to IS/IEC 61439, tested at a recognised laboratory. That matters for the split described at the end of this note: the panel is qualified once, as a type, and the per-site work is the tie-in and the test.
Fire: the building's NOC
The mill does not get its own fire no-objection certificate. It enters an existing building as equipment under the building's existing fire NOC, and it carries its own smoke detection, clean-agent suppression and an alarm-triggered power cut-off, so the building's fire posture is not weakened by its arrival. Whether adding a piece of equipment amounts to a material alteration that triggers a fresh municipal process is a municipal question, not a national one, and our design assumes the mill is absorbed into the owner's existing fire-compliance cycle rather than starting a new one.
The design reference behind all of this is Part 4 of the National Building Code of India, the fire and life safety part, in its current edition as notified by BIS.
Components: BIS registration, with a date in it
Electronic goods covered by the Ministry of Electronics and Information Technology's compulsory registration order must carry a Bureau of Indian Standards registration under the Compulsory Registration Scheme before they are sold in India. Power supplies and the IT equipment inside the mill fall under it.
The scheme is in the middle of a migration. Two legacy safety standards have governed registration, IS 13252 Part 1 for IT equipment and IS 616 for audio and video equipment. BIS is moving the scheme to IS/IEC 62368-1:2023, and the legacy standards run alongside the new one until 1 November 2028, after which they are withdrawn and a registration held only against them stops counting.
For a mill that means two things. The build sheet is checked against the live standard on every build, not against the standard that was current when the module was designed. And every component registration in the module library carries its expiry, so a part registered only under a legacy standard is flagged before the date arrives, not after.
Wiring and detection: two codes of practice
Two Indian Standards govern how the mill is wired and how it detects a fire. IS 732 is the code of practice for electrical wiring installations, and the mill's internal wiring and its tie-in to the building are specified to it. IS 2189 is the code of practice for the selection, installation and maintenance of automatic fire detection and alarm systems, and the detectors inside the enclosure and their interface to the building's fire panel are selected and installed to it.
Neither is a certificate, and no one issues one for them. They are codes of practice. Conformity is demonstrated by the specification in the type file and by the contractor's test results at each site, which is exactly the shape of evidence a Chartered Electrical Safety Engineer or a fire officer expects to see.
End of life: extended producer responsibility
Under the E-Waste (Management) Rules, 2022, producers and bulk consumers of electronic equipment register on the Central Pollution Control Board's EPR portal and route end-of-life equipment only to registered recyclers, who issue certificates. The mill's hardware never goes to a scrap dealer. When a mill leaves a building, what happens to its media is set out in the agreement, and the metal goes to a registered recycler with the recycler's certificate on file.
Why no scheme certifies a mill
Because a mill is neither a building nor a component. Building schemes certify facilities designed as facilities. Component schemes certify parts. Nobody's scheme has a category for a self-contained ten-kilowatt inference cabinet installed as equipment in someone else's room, and until one does, the honest position is that a mill cannot be certified, only made ready for every regime that governs it.
Anyone who tells you their in-building mill is certified is naming one of the regimes above, or a component's mark, or a hall's certificate that does not extend to the room. We do not.
The checklist, split in two
What we do instead is write the checklist, and split every line on it into one of two columns.
| Type level: the mill as a type, pre-cleared by the module library | Site level: done for every room |
|---|---|
| Incoming panel, type-tested to IS/IEC 61439 | Tie-in by a licensed electrical contractor |
| Wiring specification to IS 732 | Contractor's test results for this installation |
| Detection layout to IS 2189, interface to the building's fire panel | Chartered Electrical Safety Engineer inspection |
| Clean-agent suppression and alarm-triggered cut-off logic | Test report filed with the Electrical Inspector before energisation |
| Component register with BIS registrations and their expiry dates | Fire NOC continuity with the building owner |
| Change-control class for every part (patch, minor, major) | Insurer's disclosure endorsement; after-hours cooling screen |
The left column is engineered once and inherited by every mill built from the library. A change to any item on it is a change-control event with a class, and a major change re-opens the column. The right column is done every time, by named people with licences, and produces the filings.
This is why the type file carries so much weight: it is cleared once and reused. Every module in the engine's library carries its complete type file, and every mill composed from those modules inherits it. Every site adds its own filings on top. When a mill is energised, what exists is a filed test report, an inspection by a Chartered Electrical Safety Engineer, a NOC continuity letter from the owner, a component register with dates in it, and a type file a buyer's auditor can read. The checklist itself goes into the compliance pack, so that the word certification-ready has a definition anyone can hold us to.