What should an outdoor telecom battery cabinet specification contain?
An outdoor telecom battery cabinet specification should contain five coordinated schedules: battery service, site and mechanical conditions, electrical interfaces, thermal and monitoring behavior, and supplier evidence with deviations. Each schedule should state what the buyer knows, what the supplier must calculate or select, and how the final configuration will be accepted. The schedules can sit in one document or in linked project forms. What matters is that they carry the same project revision, battery population and responsibility boundary.| Coordinated schedule | Buyer defines | Bidder returns | Acceptance record |
|---|---|---|---|
| 1. Battery service | Critical-load profile, reserve objective, outage pattern, recovery source, cycling duty and expansion case | Selected battery, usable-capacity basis, string arrangement, operating limits and recharge assumptions | Approved sizing calculation, battery schedule and settings record |
| 2. Site and mechanical | Climate, exposure, mounting location, access, transport and civil constraints | Populated arrangement, mass, support reactions, lifting method, clearances and installed enclosure details | Approved general arrangement, structural interface and site inspection |
| 3. Electrical interfaces | Source and load connection points, equipment voltage window, earthing concept and external ownership | Single line, DC ratings, protection, isolation, conductors, terminals, cable entries and bonding | Drawing review, device records, torque/continuity checks and functional tests |
| 4. Thermal and monitoring | Environmental cases, battery limits, required points, protocol and alarm destination | Heat balance, control method, auxiliary demand, sensor map, point list and failure responses | Thermal-control and alarm test records tied to the offered configuration |
| 5. Evidence and deviations | Required submittals, witness points, destination rules, FAT/SAT scope and document format | Evidence index, compliance response, assumptions, exclusions, deviations and options | Approved document register, closed exceptions and as-built handover pack |
Write every critical clause as State, Return and Verify
A specification becomes reviewable when a requirement has three parts. State records the design condition or required outcome. Return tells the bidder exactly what value, method or document to provide. Verify identifies the review, inspection or test that closes the requirement.
| Topic | State | Return | Verify |
|---|---|---|---|
| Battery temperature | Permitted module operating and charging limits for defined site cases | Predicted temperatures, sensor positions, control states and failed-control behavior | Calculation review plus an agreed functional or witnessed thermal test |
| Replacement access | Heaviest field-replaceable unit and available working envelope | Removal sequence, handling tool, door clearance and temporary isolation method | Service demonstration using the approved populated arrangement |
| DC isolation | Required safe boundary and actual operating/fault conditions | Device identity, DC ratings, location, interlocks and coordination basis | Document review, installed-device inspection and safe functional test |
| Remote alarm | Required event, priority, destination and response owner | Source point, threshold, delay, protocol/register and communications-loss state | End-to-end injection from cabinet input to the nominated monitoring platform |
Which battery data must be frozen before cabinet selection?
Freeze the battery service, electrical envelope, physical module data and maintenance method before selecting the cabinet. The battery model need not be named at the first enquiry, but the bidder must receive enough duty information to propose one without hiding decisive assumptions. The minimum battery basis should state:- the protected loads over time, not only one average power value;
- the reserve objective, consecutive outage pattern, cycling frequency and permitted load-shedding sequence;
- the energy source used for recovery and the acceptable recharge window while telecom loads remain online;
- approved or excluded chemistries, required life basis, end-of-life reserve and usable discharge limits;
- equipment voltage range, charge/discharge current limits, low-voltage behavior and communications dependencies;
- module dimensions, mass, terminal orientation, heat information, operating limits and BMS hierarchy; and
- initial quantity, expansion case, parallel-string policy and the unit expected to be replaced in the field.
Specify the outdoor boundary as an installed assembly
A telecom battery cabinet is exposed as installed, not as an empty shell on a laboratory floor. The weather boundary includes doors, seals, locks, cooling or ventilation devices, cable glands, drains, vents, filters, fasteners and any site-made entries. State which installed configuration the environmental evidence must represent. Begin with actual site data: minimum and maximum ambient conditions, solar exposure, humidity cycles, rainfall and driven water, dust, salt or industrial pollution, altitude, flooding, wind, icing where relevant, insects or animals, vandalism and nearby heat sources. Translate those conditions into project requirements with the destination rules and operator specification; do not copy an environmental class or ingress code without checking its scope. IEC 61969-3:2023 addresses basic environmental requirements, tests and safety aspects for outdoor enclosures at non-weatherprotected locations above ground. It can support enclosure evidence planning, but it does not size a foundation, validate a battery chemistry, prove the field cable entries or approve a site-specific system. The mechanical return should include a populated general arrangement rather than an outline drawing. Require total and shipping mass, centre of gravity, shelf and base reactions, lifting points, transport restraints, anchor or bracket interface, door swing, cooling clearances, cable bend space and the removal path for the largest serviceable item. Identify whether batteries ship inside the cabinet or are installed at site; the structural, transport and commissioning responsibilities change with that decision.Make the DC and control boundaries unambiguous
The battery cabinet specification should follow energy from each battery terminal to the external connection point. Require the offered minimum and maximum battery voltage, normal and limiting currents, prospective fault basis, string protection, main isolation, conductor and bus ratings, terminal details, polarity, bonding and the first unprotected cable length. Do not assume one fixed telecom voltage architecture. State the connected equipment’s approved input window and require the supplier to show compatibility through charge, discharge, low-voltage protection, recovery and abnormal states. If battery and power equipment come from different suppliers, name who owns charge settings, BMS-to-controller mapping, cable sizing, protective-device coordination and final functional testing. Control interfaces need the same precision. The bidder’s point list should identify each measurement and alarm, source device, engineering unit, threshold, delay, priority, protocol/register, local display, remote destination and fallback when communications fail. Remote commands should include authority, interlocks, logging and loss-of-link behavior. “Modbus available” or “BMS monitoring included” does not establish an operable interface.How should thermal performance be specified?
Specify thermal performance by limiting battery temperatures across defined operating and failure cases, then require the supplier to return the heat balance and control method. Do not select a fan or air conditioner from cabinet volume alone. The thermal cases should cover standby or normal cycling, maximum discharge, post-outage recharge, the applicable hot and cold outdoor boundaries, solar load, auxiliary-equipment operation, door-open service where relevant and loss of the primary thermal-control function. Require the calculation to identify battery and conductor losses, nearby equipment heat, enclosure heat transfer, air leakage, solar assumptions, altitude effects where applicable, sensor locations and auxiliary energy. Battery cabinet cooling is acceptable only when the offered method keeps the relevant cell or module locations within the approved limits and deals with condensation, contamination and failed-control response. The supplier should state temperature setpoints, alarm and action thresholds, permitted module-to-module spread, heater or charge-inhibit logic where applicable, filter or heat-transfer-surface maintenance, spare strategy and the power drawn from the site-energy budget. This article defines the performance return. The next specialist guide will compare passive transfer, filtered ventilation, heat exchange and active cooling selection in detail. Keeping that method decision separate prevents the procurement specification from forcing an unsuitable thermal architecture before battery and site inputs are known.What evidence should the supplier return with the bid?
The supplier should return enough project-specific evidence to identify exactly what is priced and why it can meet the stated duty. Catalogue pages may support the return, but they cannot replace a configuration schedule, calculations and coordinated drawings.Configuration identity
Cabinet model and revision, battery population, thermal option, protection devices, controller/gateway, accessories and a controlled bill of materials or configuration code.Engineering basis
Battery sizing and compatibility calculation, populated arrangement, electrical single line, thermal return, structural interface, cable/terminal schedule and monitoring point list.Evidence index
Applicable standards and editions, document scope, test or declaration reference, represented configuration, exclusions, expiry or revision where relevant and responsible issuing party.Carry the specification through FAT, SAT and handover
Do not write factory and site tests after the cabinet is built. Add an acceptance column to the specification while the bid return is being designed. This preserves traceability when a calculation becomes an approved drawing, a drawing becomes an installed configuration and an installed function becomes a test record.| Procurement promise | Before manufacture | Factory evidence | Site evidence |
|---|---|---|---|
| Populated mechanical fit | Approved arrangement, loads, clearances and replacement method | Configuration inspection, dimensions, lifting provisions and service demonstration | Foundation/bracket, anchoring, access and external-clearance inspection |
| DC protection and isolation | Approved single line, device schedule and fault basis | Identity, wiring, torque/continuity records and agreed functional checks | Field cable, earthing, polarity, settings and safe end-to-end operation |
| Thermal performance | Approved heat balance, cases, controls and sensor map | Control sequence, alarms and agreed representative test evidence | Installed clearances, airflow/heat path, settings and operating trend review |
| Monitoring response | Approved point list and cause-and-response schedule | Local input, display, output, communications-loss and reset tests | End-to-end NOC mapping, timestamps, priority, notification and response ownership |