Frequently
Asked
Questions

Gen318 connects equipment telemetry, AI-assisted investigation, field work and performance reporting for mini-grid and C&I teams. It preserves the operating context from a site issue through the response and subsequent review.

Operators and O&M teams prioritise issues, investigate and coordinate field response. C&I asset owners and ESCOs oversee equipment, energy use and maintenance. Authorised investors and lenders review assigned-portfolio risks and supporting evidence. Technicians use a separate field PWA.

Specialist analysis combines telemetry, weather, asset health and demand context. When enabled, Ask investigates authorised records through controlled tools, cites evidence and can draft reviewable actions. Ask, its provider and its action features require deployment enablement and are off by default.

Ask records an approved dispatch override. Equipment control follows a separate execution path with its own enablement and safety checks. Approval alone does not establish command delivery or an observed equipment change. Physical control requires compatible equipment and is off by default.

Supported cloud adapters include Victron VRM, SparkMeter, Koios, Huawei FusionSolar and Growatt ShineServer. Local edge adapters provide additional paths including Modbus and SunSpec. Confirm account permissions, equipment model, firmware and signal mappings during setup.

A commissioned edge node can store readings locally and retry synchronisation when connectivity returns. The cloud view remains stale while disconnected. Storage, power and retention settings matter. Technicians can queue updates to cached jobs offline, with completion pending until the server accepts it.

Read delivery coverage and trust coverage together. Delivery measures what arrived against the expected stream; trust measures the validity of what arrived. Silent signals, source age and provisional periods are also visible. These checks do not independently verify a sensor’s physical accuracy.

No universal savings percentage or warning period is claimed. Predictions depend on data maturity and equipment conditions. Diesel comparisons require sufficient fuel evidence and an approved site baseline; monetary estimates require a site price.

Gen318 prepares operator-side site evidence, reports and Odyssey-compatible exports. Review milestone settings and amounts against the site’s current programme terms before finalisation. Automatic submission requires enablement and quality gates; programme acceptance and verification remain external.

Reporting preparation maps authorised operating and commercial records to Schedule 4 fields, with missing data and review decisions visible. Loss evidence requires defined electrical boundaries and meter records; technical estimates need a reviewed engineering study. Settlement evidence uses gross PCC imports and exports, approved agreements and effective tariffs; it also counts the dispute and payment windows from the invoice receipt you record, splits disputed from undisputed amounts, and prepares a dispute notice that you review and serve. Jurisdiction, exactly-1-MW cadence, regulatory filing, independent verification and counterparty acceptance require separate confirmation.

No. A completed job records the work reported. Evidence assessment shows its supporting records and gaps. Where enabled, post-repair evaluation checks signature clearance and recurrence over a stated observation window; insufficient evidence can leave the result inconclusive. Separately enabled owner/admin review records acceptance or dispute and the reason. Record integrity, observed outcome and human review remain distinct; none provides independent certification.

Investors can review their assigned portfolios and reports. Final reports can be shared through controlled, expiring links. Revenue estimates are energy-times-tariff proxies; collections and debt-service coverage are not measured. Investor membership does not grant access to Ask or operational controls.

Scoped read APIs, exports and event webhooks are implemented but require deployment enablement, entitlement and configuration. Discuss the data scope and downstream recipient during integration planning.

Review demand forecasts alongside recorded site and assigned-depot stock. Sourcing advice can indicate transfer, purchase or an unknown stock position; depot availability is separate from allocation. Track transfers through dispatch, transit and receipt. Forecasts depend on sufficient history, and missing stock records remain unknown.

A weekly and monthly statement of what each site delivered, in the units its sources measure. Every figure carries one grade: measured, modelled, estimated, declared, unpriced or insufficient. Naira appears only from a recorded contract or site tariff, or from diesel days above the confidence floor; a missing source is graded insufficient, never shown as 0. Each line is a site outcome, an adopted recommendation (a count, never a saving) or a platform-enabled action with confirmed execution. Investors read external lines only. A provisional statement is followed at least seven days later by a final that is frozen and hash-chained to the previous final. The value ledger and its weekly summary require enablement.

The Guide is in-console help built from reviewed help cards. It suggests what needs you and why, opens prepared forms with values Gen318 already holds, runs page tours and previews, answers product questions through a claim-checked chat, gives technicians help that works offline in the field app, and lets owners set goals on value-ledger figures. It never supplies a value only you can declare and never submits a form for you; it explains and suggests, and never changes anything. The Guide, its chat and goals require enablement.

Request a demo around a question about sites you operate, own or oversee. Walk through the relevant investigation, work order or report using clearly labelled demonstration data. Agree any use of your own data, access scope and deployment needs with the team first.