Faults are found late, and by accident
Equipment incompatibility surfaces on commissioning night, when every hour of downtime costs the most. The cause is usually one small setting nobody looked at.
IEC 61850 · POWER-NETWORK SOFTWARE
See the fault in the power network. Don’t guess it.
GridSight is software that connects to the network of power equipment — a substation, a power plant, a factory, anywhere electrical equipment talks to itself — reads the equipment configuration, finds faults in the equipment and in the network, simulates the whole network and tests it in different scenarios, and finishes with a report that proposes the most cost-effective changes.
This page describes the final, complete product — what it is being built for. Where it stands today is at the bottom of the page, and in detail on the technical page.
Final version, being built
Last updated: 14 November 2026
- Substations
- Power plants
- Factories and industry
GRIDSIGHT / IEC 61850SCL · GOOSE · SV
01 / THE PROBLEM
What problems it solves.
These four pains are what the tool is built for.
Guessing replaces evidence
The engineer knows something is wrong, not which message, which device or which setting. Fault-finding becomes trial and error and personal experience.
Every change is a new risk
Settings are changed without re-testing, and the result is a new fault that may not appear until the next start-up.
The result never becomes a document
Findings stay in chat threads and notebooks. The operator or customer receives no report — and efficiency is never measured.
Commercial tools for this work exist, and most of the market uses them. GridSight is not built to replace that ecosystem on sentiment; it is built for these four problems.
02 / THE COMPLETE PRODUCT
What the final version does.
Five jobs, on a real network, with no internet connection.
- 01
Connects to the equipment network
Connects to the power network — substation, plant, factory, any site with electrical equipment — and recognises the devices talking on it.
- 02
Reads the equipment configuration
Reads each device’s settings and structure and compares them with what they were meant to be, showing the mismatch where it occurs.
- 03
Finds faults in equipment and network
Sees a single device’s fault and the fault in the network and the communication between devices, and ties every finding to its evidence.
- 04
Simulates the whole network and tests it
Rebuilds the network in software and tests it in different states — normal scenarios, faults, boundary conditions — without needing the physical equipment at hand.
- 05
Reports and proposes the best change
Finishes with a written report and says which change is the cheapest effective fix.
These five jobs are the scope of the complete version, and the product is in development today. What is already built is in the status section, and the exact state of each part is on the technical page.
03 / WHERE
Where it is used.
Substations
Commissioning, fault-finding and configuration review — before energising and after every change.
Power plants
Protection and control networks, equipment from several manufacturers, and testing a change before applying it.
Factories and industry
Internal power networks and protective equipment, where a stopped line has a real cost.
Laboratories and consultancies
Extra analysis capacity at peaks, and independent review of supplier files.
04 / EFFICIENCY
Efficiency: what it removes.
A substation’s efficiency is measured by three things: commissioning time, the number of rework loops, and the number of unplanned outages. The tool touches all three — it finds the fault earlier, tests every change before it is applied, and hands over the result as a document.
A closed loop: every change is tested again before it is applied.
We publish no “percent faster” figure. A number that has not been measured is a claim, not a result. The measurement method for a pilot is defined: the same three numbers, before and after, on one real substation — and then they get published.
05 / STATUS
Where it stands today.
The complete version is not ready: there is no public release, installer or licence. What exists today is the analysis and test core, which is being built and tested; the numbers, the limits and the release path are on the technical page.
804 automated tests green, and five message defects found only by comparing against another implementation’s code.
06 / FAQ
Four questions worth asking before you pay attention.
Can I buy it now?
No. There is no public version, installer or licence, and no date has been announced. The exact state is on the technical page.
Does it work with equipment from every manufacturer?
We do not write that sentence before a real test. Until a live session with one named manufacturer’s equipment has been run and published, no compatibility claim is made.
Is it a replacement for foreign tools?
No. Those are hardware-plus-software ecosystems with global support. GridSight’s definition is narrower: software on the engineer’s laptop, offline, with a report and a change recommendation as the output.
I have substation work right now. What do I do?
The engineering work exists today: configuration review, traffic analysis and a pre-conformance readiness review — remote, fixed scope, with a written result. The IEC 61850 scope ↗
NEXT STEP
One network and one hour.
If you have a network in progress, start with that configuration file: we list the conflicts and see what the completed version needs for that job.