GridSight
Turn grid data into controlled action.
Not a dashboard. Not another data lake.The intelligence layer across the systems already running your grid.
GridSight connects network, asset, inspection and enterprise information into one operational context — giving AI the understanding and evidence required to support better grid decisions.
- Network
- Assets
- Inspections
- Enterprise
- External
GridSight
Shared grid context
- Understand
- Predict
- Prioritise
- Decide
- Act
Existing systems remain systems of record.
The grid doesn't have a data problem. It has a context problem.
Grid operators already have enormous amounts of data. The problem is that the information required for one decision is often spread across systems that do not understand one another.
Network operations
What is happening?
GIS
Where is it happening?
Asset management
What happened before?
Inspections
What condition is it in?
Weather & environment
What may happen next?
Work management
What are we already doing?
Critical decisions depend on the relationships between all of them.
Moving data is no longer the only challenge. Connecting its meaning is.
The control room stays the control room. GridSight assembles the context those decisions still require.
Applications
One intelligence layer. Three starting points.
Assets, operations and planning. Each one is a way in. They share the same grid context.
GridSight Asset Intelligence
Know which assets need attention — and why.
Connect condition, inspection, maintenance, topology and operating state to prioritise interventions.
- Asset risk
- Inspection intelligence
- Condition assessment
- Maintenance prioritisation
- Work-order context
- Evidence-backed recommendations
GridSight Operations
Give operators one operational picture across systems.
Bring network state, events, assets and historical context together during investigation and operational decision-making.
- Situation awareness
- Event correlation
- Topology-aware investigation
- Operator decision support
- Incident analysis
GridSight Planning & Capacity
Understand constraints, scenarios and capacity in context.
Contingency analysis sits inside this view, next to congestion, capacity and investment questions.
- Congestion context
- Capacity analysis
- Scenario comparison
- N-1 support
- Network constraints
- Investment and planning context
A decision
One asset. Every relevant signal. One decision-ready picture.
GridSight does not invent the answer from a prompt. It assembles the operational context behind the decision.
Asset
Transformer TR-2048
Attention required
- Current state
- Elevated loading
- Inspection
- Recent defect identified
- Maintenance
- 2 open work orders
- Network context
- Supplies constrained area
- Environment
- High-load conditions expected
Recommendation
Engineering review before next peak period
Evidence 7 supporting records
Decision Human approval required
How it works
Connect, understand, reason, govern, act.
01
Connect
Read from the systems already running the grid.
02
Understand
Resolve information against assets, topology and operational context.
03
Reason
Apply models and agents to the connected context.
04
Govern
Check identity, permissions, policy and evidence.
05
Act
Return approved outcomes into existing workflows and systems.
The level of autonomy belongs to the workflow — not the model.
- ObserveAI analyses.
- RecommendAI proposes.
- PrepareAI prepares work.
- ApproveA qualified person authorises.
- ExecuteApproved systems perform the action.
Different workflows can stop at different stages according to policy and risk.
GridSight does not replace SCADA, EMS, GIS, EAM or operational control systems.
GridSight is decision support. Switching, protection and safety-critical control remain within certified systems and authorised operational procedures.
Grid ontology
Give AI a model of the grid — not just access to documents.
A transformer isn't simply a record. It sits inside a topology, has a condition history, inspections, maintenance, risks, dependencies and operational constraints.
Substation
contains
Transformer
connected to
Line
supplies
Region
Transformer
- Inspections
- Defects
- Work orders
- Measurements
- Risk
- Policies
The ontology lets GridSight reason over these relationships rather than treating enterprise information as unrelated records and documents.
Inspection
Turn inspection data into asset intelligence.
GridSight connects inspection findings to the asset, its history, operating state and existing work — rather than leaving findings inside separate inspection reports.
01
Image, LiDAR, thermal, report
02
Defect detection
03
Asset
04
Condition and history
05
Risk
06
Work order
The product
One shared grid context. Different operational views.
The same model, opened where the work happens.
- Grid overview · North
Grid overview
Network state, risks and active situations.
- Asset 360 · TR-2048
Asset 360
Everything known about one asset.
- Inspection intelligence
Inspection intelligence
Imagery, defect, asset, risk and work.
- Decision workspace
Decision workspace
Evidence, recommendation, approval and action.
Illustrative views. They show the shape of the product, not a live system.
Keep the systems that already run the grid.
GridSight connects context across these systems. It does not become another system of record.
Grid operations
SCADA · EMS · DMS · Historians
Assets & work
SAP · EAM · ERP · Work orders
Spatial
GIS · Topology · Network models
Inspection
Images · LiDAR · Thermal · Reports · Field findings
Enterprise data
Databases · Warehouses · Lakes · Documents
External context
Weather · Markets · Regulatory · Geospatial
Categories describe intended coverage. They do not imply partnership, certification or endorsement by any vendor.
Fit
Built for grid environments.
Controlled
Identity, policy and approval before action.
Traceable
Recommendations resolve to their supporting evidence.
Deployable
Customer cloud, private cloud, on-premise, edge or isolated environments.
Model-independent
Use commercial, open or specialised models without rebuilding GridSight.
GridSight is NeuroCluster applied to grid operations.
GridSight is an industry application on the NeuroCluster platform. The same enterprise foundation becomes a domain-specific intelligence environment through grid ontology, integrations, applications and workflows. Your GridSight deployment is scoped around your needs; adopting all three horizontal products is not a prerequisite.
Outcomes
What GridSight is designed to improve.
Operational change, described as intent. No invented savings or accuracy figures.
Faster investigations
Spend less time assembling information across systems.
Better maintenance prioritisation
Bring condition, history, network importance and existing work into one view.
Better planning context
Connect network constraints, assets and external conditions.
More effective inspections
Turn inspection findings into connected asset intelligence.
Reusable operational context
Avoid rebuilding integrations and semantics for every AI initiative.
Controlled AI adoption
Introduce AI without bypassing existing authority and operational procedures.
Adoption
Start with one decision. Build reusable grid intelligence.
GridSight is designed to turn individual AI projects into reusable operational intelligence.
01
First workflow
Connect the objects and systems needed for one decision.
02
Second workflow
Reuse the same assets, topology, history, identities and policies.
03
Every workflow after that
Extend the shared model rather than starting again.
- 01
Land
Choose one high-value workflow.
- 02
Prove
Show value with operational evidence.
- 03
Expand
Add adjacent data, assets and workflows.
- 04
Standardise
Reuse shared context and governance.
- 05
Scale
Deploy applications across teams and regions.
A six to ten week first workflow is a planning target where data access and approvals are ready. It is not a contractual commitment. Duration depends on system readiness and internal approvals.
Questions
Does GridSight replace SCADA, GIS or EAM?
No. Those systems remain the systems of record. GridSight is an intelligence layer across them. It connects what their records mean in relation to one another.
Does GridSight write to operational control systems?
No. Operational technology is read through a one-directional, rate-limited path, usually via a historian rather than the control system itself. There is no write path into process control. Switching, protection and safety-critical control stay inside certified systems and authorised operational procedures.
Can it run entirely in our environment?
Yes. GridSight can run in your cloud, a private cloud, on-premise, at the edge, or in an isolated environment, including with local inference.
Do we have to use a specific model?
No. Commercial, open and specialised models can be used for different workloads. Changing a model does not require rebuilding the grid context, the policies or the applications.
How much ontology must be built before we see value?
Enough for one decision: the asset, its place in the network, its history and the constraint that bears on it. The first workflow builds that context. The next one reuses it.
How do we start?
Bring one workflow where engineers or operators still assemble information by hand across several systems. A six to ten week first workflow is a planning target where data access and approvals are ready, not a commitment.
Start with the grid decision that matters most.
Bring one workflow where engineers or operators still have to assemble information manually across multiple systems.