A utility-scale battery plant is documented in two languages at once. The electrical side is a set of one-line diagrams, from the point of interconnection down through the step-up transformers and the power conversion systems to the DC side of the racks, tagged with ANSI device numbers and equipment designations. The mechanical side is a small set of P&IDs: a thermal-management loop, an HVAC set for the enclosures, and a fire and gas layout that is drawn like a P&ID whether the suppression is water, clean agent or ventilation. The registers a project runs on, the I/O list, the instrument index, the protection and metering schedule, the cable schedule, draw from both.
This is a reference for the engineer handed a BESS package who has to build those registers, from an EPC's balance-of-plant set, an integrator's enclosure drawings and a utility's interconnection one-line that were all produced by different parties.
Key takeaways
- The one-line set is large and the P&ID set is small; both feed the same I/O list.
- Expect the IEEE C37.2 device set on the medium-voltage one-line and a block for the PCS with interface signals rather than discrete devices.
- The thermal-management P&ID reads like a small utility loop: chillers, pumps, glycol, temperature and flow per enclosure.
- Off-gas detection is the earliest warning on the fire and gas drawing and it talks to both the fire panel and the battery management system.
- The I/O list has to distinguish hardwired from serial points, because a battery plant carries thousands of the second kind.
The one-line set
| Level | What is on the sheet | Characteristic tags and devices |
|---|---|---|
| Point of interconnection | Utility metering, the POI breaker, the interconnection protection the utility specifies | Revenue meter (MFM-POI-01 on the synthetic sheet), 52 POI breaker, 32 directional power, 27 and 59 voltage, 81 frequency, 25 synchronism check, 86 lockout |
| Medium-voltage switchgear | Main and feeder breakers, bus PTs and CTs | 52-MV-01 and the feeder 52s, 50 and 51 overcurrent, 50N and 51N ground, bus differential where fitted, DT-GIS-04 style gas-density monitoring on GIS |
| Step-up transformers | Inverter-side to MV | 87T-T1 differential, 49 thermal, 63 sudden pressure, 71 oil level, winding and oil TT (TT-T1-OIL), tap position |
| Power conversion systems | Inverters, LV side, DC link | Drawn as a block: PCS status and trip, AC and DC metering (MFM-PCS-02), DC contactor status, the interface to the plant controller |
| DC side | Combiners, rack breakers, strings | Rack-level breakers and fuses, string current, isolation monitoring, DC bus voltage, mostly reported over the battery management network |
The one-line is where the protection and metering schedule comes from: every relay, its device numbers, its CT and PT ratios, its trip targets. It is also where a large part of the hardwired I/O originates, since breaker status, trip and close commands and lockout states are still wired to the plant controller on most sites regardless of what the relays report over the network.
The thermal-management P&ID
Liquid-cooled enclosures have a coolant loop and it is drawn as a P&ID: chillers or dry coolers, circulating pumps, a glycol fill and expansion system, and a supply and return to each enclosure. The instrumentation is a small utility loop repeated many times:
- supply and return temperature per enclosure (TT-ENC-07-A on the synthetic sheet, with a B for the return);
- coolant flow per enclosure or per branch (FT-CT-3001);
- loop pressure and differential pressure across the enclosure heat exchangers;
- chiller interface points, usually serial, with a hardwired run and fault;
- expansion tank level, glycol concentration sample point, filter differential.
The count is driven by the number of enclosures. A site with a hundred enclosures has a hundred sets of the same four or five loops, and the instrument index has to carry the enclosure number on every row so the DCS or EMS graphics can be generated from it rather than typed.
Air-cooled enclosures replace this with an HVAC schedule: an air handler or split unit per enclosure with supply and return air temperature, filter differential, and a run and fault. The P&ID-shaped drawing is thinner but the register is the same shape.
The fire and gas drawing
NFPA 855 drives most of what is on this sheet, and it is the part of the set a process engineer is least likely to have seen before:
| Element | What it is for | Typical points |
|---|---|---|
| Off-gas detection | Earliest warning of a cell venting before thermal runaway | One or more detectors per enclosure (OGD-ENC-07), outputs to the fire panel and to the battery management system |
| Smoke and heat detection | Conventional fire detection in the enclosure and in electrical rooms | Addressable detectors on a fire loop, hardwired alarm and fault |
| Gas detection | Combustible gas (hydrogen and hydrocarbon off-gas) and, in some designs, CO | Detectors with alarm and high-high levels, ventilation start |
| Explosion control | Deflagration venting per NFPA 68 or prevention per NFPA 69 | Vent panel position switches, exhaust fan run and fault, damper position |
| Suppression | Water mist, clean agent, or aerosol per the AHJ and the UL 9540A results | Release circuits, discharge pressure switches, manual release and abort, isolation valve position |
| Emergency stop | Plant and enclosure level | E-stop status to the PCS and the plant controller |
These points are the safety-critical part of the I/O list, and most of them are hardwired. The cause-and-effect matrix for a battery plant is built almost entirely from this sheet: which detector, at which level, isolates which racks, starts which fans, releases which suppression, and trips which PCS.
Building the registers
The I/O list on a battery plant has a column that a process plant's often does not need: the transport. A site controller sees a few hundred hardwired points and many thousands of serial ones, and the commissioning, the SCADA build and the cyber-security review all treat the two differently.
| Register | Built from | Notes |
|---|---|---|
| I/O list | One-line (breaker status, trips, metering), thermal P&ID, fire and gas drawing, PCS and BMS interface lists | Hardwired versus serial on every row; enclosure number on every row |
| Instrument index | Thermal P&ID, fire and gas drawing | Repeated per enclosure; the enclosure number is the key |
| Protection and metering schedule | One-line | Device numbers per IEEE C37.2, CT and PT ratios, trip targets |
| Equipment list | One-line and thermal P&ID | Transformers, switchgear, PCS units, chillers, pumps, fans |
| Cable schedule | One-line, block diagrams, the fire loop drawings | Power, control and fibre; the fire loop is its own class |
| Cause-and-effect matrix | Fire and gas drawing, PCS interface | The safety logic of the plant |
Conventions on one site
A BESS package is assembled from parties who do not share a tagging rule. The interconnection one-line follows the utility's standard. The integrator's enclosure drawings follow the integrator's, and if the integrator is European that may be an IEC 81346 reference designation system, where a tag reads like =E1+Q1-F1 rather than a letter code and a loop number. The thermal package follows its supplier. The fire and gas drawing follows the fire contractor.
The registers hold every tag as its sheet prints it, with the sheet reference on the row. Translating the integrator's IEC designations into ISA-style tags, or the reverse, produces a register the field cannot match to a nameplate; keeping both, keyed on the sheet, produces one it can.
Tagsight reads one-lines and P&IDs, in ANSI, ISA 5.1 and IEC 81346 as drawn, into these registers, with every row referenced to its sheet and confirmed by the engineer before it exports. The protection settings, the UL 9540A conclusions and the cause-and-effect logic remain the project's engineering.