Intelligence

Specialist intelligence. Evidence for the next decision.

Bring telemetry, alerts and maintenance history into the same investigation. Gen318 combines specialist analysis with Ask, an operator workspace that helps you follow the evidence and prepare a response for approval.

Specialist investigation · illustrationReasoning
Investigation traceNOT A LIVE RUN
DATA01

Freeze the site evidence snapshot. Record source age, trust and delivery coverage.

WEATHER02

Load available weather context for the investigation period.

HEALTH03

Assess battery and inverter indicators with model confidence and missing inputs.

DEMAND04

Bring the demand forecast into the same site investigation.

IMPACTREVIEW05

Rank findings using the supported operating context. Route uncertain evidence for review.

SYNTHESIS06

Preserve results and evidence. Optional grounded synthesis explains the findings; no equipment action is shown.

Specialist
Site analysis
Cited
Ask evidence
Reviewed
Action proposals
Recorded
Field findings
01 · The agents

Each one reads different instruments.

Each specialist reads a different part of the operating record: asset condition, demand, weather or reporting evidence. Together, they help explain which finding deserves attention and what supports it.

Battery Health

PHYSICS FIRST
Reads
Charge cycles, impedance, cell temps
Calls
Degradation vs expected · remaining useful life

Confidence depends on available evidence

Inverter Diagnostics

FAULT INDICATORS
Reads
Voltage / current signatures, efficiency curves
Calls
Fault indicators and risk estimates

Investigation, not a guaranteed failure date

Demand Forecast

FORECAST MODELS
Reads
Load history, weather, market calendars
Calls
Hourly → monthly load, with confidence bands

Context and history shape the forecast

Dispatch Planning

ADVISORY
Reads
Forecasts, tariffs, fuel price, battery state
Calls
A generation plan for review

Measured against the approved site baseline

Compliance

REPORTING
Reads
Uptime, power quality, connections, milestones
Calls
Reviewable programme evidence

Review before export and submission

Weather

NASA POWER + LOCAL MET
Reads
Irradiance, dust, rain, heat forecasts
Calls
Irradiance and weather context

Weather context for inspection and dispatch planning

02 · Compound learning

Evaluate the prediction against the field finding.

Match eligible predictions to recorded field findings to assess how well the model performed. Keep the inspection result, observation window and evidence gaps with the evaluation.

Physics and statistical models provide the starting point. Learned models need sufficient evidence and controlled deployment. The example shows how findings enter evaluation; model improvement must be measured.

Model evaluation

Compare the prediction with the field evidence.

Example—not measured model performance.

  1. 01 · Prediction

    An equipment-risk finding

    Keep the prediction and its supporting inputs.

  2. 02 · Field finding

    A recorded inspection

    Distinguish technician-reported findings from measured observations.

  3. 03 · Evaluation

    A comparison where supported

    Match eligible evidence. Missing or inconclusive evidence cannot establish success.

Match
connect the prediction to a recorded field finding
Evaluate
measure performance on eligible evidence
Review
improvement must be measured, not assumed
03 · Where the models run

The edge collects. The cloud connects context.

Commissioned edge nodes collect and analyse locally. Cloud services assemble site evidence and support investigation, reporting and model evaluation. Connectivity loss makes remote views stale; power, storage and configuration still matter.

At the site · edge nodeLOCAL
  • Local inference
    configured models analyse site readings
  • Local dispatch planning
    physical control has separate enablement and safety checks
  • Persistent buffer
    retry queued readings with priority synchronisation
  • Interrupted links
    power, storage and commissioning still matter
In the cloud · fleet brainANALYSES
  • Specialist analysis
    site evidence, health, demand and weather
  • Evidence snapshots
    retain inputs and results for review
  • Model evaluation
    eligible findings can be matched to predictions
  • Controlled rollout
    models and actions have distinct deployment controls
04 · Conversational operations

Ask the fleet why. It shows its work.

Investigate a site issue with telemetry, alerts and maintenance history in one console workspace. Follow the supporting records and prepare a response for approval. Ask is optional and uses controlled, permissioned tools.

