What's next

The module aims to cover every function of the relay vendor tools and system configurators that a protection and substation automation engineer relies on, each run against the real tool. This page lists what is not built yet. Nothing here is a commitment to a date. Several items depend on what each vendor's tool allows, which is confirmed on a real installation first.

First runs against real tools, relays and Windows

For everything already built, the next step is evidence from real equipment and software:

• A run on a managed Windows laptop with no network: install, open a station SCD, and the Windows paths, code pages and registry reads.
• The PCM600 verification kit's report from a machine with PCM600, then SCD export and import against PCM600 itself.
• A relay of each vendor on a lab test network (Siemens SIPROTEC 5, Hitachi Energy Relion, SEL, GE) for online browse, reports, resynchronisation, segmentation, records and logs, and the commissioning view.
• Files written here (CID, SCD after edits, Add IED, Update IED, edition upgrade) opened in PCM600, DIGSI 5, SEL Architect and a system configurator.
• COMTRADE exports and test set configurations imported by OMICRON, Doble and Megger software.
• Signal lists imported by gateway tools.
• Real station exports of 100 or more IEDs, and real captures from a station bus with merging units.
• A session of the agent tools with a language model.

Relay configuration in the vendor's domain

• Protection and control logic: DIGSI 5 CFC charts and libraries, PCM600 Application Configuration, SEL SELogic, GE FlexLogic.
• Signal routing: the DIGSI 5 information routing matrix and the PCM600 Signal Matrix.
• The relay's local display: the DIGSI 5 display editor and the PCM600 Graphical Display Editor.
• Relay hardware configuration: modules, inputs and outputs, CT and VT data, and adding a device from its order code.
• SCADA protocol mapping inside the relay: DNP3, IEC 60870-5-103 and 104, Modbus, and time synchronisation.
• Firmware updates, PCM600 connectivity packages and DIGSI 5 device drivers: which firmware each relay runs and whether the project's device description matches it.
• IED user accounts, roles and security settings on the device, configured as part of the relay's configuration; policy and evidence stay with Neural Inverse Govern.

Relay settings

• Settings kept only in vendor projects and exports: PCM600 projects, parameter CSV and XRIO (through PCM600Cmd's parameter export, import and validation), DIGSI 5 projects, SEL settings files, GE and Schneider tools; and settings in SCL Private elements.
• Checks of setting values against minVal, maxVal and stepSize; editing Dbpos, Timestamp, Octet and other types.
• The vendors' own settings sheets and reports; printing and PDF; an approval workflow with signatures.

Loading and operating the relay

• Loading a CID to an IED through the relay vendor's tool (PCM600 has write and read commands for the IED), each load confirmed by the engineer. Today the CID is prepared here and loaded in the vendor tool.
• Operating the relay from the Editor: control (operate, select before operate, cancel), test mode, simulation, and selecting, editing and confirming setting groups, including comparing groups other than the active one. These stay with the vendor tool or the station HMI until a lab test relay is available and the confirmation design has passed a written safety review.

SCL engineering

• References between files (an input naming an IED only in another SCD or ICD); untitled and remote files.
• OCL validation rules (IEC TS 61850-6-3) and NSD data model validation (IEC 61850-7-7); suppressing a rule; edition-specific rules; checks of unsaved text.
• Reading large files off the window's main thread, and files over 64 MB.
• Adding access points and subnetworks; editing MinTime and MaxTime; report control blocks in the data flow matrix.
• Editing the substation from the single line diagram; drawing SubEquipment, GeneralEquipment, Function, TapChanger, NeutralPoint and the Edition 2.1 Line and Process sections; sxy:dir.
• Exporting the semantic compare; SED export.
• Edition 2 Services capabilities, data model changes and Edition 2.1 later binding in the edition upgrade; downgrades.
• Vendor project versioning (DIGSI 5 project versions, PCM600 project history, SEL QuickSet Device Manager) and import of vendor project exports.
• The vendors' terms, keymaps and layouts in the Editor.

Online and records

• Writes other than report control block attributes.
• TLS certificate revocation lists and OCSP, IEC 62351-4 end-to-end security, IEC 62351-8 role certificates, the Windows certificate store, and several requests in flight over TLS.
• ObtainFile, file rename and compressed records; SEL event report commands; record retrieval over TLS against a relay.
• An agent tool for enabling reports.
• The vendor monitoring views: DIGSI 5 test and diagnosis, PCM600 Signal Monitoring, SEL QuickSet HMI, IEDScout simulation.

Captures and records

• IEC 61850-90-5 routed GOOSE and Sampled Values, GSE management, and PRP and HSR trailers; Sampled Values members as values; captures over 512 MB.
• Comparing two COMTRADE records; frequency and harmonic views; the vendor record views (time signals, phasors, impedance circle, fault location, several records in one time base).
• Resampling with an anti-aliasing filter; XRIO export; reading test results back; test plans with a test set's own configuration.

Gateway signal lists

• Gateway tool formats (SICAM TOOLBOX II and Device Manager, SEL RTAC, Hitachi Energy COM600 and RTUtil500, Schneider EcoSUI).
• The type rule checked against IEC TS 61850-80-1 and IEEE 1815.1.
• IEC 60870-5-101 and Modbus; quality and time tags, counters, step positions, command options and dead bands; editing in the table.

Governance

• Reporting the module's actions to Neural Inverse Govern.