Switchgear-room form factor. PrecisionDCMS operating contract.

• The primary installation location is a switchgear room, microgrid building, generation plant, BESS building, central cooling plant, utility room or industrial control space.
• The customer wants freestanding hardware that visually and mechanically belongs beside electrical or mechanical lineups rather than in an ordinary IT rack.
• A centralized field-cable landing point is preferable to many smaller wall enclosures.
• Point count, network demarcation, OOB, power distribution or service access justify multiple internal compartments or bays.
• Door-mounted local HMI and service status are required.
• Independent A/B hardware should be arranged as a coordinated lineup.
• The site uses industrial control power, field wiring, fiber, serial or protected-network interfaces.
• The environment needs engineered cooling, filtration, corrosion protection, cable entry, grounding or physical-security provisions.
• A complete factory-staged hardware package is preferable to field assembly of unrelated cabinets and rack devices.

Reference architecture — final dimensions, ratings, components and capacity are order-specific.

Industrial Standard follows the same PrecisionDCMS Standard rule as every other hardware form: two independently powered and networked matching nodes with tested coordination, explicit leader/follower or approved active/active behavior, fenced singular actions and no shared-storage dependency in the base local architecture.

• AC or DC input source selected by the approved site design
• One or two independent inputs according to Lite/Standard and the availability objective
• Lockable or guarded disconnecting means as applicable
• Surge and transient protection selected for source and exposure
• Industrial power conversion
• Active or diode ORing where designed
• DC hold-up or controlled shutdown where required
• Electronic branch protection
• Separate monitoring of compute, PFC, I/O, network, HMI, OOB, accessories and outputs
• Source, PSU, branch, battery/hold-up and enclosure-temperature monitoring
• A/B power paths traced to actual upstream sources
• NX server power mapped to documented rack or cabinet power sources
• GMS safety power remains independently engineered

• Top or bottom field-cable entry
• Segregated power, relay, digital, analog/RTD, serial, Ethernet and fiber pathways
• Pluggable labeled terminals
• Shield and protective-earth bars
• Mechanically keyed A/B harnesses
• Industrial copper and fiber network demarcation
• Serial gateway or one-master architecture
• Front-accessible service and test points where appropriate
• Field wire numbers, point tags, terminal references and cable schedules
• Optional remote-I/O or distributed Field enclosures for distant equipment
• No uncontrolled bridging between OT, OOB, security, enterprise or customer-management networks

• Site and lineup health
• Power-source and branch status
• Core/Node A and B role and availability
• OT network, OOB and Cloud-path health
• Source quality and stale state
• Active alarms and local-continuity events
• Maintenance and out-of-service state
• A/B disagreement
• Queue and replay state
• GMS monitor-only status where present
• Permitted S3/S4 actions only where ordered
• No raw arbitrary register writes
• Named user or controlled local service access
• Session timeout and audit
• Local fallback view during WAN or hosted-service loss according to configuration

• Electrical protection remains with protective relays, breakers and the designated electrical authority.
• Microgrid dispatch and generation control remain with the approved EMS, plant controller or OEM controls unless an order-specific supervisory function is engineered.
• Fire alarm, gas shutdown, emergency shutdown and equipment-local safeties remain independent.
• The ability to read a Modbus register, API or HMI does not grant authority to write it.
• Output control is optional and disabled by default.
• S0 independent safety is monitor-only.
• S1 critical electrical is monitor-only unless an order-specific restricted function is approved.
• S2 automatic mechanical logic remains local to an approved controller.
• S3 supervised operator actions require role, mode, interlocks, expiration and feedback.
• S4 indication and notification may be permitted with feedback or supervised test.
• No expired command is replayed after an outage.
• No shared center-bay element may silently become the authority for both A and B sides.

• 24/7 NOC monitoring where ordered
• OT network and OOB monitoring
• Utility, generation, BESS, switchgear, cooling and environmental event correlation
• Carrier and remote-hub coordination
• Alarm, incident, work and change linkage
• Vendor and OEM dispatch
• Field-service and remote-hands integration
• Preventive maintenance and calibration
• Configuration backup and restore testing
• Firmware and vulnerability lifecycle
• Spares and replacement planning
• Customer status and evidence
• Compliance evidence operations
• Data Fabric and customer API delivery
• Reliability and recurring-fault review