Inspect a real Ask investigation →
  • Investigate with source records, coverage and freshness
  • Prepare a proposed response for authorised review
  • Check related alerts and work orders in the same investigation
  • Identify missing evidence before committing to a response
Gen318 Ask
Sample scenario · Synthetic data

Operator task · Riverside Industrial Solar

Review the completed source-data assessment and open inspection before preparing another visit.

Recorded Ask answer

The completed source-data review for the inverter found that the cause of the interruption remains undetermined, and recommends ongoing monitoring [WO:2649]. The outstanding item is to investigate the inverter’s output interruption, which is still open [WO:7809]. The saved proposal asks the operator to review the completed source-data assessment, check the inverter’s source readings, and confirm the cause before any repair is advised [WO:7809].

Create a medium work order at Riverside Industrial Solar: Carry out inverter inspection: reconcile open work order and confirm cause before any repair

EXPIRED · NOT APPROVED

Selected answer and proposal from separate turns of the same investigation, captured 8 September 2026. The proposal expired without approval; its accompanying answer was withheld by the grounding gate.

Inspect the captures and source record →
05 · The AI-native stack

Keep the decision chain intact.

Move from an investigation to a plan, then coordinate the response across the fleet. Keep the assumptions, approval and subsequent findings with each decision.

01 · Dispatch planning

Review the plan before changing the operation.

Compare dispatch options using demand, weather, battery and genset constraints before approving a plan. Inspect the assumptions behind each recommendation; equipment execution follows its own enablement and safety checks.

Dispatch scenarios · illustrationNOT A LIVE SIMULATION
Inputs
demand, weather and asset context
Assumptions
inspect constraints and missing evidence
Review
a plan is not an executed command
Fleet evidence · information flowReview

Fleet coordination. Information from each site supports a shared operating view.

02 · Fleet context

Connect the evidence across sites.

Compare site issues in a shared fleet view and coordinate the next response. Each site retains its operating context and permissions; the diagram shows information flowing into that view.

An approved proposal is not a hardware outcome.

Ask records an approved dispatch override. Equipment control follows a separate execution path with its own enablement and safety checks. Authorised operators review actions; the record must still show execution and subsequent observations separately.

03 · Operational response

Follow the issue through the response.

Closed-loop operations · incident WO-0151SEQUENCE
Detect
SITE SIGNALSOPEN

Related equipment alerts are grouped for investigation.

Review
OPERATORDECISION

Review the evidence and proposed response. Commands and approvals remain distinct.

Assign
FIELD TEAMWORK

Coordinate the work order and retain the technician's recorded findings.

Assess
EVIDENCECHECK

Assess attached records. Missing evidence remains visible.

Follow up
SUPERVISORREVIEW

Where enabled, review post-repair findings separately from field completion. Human review is not independent certification.

Follow detection, review, assignment and observed findings in one record. This is not an autonomous response or a measured resolution time.

04

Reviewable briefs

Prepare operating summaries from evidence bundles. Optional language-model assistance does not replace the underlying records or review.

05

Evidence packages

Keep field claims and attachments with their evidence assessment. Package integrity and evidence quality answer different questions.

06

Post-repair review

Where enabled, review the observed repair findings alongside the supervisor’s assessment. Keep successful, unsuccessful and inconclusive outcomes distinct.

Availability: Ask, AI actions, Operations Desk, post-repair verification and attestations must be switched on for your organisation and available to your role. Record integrity, repair findings and supervisor review are separate checks—not independent certification.

06 · Insight explorer

Review the issue with its evidence basis.

Rank issues using the supported impact basis and evidence available. Missing prices stay unpriced. Illustrations show how to read the context; they do not establish customer outcomes or universal financial rankings.

Profile · not customer measurements
This site Fleet median1 axis flagged
Investigation queueEXAMPLE
Plan

Review the generation plan against demand, weather and site constraints.

DISPATCH
Inspect

Assess a battery health finding with its evidence and uncertainty.

BATTERY
Check

Resolve missing readings before interpreting a reporting period.

COVERAGE
Follow up

Inspect the recorded cause and post-repair findings where available.

FIELD

Generation trend · not measured savings

Bring one site question to the demo.

We follow up to arrange a demonstration of investigation, supporting records and review.

Request a demo