ARCNODE EMS speaks Redfish to the compute and DNP3, Modbus, BACnet and SNMP to the grid. point maps come from curated vendors. these maps are used during site commisson. Consistent mqtt api, unit are encoded in the topic path. Nothing in operational technology speaks Redfish. Nothing in server management speaks DNP3.
An Autogenerated spec consiting of CAD drawing, BOM, and installation squence.
Buffers GPU transients. Supervises BESS, compute, and grid. Dispatches against curtailment and price.
IEEE 738 dynamic line rating. Surfaces 10–30% of interconnect capacity that static ratings hide.
BESS protects your GPUs from grid fluctuations1. Keeping your training and inference targets predictable.
1. Haggi & Morankar, "Resilient Design and Optimal Operation of Battery Energy Storage Systems for Behind-the-Meter Data Center Microgrids," arXiv:2609.19342.
The engineering deliverables package is built from you specications: BOM, ionterface plate DXFs, single-line + P&ID, cable schedule, install sequence. Your integrator builds from this.
Equipment list with vendor, model, quantity, and procurement notes. Fab tier flagged for NDAA and ITAR requirements.
DXF drawings of container interface plates — mechanical mount points and penetrations for power, signal, and cooling connections. Files are ready for fabrication.
Single line diagram, piping & instrumentation diagram, and comms architecture drawing — switches, VLANs, EMS data paths to BESS, compute, and grid equipment.
Routing, sizing, and termination details. Covers power, signal, and cooling connections between containers and customer-supplied equipment.
Step-by-step installation and commissioning sequence. Integrator follows it. ARCNODE EMS validates each step before going live.
When your configuration generates, your integrator gets a single signed URL to a dashboard like this. Three columns — edge & connectivity, engineering drawings, manifests & schedules. Gateway container, CloudFormation template, and mobile client on the left; drawings and schedules on the right. Every artifact versioned, every URL pre-signed and 7-day expiring. No login portal to chase.
Site controller. Supervises BESS, compute, and grid on your pad. Runs in your AWS account or fully air-gapped. Device links use TLS 1.3 with X.509 certificates (DNP3, Modbus, Redfish); utility dispatch arrives over mutual TLS (IEEE 2030.5).
Flexible interconnection is usually the fastest utility approval. EMS rides curtailment events with BESS and throttles compute to stay within contract.
ARCNODE EMS supervises import and export at your point of interconnection. Certified export limiting and interconnection approval are the operator's and EPC's responsibility.
Supervises OTS and custom equipment via industrial protocols. External setpoint architecture — each device runs autonomously, EMS sets the targets.
RAG agent over a curated domain corpus and site data. Analysts ask in natural language. Plotting tools render charts inline.
Live SLD, live telemetry, live dispatch. Write actions require explicit unlock — operators see what's happening, they don't accidentally change it. Full desktop + mobile support; only mobile depicted below.
Live current, protection IDs, CT/PT locations.
Arbitrage, ancillary, capacity — tracked to the dollar.
Power, thermal, GPU utilization — per node, per rack.
Charge, cycles, throughput — every cell accounted for.
Natural language over live telemetry and historian data.
Transmisisin lines without sensors are 10-30% less efficient. Grid-edge sensors measure conductor temperature and ampacity in real time per IEEE 738. Operators dispatch against actual thermal limits, not worst-case assumptions.
Per-site climatology picks the SKU. Same carrier board and firmware binary across both — the sensor, cable harness, PV panel, and battery are field-swappable kit components.
Deploy where less than 15% of the year sees wind under 1 m/s perpendicular. DLR falls back to static rating below the sensor's 1 m/s threshold — the marginal capacity below that is small enough to walk away from.
Deploy where more than 15% of the year sees wind under 1 m/s perpendicular. The Vaisala widn sensor it tuned for low wind corridoes.
ARCNODE generates your engineering package automatically.
Enter your load requirements, site constraints, and deployment context into the System Configurator. The sizing engine outputs a module configuration in seconds.
Your inbox gets everything: Delivery Portal link (EDP package — BOM, drawings, installation sequence), EMS deployment link (CloudFormation or ISO for air-gapped), and EMS Android client (iOS not supported).
Hand the EDP to your integrator. They procure the equipment and assemble the containers. Spin up the ARCNODE EMS. The EMS starts in simulation mode and goes live on commissioning — no ARCNODE involvement required after delivery.
US datacenters wait about 4 years for grid power on average — 7 years for 100 MW in Northern Virginia1. One MW of H100-class GPUs earns roughly $0.9M a month in rental revenue at 2026 contract rates2. Every month online sooner is worth about that much, per MW.
1. JLL, 2026 Global Data Center Outlook, cited in "How Long It Actually Takes to Power a Data Center in 2026", Construction Owners Association of America.
2. ~784 GPUs/MW · $2.35/GPU-hr one-year contract (Mar 2026) · 70% utilization · gross revenue, not margin. H100 rental pricing, Akash Network.
ARCNODE is open infrastructure. The engineering templates, EMS software, and sizing engine are freely available. We believe the industry moves faster when the stack is open.
Input your constraints. Receive your EMS instance, mobile app, and engineering package.