AMPERE Training Manual

Authenticate with your work email and password.

1. 01

   Open the sign-in page

   Navigate to the AMPERE URL provided by your administrator and select Sign in. Enter the work email address your invitation was sent to.

2. 02

   Accept your invitation (first time only)

   New users receive an invitation link by email. Opening it lets you set your password before first sign-in. Invitation links expire — ask your administrator to re-send if yours has lapsed.

3. 03

   Complete two-factor authentication

   If your organisation enforces 2FA, you will be asked for a 6-digit code from your authenticator app after entering your password. Enter the code to continue.

Understand what your role allows you to see and do.

1. 01

   Know your role

   AMPERE roles include Organisation Admin, Executive, Loss Control Officer, Asset Engineer, Capital Planner, Regulator Analyst, Field Supervisor and Platform Admin. Your sidebar only shows the modules your role can access.

2. 02

   District scoping

   Some roles are scoped to specific districts. Scoped users see only submissions, assets and analytics for their districts; actions outside that scope are rejected by the server, not just hidden.

3. 03

   Request changes through your administrator

   Role and scope changes are made in Users & Access by an Organisation Admin, and every change is recorded in the audit log.

The executive snapshot: headline KPIs, loss trend, alerts and regional comparison.

1. 01

   Read the KPI band

   The top band shows the organisation’s headline metrics — energy input, billed energy, loss percentage, collection rate — for the current period, each with its trend against the prior period.

2. 02

   Act on Lumen signals

   Predictive signals from Lumen (the AI assistant) surface anomalies worth attention, each with a severity and an evidence link into the relevant module.

3. 03

   Drill into a region

   Selecting any region in the comparison table opens its dedicated page with district-level breakdowns.

Navigate the operational hierarchy from region to district to feeder.

1. 01

   Compare regions

   The regions grid ranks every region by loss %, collection rate and outage load so under-performers stand out immediately.

2. 02

   Open a district

   Each district page shows its feeders, transformers, loss profile and active field work in one place.

Ask questions about your network in plain language and receive evidence-backed answers.

1. 01

   Ask a question

   Type a question such as “Which feeders had the largest loss increase this quarter?”. Lumen answers using live platform data and cites the modules it drew from.

2. 02

   Follow the evidence

   Every Lumen claim links back to the underlying dashboard or record so the analysis can be verified, never taken on faith.

Localise technical, commercial and collection losses to feeder, transformer and customer level.

1. 01

   Read the energy balance

   The waterfall chart tracks Energy Input (BSP) through technical losses, commercial losses and the collection gap to revenue-realised energy. Source badges show which stages are measured versus modelled.

2. 02

   Drill down the hierarchy

   The drill-down table walks District → Feeder → Distribution Transformer. Click a DT row for its detail: energy in, energy billed, loss %, loss value and 6-month trend.

3. 03

   Filter to what matters

   Use the Region and Feeder filters, the minimum loss % slider and the “Only anomalies” toggle to isolate the worst cases.

4. 04

   Check Network Topology and Trends

   The Network Topology tab shows losses on the physical network; the Trends tab decomposes technical vs commercial vs collection losses over 24 months as a % of energy input.

Track billing integrity, detect suspected theft and manage revenue-recovery cases.

1. 01

   Review the assurance funnel

   Follow billed → collected → recovered amounts and identify where revenue leaks.

2. 02

   Work the case queue

   Suspected theft and under-billing cases carry an evidence trail and a status; progress them as investigations conclude.

Customer-level consumption, billing history and payment behaviour.

1. 01

   Search for a customer

   Look up customers by account number, name or meter. The profile shows tariff class, consumption history and payment record.

2. 02

   Spot consumption anomalies

   Sudden drops in billed consumption against a stable feeder profile are classic meter-tamper indicators and are flagged on the profile.

Geographic view of the network with live energy accounting overlays.

1. 01

   Navigate the map

   Pan and zoom to any region. Layers toggle substations, feeders, transformers and customer clusters.

2. 02

   Read the energy accounting chain

   The side panel tracks energy input at BSP through each network level, with GWh input and revenue-realised figures.

The canonical inventory of substations, feeders, transformers and service points.

1. 01

   Find an asset

   Filter by type, region, district or condition. Each asset page carries its identity, position, ratings, condition history and linked field submissions.

2. 02

   Verify positions

   Assets carry a position status (verified / unverified / conflicted). Field surveys captured on the mobile app update positions subject to the review workflow.

3. 03

   Use Asset Mapping

   The mapping tool (Assets → Mapping) reconciles imported records against field captures so duplicates and orphans are resolved deliberately.

Condition monitoring: overloaded transformers, ageing assets and thermal stress.

1. 01

   Review the health ladder

   Assets are banded by condition. Work the critical band first — these carry both outage and loss risk.

The metering fleet: coverage, communication health and data quality.

