Read-only by design
One-way connection out of the control network. Helm never writes to the DCS, the SCADA or the historian.
The digital backbone of modern power generation.
Helm connects plant knowledge, shift records and live signals into one operating picture. Every answer cites its source.
One plant.
A thousand signals.
Trends live in the historian, procedures in binders, context in the last shift's memory. Helm brings them into one structure your team can question.
- Control systemDCS, SCADA, historian
- Plant documentsManuals, P&IDs, procedures
- Shift recordsLogbook, handovers, dispatch
- Cited answersDocument, revision and page
- Alarms with contextCause, evidence, next check
- Signed handoversStatus, events, pending items
Follow one signal through Helm.
At 04:18 the exhaust spread on GT-01 starts to climb. Five modules pick up the same event, each from its own angle.
Helm Watch
See the deviation before the alarm.
A read-only connection to DCS, SCADA and historian. Every live value sits against the range Helm expects for that unit.
- Live values and trends inside the conversation
- Expected ranges learned from each unit's history
- Frozen or uncertain signals flagged, never hidden
37.8 °C↑ 0.6 °C/minExpected 8-30 °C
Observed Projected Expected range Alarm high 45 °C
Thermocouple TC-07. No variation since 04:18. Excluded from the spread calculation.
Helm Events
Turn an alarm list into a sequence.
Helm orders what happened, explains each alarm in its operating context and lays out probable causes with their evidence.
- First-out and ordered cascade
- Cause hypotheses, each with evidence and confidence
- Permissives still missing before a restart
- Spread leaves its expected rangeDetected by Helm
- TC-07 without variationSignal quality
- EXH SPREAD HIGHDCS alarm, priority 3
Next check. Adjacent thermocouples TC-06 and TC-08 against load. One hypothesis open, two sources.
Helm Knowledge
Every answer cites its page.
Ask by voice or text. Helm answers from your manuals, drawings and procedures, and separates what is written from what is deduced.
- OEM manuals, P&IDs, procedures and alarm lists, indexed by revision
- Questions in Spanish over manuals written in English
- Without evidence, Helm says it does not know
■ Observed
A spread above 45 °C at stable load calls for the exhaust spread investigation procedure.
POP-GT-014 Rev. D, p. 3◐ Inference
TC-07 has not varied since 04:18, so part of the reading may be a measurement fault.
GT-01 manual 6.2, p. 148 Historian 04:10-04:45◌ Hypothesis, not confirmed
Non-uniform combustion in the TC-07 zone.
Medium confidenceHelm Shift
Dictate the logbook. Sign the handover.
Operators log by voice. Helm files each entry with time, unit and type, then drafts the handover from the shift's events.
- Voice logbook, exportable to the plant's own format
- Dispatch requests, starts and stops recorded for start KPIs
- Handover with unit status, open events and pending items
- ObservationExhaust spread rising at stable load.GT-01, dictated by J. Rivas
- RequestI&C to check TC-07 wiring.Linked to EV-2026-0412
- DispatchGrid operator requests hold at 142 MW.Unit 01
Handover approved at 05:52. Seven of seven sections reviewed, one open event, two pending items for Shift A.
Helm Insights
Learn from every shift.
Performance, trends and recurring events across units and periods, with predictive models for the failure modes that matter to your plant.
- Alarm load and recurring events by system
- Start reliability and dispatch indicators
- Failure-mode models validated with your team
- Exhaust
- 47 / 31
- Lube oil
- 18 / 22
- Fuel gas
- 12 / 9
- Vibration
- 7 / 11
- Generator
- 4 / 6
Last 30 days Previous 30 days
Copilot, not autopilot.
Helm reads, explains and records. Plant teams review the evidence and decide what happens next under their own procedures.
))
Inside your perimeter
Documents, signals and language models run on a server in the plant, segmented in line with IEC 62443.
- ■ Observed Stated in a document or a signal
- ◐ Inference Deduced from two or more sources
- ◌ Hypothesis Possible, not confirmed
Nothing is a black box
Every answer, alert and hypothesis is recorded with its evidence, its confidence and the operator's decision.
Your data stays yours
The knowledge base and records belong to the plant, in open formats. Never used to train third-party models.
OPC UAPISQL
Adds to what you run
Helm works with your historian and existing tools. It does not replace the control system or the CMMS.
In service in month two.
A field specialist surveys the plant, Helm ingests its documentation, and operators start using Knowledge and Shift. Live data follows.
- Month 1Survey and ingestion
Five days on site. Server installed, documents ingested, KPI baseline set.
- Month 2Knowledge and Shift
Voice logbook, handover and cited answers in the control room. Team trained.
- Month 3Integration
Ten days on site. Read-only connectors, tag mapping, alarm list loaded.
- Month 4Watch and Events
Alarms with context, event assistance and handovers that carry live data.
- Month 5Validation
Daily use by operations and maintenance, tuned on real events.
- Month 6Results
KPIs measured against the baseline and a continuity plan.
Bring your plant into the conversation.
Outline the assets, workflows or operating questions you'd like to cover in a Helm demo.