A power system that combines conversion, storage and controls changes what an infrastructure team needs to verify. The procurement question extends beyond the electrical output to the decisions the system makes when sources, loads or components change state.
In its October 13 announcement, DG Matrix introduced the Interport SST Cell and Interport OS as the building blocks behind its Interport 360 Flex system. The company describes a skid-mounted approach that accepts AC supply and delivers native 800 VDC for AI infrastructure based on NVIDIA MGX. It says the software coordinates power routing, storage, ride-through and other functions across the system.
The announcement builds on an earlier GTC reveal of the transformer technology. The new disclosure concerns the modular building block and operating layer within the broader power solution. These are vendor descriptions of capability. The release does not provide enough test detail to independently establish efficiency, recovery behavior or deployment speed for a particular customer site.
My assessment is that buyers should treat the control model as part of the deliverable. A clear operating-state specification would be a useful starting point for evaluating this kind of architecture.
Ask for the state transitions, not just the steady state
Start by listing the conditions the proposed installation must handle: normal operation, a source interruption, storage unavailable, maintenance isolation and restoration of supply. For each condition, identify the expected power path and the service outcome promised to the customer.
Then examine the transitions between those conditions. A design may describe several supported modes without explaining how it moves safely from one to another. Request the sequence, the conditions that trigger it and the circumstances that require an operator's approval.
Keep the evidence specific to the offered configuration. The storage arrangement, connected sources and downstream loads all belong in the record. A demonstration using a different setup can inform an engineering discussion, but its limits should remain visible in the acceptance plan.
Separate protective functions from optimization
Power optimization and protection serve different purposes. Ask the supplier to identify which decisions seek efficiency or load smoothing and which enforce the supported operating limits.
Document the behavior if the optimization service stops, communication is interrupted or a sensor provides an invalid reading. Determine which functions continue locally and which require a wider control path. Establish how operators can recognize that the system has moved into a restricted operating mode.
These are proposed diligence questions, not findings about DG Matrix's product. Their value is to make assumptions explicit before a buyer relies on several functions being delivered through one integrated platform.
Review the downstream installation as a complete system
Converting an existing AC supply into a different distribution architecture still leaves a site-specific integration task. The project team needs an agreed boundary covering the conversion system, distribution equipment, connected racks and maintenance arrangements.
Ask for the applicable design documentation and protection coordination for the actual installation. Identify the isolation procedures, responsible parties and qualifications required for service work. A factory-integrated skid should arrive with the information the site team needs to integrate it into its own operating procedures.
Bring the facilities, electrical and IT teams into that review. They need a shared understanding of what happens to workloads when the power system changes mode, including any conditions under which load must be reduced or equipment taken out of service.
Make the handover preserve the tested behavior
A programmable power system needs a configuration record that survives commissioning. Capture the approved hardware, software, settings and test conditions alongside the results.
Agree on how future changes are approved. A software update, replacement module or revised storage configuration should have a defined review path and a way to determine which acceptance checks must be repeated. Record who can authorize the change and who confirms that the installation remains within its supported conditions.
For technical B2B suppliers, this creates concrete work: translate an integrated product's capabilities into an auditable operating plan and maintain that plan through the installation's life.
DG Matrix's update makes the software layer of AI power infrastructure more visible. Buyers can use that disclosure to ask for a stronger handover: documented power paths, verified transitions and clear responsibility for keeping the tested configuration intact.
Top comments (0)