Disconnected systems slow decisions and field response.
Equipment dashboards, fuel spreadsheets and field messages tell separate parts of the story. Teams lose time piecing them together to find the issue, coordinate the work and confirm what changed.
Can you explain a missed service target?
An uptime figure alone does not explain an outage. The reviewer also needs the period, operating conditions and gaps in the source data.
Did fuel use improve—or did demand change?
A lower fuel total can reflect lower demand, more solar or incomplete records. Without a site-specific baseline, the saving is hard to defend.
Why does every report start from scratch?
Equipment readings, maintenance notes and spreadsheets tell separate parts of the story. Someone has to reconcile them before the client or board can review it.
Was the fault fixed—or just the ticket closed?
A closed job records that work ended. Without field findings and follow-up evidence, the next shift may still not know whether the problem remains.
Know what is happening across your sites.
Bring supported equipment readings into one view to spot changes and decide where to investigate. Freshness and coverage checks help distinguish an equipment issue from a gap in the data.
Offline-first edge — stores readings locally and retries sync after interrupted links
One metric vocabulary — brings supported equipment into a shared fleet view
Delivery and trust checks — distinguish missing readings from readings that arrived but need scrutiny
Visible freshness — shows when the cloud record is stale while an edge node is disconnected
A gap stays a gap. It is not silently treated as zero.
Illustrative fleet record. Hatching marks readings backfilled after a link came back.
From a site signal to a decision you can explain.
See what needs attention, investigate the cause and coordinate a response. Keep the supporting records with the work, so the next review starts with evidence.
- 01 · Observe
A site issue in context
- 02 · Investigate
An explanation with evidence
- 03 · Respond
Assigned work and field findings
- 04 · Review
A verified outcome
Which site needs your attention?
Start with related alerts and site readings in one view. Separate an equipment warning from a stale connection before deciding what to investigate.
Identify what needs attention and what to investigate next. Keep the affected site, supporting signals and visible data gaps together as you work through the issue.
Turn the decision into work someone owns.
Assign a work order with the issue and its supporting context. Technicians return findings and evidence, giving the operations lead a record to assess.
A closed ticket isn't a fixed fault. Gen318 keeps the technician's findings, the post-repair readings and the supervisor's sign-off as separate records, so you can see whether the repair held.
Where would you start?
Start with the operating question your team needs to answer. Explore the relevant workflow before expanding the scope.
Are we meeting our service obligations?
Bring uptime, energy and reporting-period completeness into the client review. Programme participants can prepare Odyssey-compatible exports with their site evidence.
Client uptime reports · Portfolio evidence · Programme exports
What should we plan for the next operating period?
Use demand, weather, battery and genset context to assess dispatch recommendations. Compare diesel use against an approved site baseline so the saving is one you can defend.
Dispatch recommendations · Demand forecasts · Fuel evidence
Which asset needs closer investigation?
Battery and inverter analysis flags degradation and fault indicators early. Field findings are recorded against each warning, so you can see how often the model was right.
Asset health · Fault investigation · Recorded outcomes
Bring your priority to a focused walkthrough.
Request a demoWhat you’ll see in a walkthrough.
Make the first site useful. Scope it before expanding.
Choose the scope
One question, one starting site
Identify the equipment, people and operating question to cover. Agree what a useful review would need to show.
Check the inputs
Access, mappings and history
Review vendor permissions, available signals and connectivity. Confirm which connection paths fit the equipment.
Establish the basis
Coverage before conclusions
Inspect delivery, trust and missing history. Set the relevant baseline and reporting period before interpreting comparisons.
Agree the workflow
Roles, review and enablement
Confirm who investigates, assigns work and reviews evidence. Scope optional Ask or control capabilities separately before use.
Your team brings
Equipment context and the people who use it.
- A site and equipment list, with models, firmware and the measurements you need.
- Someone authorised to arrange vendor API access or local commissioning, alongside an operations or maintenance lead.
- Available operating history, work records and relevant service terms. Report dates, missing periods and existing fuel baselines help define a useful comparison.
Scope with Gen318
A connection path and a useful first output.
- Confirm whether a supported cloud connection supplies the required data, or whether local collection needs an edge node and device mapping.
- Agree the workflow, responsible roles, configuration and output to inspect: an investigated issue, a maintenance record or a period report.
- Set the deployment scope and schedule after checking access, commissioning, data history and review requirements.
Start with one site and one question. Expand when the first answer is useful.
Check connection requirements before an enquiry →Build on your existing systems. Keep their role.
Connect supported equipment and portals after checking model, access and signal coverage. SparkMeter remains the metering and billing partner; Odyssey remains the programme platform.
AI that helps you investigate. Evidence you can follow.
Bring asset health, alerts and forecasts into the same investigation. Ask helps you explore the supporting records and draft a response; authorised operators review proposals before an action is taken.
Ask drafts; your authorised operators decide. Equipment control is a separately enabled, safety-checked path.
Explore Ask and reviewed proposals →Illustrative investigation
“What should we investigate at this site?”
- 01 · Specialist analysis
Review alerts, asset condition and the available operating context.
- 02 · Ask
Explore the supporting records and identify what is still uncertain.
- 03 · Reviewed proposal
Draft a work order for an authorised operator to assess.
Battery Health
Estimates degradation and remaining useful life to inform maintenance review.
Inverter Diagnostics
Connects fault indicators to a diagnosis worth investigating.
Demand Forecast
Builds a demand forecast to support the next operating plan.
Dispatch Planning
Prepares recommendations for operator review.
Performance Reporting
Generates Odyssey or C&I uptime reports from the same evidence trail.
Weather
Helps explain generation changes with irradiance and weather context.
Intelligence at the edge. Even without internet.
Site nodes keep collecting and analysing when the link drops, then sync critical records first when it returns. The cloud view tells you exactly how stale it is.
Learn from recorded outcomes.
Every technician finding and repair outcome is matched back to the prediction that triggered it, so your fleet's own history sharpens the next warning.
Connect operating results to the decisions and work behind them.
Review a site-specific diesel comparison
Compare fuel and runtime against an approved site baseline under the actual operating conditions, so a diesel saving is one you can put in front of a client.
Give each reviewer the right output
Give clients an uptime report and capital reviewers a scoped portfolio record. Every figure carries its period, coverage and calculation basis.
Review what happened after the repair
Evidence packages keep the field record, the post-repair readings and the supervisor's review together, so you can show what was done and what happened after.
Bring the question you need answered.
Request a demo around your priority: site response, service performance, maintenance evidence or portfolio review.