For electricity grids
GridSight
- Bring network constraints and asset condition into one picture.
- Compare inspection, maintenance and capacity priorities.
- Give engineers the evidence behind a recommendation.
GridSight + OT Intelligence + Industrial Edge Pod
Better decisions for the infrastructure you already have.
Understand your assets. Assess operational risk. Explain why a decision makes sense. Three complementary parts, supported by one connected model and the same rules for access and approval.
For European grid operators, industrial partners and infrastructure investors.
From a signal to a decision
Know the risk. See the reasoning.
An alert tells you something changed. The connected picture helps explain what it could affect and which response deserves attention.
Electricity grid
- 01
Signal
A transformer is running hotter than usual.
- 02
Context
Link its load, inspection history and the customers that depend on it.
- 03
Risk
Estimate the likelihood and impact of a failure, including the effect on supply. Show the assumptions and missing data.
- 04
Decision
Compare an inspection, a load adjustment and planned maintenance. An authorised engineer decides.
- Failure likelihood
- Hours of disruption
- Cost ranges
Illustrative examples. Risk estimates depend on available data and agreed methods; they are not measured customer results.
Intelligence for critical infrastructure
Two ways to understand. One way to run locally.
GridSight supports grid decisions. OT Intelligence connects operational equipment, security findings and dependencies across grids and industrial sites. The Industrial Edge Pod brings processing to the site. Start with the part that fits your problem.
For operational technology
OT Intelligence
- Understand operational technology: controllers, gateways and networks across substations, offshore installations and industrial sites.
- Connect existing security findings, equipment condition and maintenance to the services that depend on them.
- Prioritise vulnerabilities, ageing equipment and recovery work by safety, availability and operational impact.
For processing on site
Industrial Edge Pod
- Collect, normalise and buffer approved data locally, without a permanent connection to the central platform.
- Forward only approved data through a controlled gateway when the connection is available.
- Choose a physical or virtual appliance; scope local analytics and compute separately.
From the site to the shared platform
Collect locally. Share with control.
The Industrial Edge Pod is a physical or virtual appliance. Its core job is reliable local collection and preparation. Operational control continues independently of the Pod.
- 01
Existing systems
Use approved historians, OT security tools, SAP, GIS and operational data feeds.
- 02
Industrial Edge Pod
Read, normalise, match asset identities and buffer locally. Retain data during uplink loss.
- 03
Controlled transfer
Validate and allowlist what may leave. Forward through an approved gateway when connected.
- 04
Shared intelligence
Bring relationships, risk assessments and evidence into the approved NeuroCluster environment.
- Read-only collection by default, through approved integration points.
- Source-owner limits on collection rate, storage and resource use.
- If a collector is overloaded, collection slows or stops; the operational source takes priority.
How is data collected?
Start with existing interfaces
Use approved APIs, replicas or exports from historians, asset systems, GIS and OT security tools.
Reuse passive discovery
Import assets and relationships from an existing, approved OT security sensor that observes network traffic.
Agree any protocol access separately
Use a dedicated read-only adapter only where needed and explicitly approved. Automated scanning and writes to production controllers are outside this collection design.
Which Pod fits the site?
Edge Collector
A compact appliance for collection, data preparation and local buffering.
Industrial Intelligence Pod
A larger appliance with more storage and agreed local analytics. Additional compute is sized to the workload.
Virtual Pod
The same collection software in an existing approved virtual environment or OT transfer zone.
For a first pilot, start with a Virtual Pod when an approved environment is available. Validate hardware, network separation and site conditions before selecting a physical appliance.
Design basis: OT Intelligence target architecture v1.0, 14 October 2026. Integration availability, offline operation, local analytics and hardware sizing are validated within the agreed pilot scope.
Who it’s for
Built around the decisions you own.
Grid operators
Which asset needs attention first? See condition, network impact and available capacity together.
Industrial partners
What could interrupt production? Connect equipment condition to the processes and sites that depend on it.
Infrastructure investors
What needs investment, and why? Review operational exposure, maintenance priorities and the evidence behind an asset assessment.
Pilot validation
From design to validated results.
The examples explain a possible decision. Each pilot must separately establish what data collection, local analysis and loss of connectivity can actually support.
No public pilot reports with validated results are published on this page yet. The architecture below is a target design; availability and performance are evaluated for each site.
What must a pilot demonstrate?
Data collection
Which sources and protocols were tested, with which permissions and on which equipment?
Local analysis
Which analysis actually ran on site, with what compute and measured quality?
Connection loss
How long did collection continue, what was buffered and how did recovery handle data loss?
Start small
One site. One decision. A clear way to measure value.
Agree a focused pilot before expanding. Product capabilities, integrations and deployment requirements are confirmed against your situation.
01
Choose the decision
Pick one asset group or workflow. Agree the owner, data access and the baseline you will compare against.
02
Connect the evidence
Link the relevant records. Agree how to assess likelihood, impact and uncertainty with your engineers.
03
Review the result
Measure investigation time, evidence completeness and decision quality against the baseline. Expand when the results justify it.
Start small
Start with a decision you need to get right.
Bring an asset, a site or an operational question. We will define a practical first step with your team.