# Energy and utilities

> Station files checked before they reach site.

Source: https://neuralinverse.com/industries/energy/

---

![](/photos/facility.jpg)

[Industries / Industry and infrastructure](https://neuralinverse.com/industries/)

# Station configuration checked before it reaches site.

For protection, substation automation and commissioning engineers. Your relay vendor tools stay as they are.

Standards

IEC 61850 · IEC 62443

Station files

SSD, ICD, IID, SCD, CID, SED

Records

COMTRADE 1991, 1999 and 2013

Works with

SCL from PCM600, System Configurator and other IEC 61850 tools

Deployment

Self-hosted, your cloud or air-gapped

What your team gets

## IEC 61850 engineering without leaving the IDE.

Govern features are in use today. Domain modules are pre-release; their state is listed under Tools and formats.

- **Station configuration:** SCL files read, indexed, edited and compared natively from IEC 61850-6, with the rest of each file kept byte for byte.
- **Schema and consistency checks:** Files validated against your copy of the IEC schema and checked for references, names and address clashes before they are issued.
- **GOOSE and Sampled Values:** Captures decoded and checked against the station file.
- **Disturbance records:** COMTRADE records viewed with cursors, phasors and events, and downloaded from the relay over MMS.
- **Read-only commissioning:** IEDs browsed online over MMS, including secure connections, without writing to them.

Who uses it

## One environment for every role on the team.

- **Protection engineers:** Compare relay settings held in the SCL file, as issued against as left.
- **Substation automation engineers:** Configure IEC 61850 systems from the SCL files.
- **Commissioning engineers:** Check GOOSE and Sampled Values traffic against the design.
- **Analysis engineers:** Read disturbance records after an event.

Tools and formats

## What the Energy module handles, and how far each is verified.

The module is behind a setting, off by default. Loading a CID file to a relay goes through the relay vendor's tool.

- **SCL station files:** Reader, index, schema validation and checks verified on 292 public sample files, including PCM600 and Siemens System Configurator exports. The editors and the single line view are modelled.
- **Online IEDs:** Browsing, reports and record retrieval over MMS, read-only. Verified against open-source IEC 61850 servers on Linux; no relay has been connected.
- **Records and captures:** The COMTRADE reader and writer are checked against an independent reader, and the GOOSE and Sampled Values decoder against tshark.
- **Relay vendor tools:** PCM600 SCD export and import driven through its command line. Kit shipped: not yet run against PCM600.

No relay vendor tool or relay has been run, and no customer project opened. The module's checks are its own, not a vendor tool's acceptance. Domain modules are pre-release. Nothing is verified by a customer yet, and nothing is verified on Windows. Do not rely on a capability for production work until it is verified for your tools, versions and operating system. Product names belong to their owners.

How a change moves

## A person decides before anything leaves the desk.

1.  Propose
    
    An engineer or agent drafts a change to station configuration.
    
2.  Verify
    
    Schema and consistency checks run on the files before issue.
    
3.  Approve
    
    A push to the issued configuration waits for a named approver.
    
4.  Record
    
    Change, results and approval kept together in the audit record.
    

Standards

## Evidence for your engineering process. Conformance is yours.

- **IEC 61850:** Station files checked against the IEC 61850-6 schema and the module's own rules. Conformance testing of devices stays with you and the vendors.
- **IEC 62443:** Evidence toward IEC 62443: agent rules keep agents off the station and plant networks you name, and every change keeps its approver.

Neural Inverse provides evidence toward these standards. Certification stays with your organisation and assessor.

Products used

[Neural Inverse Build →

Editor, Agents and CLI with the domain tools your engineers need.](https://neuralinverse.com/build/)[Neural Inverse Govern →

Policy, approvals and audit for every AI tool your teams use.](https://neuralinverse.com/govern/)

Product names belong to their owners.

Related industries[Industrial automation](https://neuralinverse.com/industries/industrial/)[Telecommunications](https://neuralinverse.com/industries/telecom/)[Defence and space](https://neuralinverse.com/industries/defence/)

![](/photos/team.jpg)

## Talk to our team.

Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.

[Request access](https://neuralinverse.com/contact/?topic=access)[Contact us](https://neuralinverse.com/contact/)