1. 01

   Check coverage

   Coverage tiles show what share of each network level is metered versus modelled — the foundation of loss-figure confidence.

2. 02

   Chase silent meters

   Meters that stopped communicating are listed with last-heard timestamps; prolonged silence on high-value points warrants a field visit.

Live outage board with affected customers, crews dispatched and restoration progress.

1. 01

   Triage by impact

   Outages rank by customers affected and duration. Each carries its feeder, cause category and crew assignment.

2. 02

   Track restoration

   Status moves through reported → crew dispatched → isolated → restored, stamping times for SAIDI/SAIFI reporting.

Planned and corrective work: creation, assignment, tracking and closure.

1. 01

   Create and assign

   Raise a work order against an asset or location, set priority and assign to a crew.

2. 02

   Close with evidence

   Completion requires the closing record — what was done, parts used and any follow-up required.

The field data programme: mobile captures, the review queue and crew management.

1. 01

   Understand the capture flow

   Crews capture surveys, verifications, investigations, maintenance records, commissionings and hazards on the AMPERE mobile app — offline-first, with GPS and photo evidence — and sync when connected.

2. 02

   Work the review queue

   Synced submissions appear in the review queue. Reviewers with a configured reviewer role approve or return each submission; returning work to a crew requires a note explaining why (when the workflow demands it).

3. 03

   Respect auto-approval

   If your organisation has enabled auto-approve for a submission type, high-quality captures (tight GPS accuracy, sufficient photos, no data conflicts) approve automatically at sync and never reach the queue. The review note records the reasons.

4. 04

   Watch the SLA

   Pending submissions older than the configured SLA hours are flagged as breaches — clear them first.

SAIDI, SAIFI and CAIDI tracking against regulatory targets.

1. 01

   Monitor the indices

   Reliability indices are computed from the outage record and tracked monthly against PURC benchmarks, by region and feeder.

Rank candidate investments by loss-reduction return.

1. 01

   Review ranked interventions

   Candidate projects — reconductoring, transformer replacement, metering rollouts — are ranked by expected loss reduction per cedi invested.

2. 02

   Build a portfolio

   Assemble a budget-constrained portfolio and export the justification pack for board or funder review.

Data quality workbench: completeness, freshness and reconciliation across sources.

1. 01

   Check source health

   Every inbound source (billing, metering, GIS, field capture) is scored for completeness and freshness. Investigate any source showing drift before trusting downstream analytics.

Generate regulator-ready filings from live data.

1. 01

   Generate a filing

   Select the filing type (EC, PURC or Ministry format) and period. The pack is assembled from live platform data with every data point labelled with its source and freshness.

2. 02

   Review before submission

   Each pack lists its data points — for example “Energy input at BSPs — Grid metering feed — live” — so the signatory can verify provenance before filing.

Cross-utility sector picture: losses, reliability and collection across licensees.

1. 01

   Compare licensees

   Utilities are compared on the standard metric set, all computed from the same data standard so figures are genuinely comparable.

Each institution’s statutory view with its own metric emphasis.

1. 01

   Use your institution’s console

   The EC console emphasises licensing and technical standards; PURC emphasises tariffs, reliability and service quality; the Ministry console emphasises sector policy outcomes.

2. 02

   Trace any figure

   Every number links to its definition in the Data Standard and to the underlying evidence trail.

The canonical metric definitions all parties compute against.

1. 01

   Reference the standard

   Each metric carries its formula, scope, unit and validation status. Disputes about a figure start (and usually end) here.

Invite users, assign roles and district scope, revoke access.

1. 01

   Invite a user

   Send an invitation to a work email with a role and (optionally) district scope. The account activates when the invitation is accepted.

2. 02

   Change or revoke access

   Role changes take effect immediately; revocation ends active sessions. Both are audited.

The tamper-evident record of every material action on the platform.

1. 01

   Filter and investigate

   Filter by actor, action type and period. Review decisions, configuration changes, access changes and sign-ins are all recorded.

Configure how field submissions move through review, per submission type.

1. 01

   Set reviewer roles

   Choose which roles may approve or return each submission type. Organisation Admins can always decide.

2. 02

   Configure auto-approval

   Optionally auto-approve high-quality captures at sync: set the maximum GPS accuracy, minimum evidence photos, and whether data conflicts block auto-approval.

3. 03

   Set return policy and SLA

   Decide whether returning work requires a note, and set the SLA hours after which pending work counts as a breach.

Metric definitions, security policy and local terminology.

1. 01

   Maintain the metric dictionary

   Edit metric names, definitions and scope; every edit writes an audit line. Definitions should track the sector Data Standard.

2. 02

   Set security policy

   Password rules, 2FA enforcement and session length are set under Settings → Security.

3. 03

   Localise terminology

   Terminology settings adapt platform vocabulary to your organisation’s conventions.