Schneider Electric–Equinix pilot: what should be verified when deploying software-defined MV switchgear in a live data center?

Introduction

• Schneider Electric unveiled its software-defined medium-voltage switchgear architecture on September 28, 2026.
• Equinix is piloting the solution in an operational colocation data center.
• The stated objective is to combine modular hardware, software-configurable functions, and less custom wiring.
• The pilot's most important question is not only whether the system works, but whether protection, change management, cybersecurity, and recoverability can be validated.

According to Schneider Electric, further pilots will continue in 2027, with broader availability planned for 2028. This means that any assessment of the technology must distinguish between the stated architectural benefits and evidence from sustained operation. A live data center pilot is important precisely because it can demonstrate, under controlled conditions, how the system behaves in real operational, maintenance, and change-management scenarios.

What happened in the Schneider Electric–Equinix pilot?

The announcement concerns a medium-voltage switchgear architecture that combines modular hardware with software-configurable functions. The manufacturer's concept is intended to reduce custom wiring and make subsequent modifications easier to implement.

Equinix's participation is significant because the pilot is taking place in an operational colocation data center rather than exclusively in a laboratory environment. However, this alone does not demonstrate broad applicability. The value of the pilot will depend on which operating states, faults, and interventions are tested, and what auditable evidence is produced.

Who is it for, and why does it matter to the data center sector?

The development is primarily relevant to data center operators, facility managers, electrical designers, project owners, technical procurement teams, and colocation providers. The professional focus is not simply on purchasing new equipment, but on evaluating how software configurability fits with existing redundancy, protection philosophy, and operating procedures.

Faults in medium-voltage distribution can affect multiple interconnected systems. For this reason, every new control or configuration layer must be treated as part of the complete power delivery chain, not as a standalone digital function.

Why does software-defined architecture matter now?

With conventional switchgear, a functional modification often requires documentation updates, wiring work, testing, and a planned intervention window. In principle, a software-configurable approach can reduce the need for some physical modifications and enable a more standardized hardware platform.

However, this benefit can also create new dependencies. Configuration versions, firmware status, access permissions, and communication links can directly affect the system's verifiability. A change may be technically faster to implement, but the approval and testing process must not become shorter or less rigorous as a result.

What does this mean from an operational perspective?

The central questions are which functions a change affects, who may approve it, how it can be tested, and how it can be rolled back safely. Before every change, the operator must understand the current configuration and how it relates to single-line diagrams, protection settings, interlocking logic, and operating procedures.

The maintenance model may also change. In addition to mechanical and electrical inspections, teams must manage the firmware lifecycle, configuration backups, integrity checks, and access permissions. It must also be established in advance which functions remain locally available if communications are lost or the central supervisory system fails.

What should be technically verified during the pilot?

Protection and selectivity

Software-configurable functions must not override the approved protection coordination. Verification should determine how setting changes affect the sequence of operating times, the protection of transformers, generators, and feeders, and the separation of the A and B power paths.

Testing should cover not only normal network conditions but also maintenance states, backup supply arrangements, and partially unavailable configurations. Documented evidence must confirm that the protection study matches the settings actually loaded into the equipment.

Firmware, version control, and rollback

Every firmware and configuration update requires an approved target version, compatibility verification, a backup, and a rollback procedure. The pilot should test not only successful updates but also recovery after an interrupted or failed update.

The audit trail should show who made the change, when it was made, why it was required, and how it was approved. A key requirement is that the operator can clearly identify the active version and the latest verified backup.

Cybersecurity and access control

Digital configuration introduces new access points and permission-management requirements. User roles, remote access conditions, logging, interface protection, and the authorization and revocation of vendor access must all be assessed.

In addition to network segmentation, a failure of a communication or supervisory component must not result in an unpredictable switching state. The safe default state and the availability of local control must be demonstrated through testing.

Common mistake: equating software flexibility with lower risk

A common mistake is to assume that less custom wiring automatically means simpler operations. Physical complexity may decrease while responsibility for configuration and lifecycle management increases.

It is particularly risky when a project team treats factory default settings as the final operational configuration or regards an update as merely an IT task. The change must pass through the same engineering controls as any other intervention affecting critical power infrastructure.

SAT and IST: what must be demonstrated before handover?

The site acceptance test, or SAT, must confirm alignment between the installed hardware, configuration, interlocks, indications, and documentation. Testing should cover local and remote operation, alarms, communication loss, and access levels.

The integrated systems test, or IST, must verify how the switchgear works with transformers, generators, UPS systems, supervisory systems, and operating procedures. Scenarios should include loss of supply, an incorrect switching command, the use of redundant paths, and controlled restoration. In a live environment, every test must be linked to a risk assessment and an approved methodology.

Recommended next step

The assessment of software-defined medium-voltage switchgear should begin with a review of the existing infrastructure and operational capabilities:

1. Document the single-line diagrams, protection settings, and normal and abnormal operating states. 2. Create a responsibility matrix for approving, loading, and rolling back configurations. 3. Define the required factory, site, and integrated tests, together with their acceptance criteria. 4. Assess the full lifecycle of firmware support, spare-parts availability, and required expertise. 5. For a pilot, limit the scope of change and provide a verified rollback option.

In Digital Technologies' engineering approach, this type of deployment is not a standalone product replacement. It is an electrical, control, cybersecurity, and operational workstream. Decisions should be based on documented system impact, maintainability, and recoverability.

Conclusion

The Schneider Electric and Equinix pilot could be an important step toward more flexible configuration of medium-voltage distribution in data centers. However, the September 28, 2026 announcement concerns an architecture still being introduced, with broader availability planned only for 2028.

For technical decision-makers, the main question is therefore not whether the system is software-defined, but whether every configuration can be demonstrated to be safe, traceable, and recoverable. Protection, selectivity, firmware management, cybersecurity, and integrated testing together determine whether the concept is suitable for deployment in a specific critical environment.