MAHARASHTRA · E-BUS DISCUSSION CONCEPT

Command overview

COMMAND CENTRE · FLEET + CHARGING + POWER

Buses ready. Power visible.
Every issue with an owner.

Three depots in one command view.

Ring = readinessColumn = grid importWarning levelBuses on roadOpen incident
Drag to rotate · click a depot to focus · concept visual, not an operational deployment
Pune Depot | 05:15 | Next dispatch: 06:00
ILLUSTRATIVE DATA
DEPOT COMPARISON

Depots side by side

ACCOUNTABILITY

Priority incidents — owner, deadline, status

LIVE ACTIVITY

Event stream

Live
FLEET ACTIVITY

Dispatch readiness trend

% of buses at depot meeting the 80% charge target
Illustrative mobile app screen
POWER VISIBILITY

Depot grid import vs warning level

kW · synthetic
CHARGING OPERATIONS

Charger status

Selected site
LIVE SYSTEM TRACKING · DIGITAL TWIN

Live tracking — Pune Depot

A 3D digital twin of the depot with simulated GPS, charger (OCPP) and meter feeds. Positions and readings are synthetic and update with the simulation; nothing connects to real vehicles or equipment.

3D DIGITAL TWIN

Depot yard — buses, charging bays and power flow

ReadyCharging Needs attentionPower flow
Drag to orbit · right-drag or Shift-drag to pan · scroll to zoom · click a bus or charger
DIGITAL TWIN · SIMULATED
SELECTED ASSET

Live asset detail

SYSTEM HEALTH

Data feeds

LIVE GPS

Buses on route

Positions update continuously
TELEMETRY STREAM

Incoming packets

GPS · OCPP · METER · CAN
    ON-ROAD FLEET

    Trip progress

    BUS & DISPATCH READINESS

    Fleet readiness

    Every bus as a 3D column of its state of charge against the 80% dispatch target, with the projected charge at departure. Projections are rule-based (current SOC + charger rate), not AI. Battery data would need OEM telemetry; GPS alone does not provide it.

    3D SOC SKYLINE

    SOC skyline

    SELECTED BUS

    Readiness detail

    NEEDS ATTENTION

    Before departure

    FLEET STATUS

    Where every bus is

    DEPARTURES WAVE

    Next 3 hours

    SOC DISTRIBUTION

    Buses at depot by charge

    DISPATCH BOARD

    Next departures

    FLEET MATRIX

    E-buses by state of charge

    FLEET REGISTER

    Bus status register

    Click a row to focus the bus
    CHARGING INFRASTRUCTURE · 3D

    Charging hall

    Every charger with its live session, power and health. Equipment faults are shown separately from telemetry loss: a charger with stale data keeps its last known state and is flagged as a data-quality issue.

    3D CHARGING HALL

    Charging row

    ChargingReady FaultComms lost
    Drag to rotate · Pan or right-drag to move · scroll to zoom · arrow keys
    LIVE SESSIONS · SIMULATED
    SELECTED CHARGER

    Session detail

    POWER SHARE

    Who is drawing power

    SESSION TIMELINE

    Next 3 hours by charger

    Click a lane to focus the charger
    CHARGING BAYS

    Bay status

    Ring = bus state of charge
    QUEUE

    Buses waiting for a charger

    DEPOT ENERGY · 3D POWER FLOW

    Energy & power

    Follow every kilowatt from the grid and solar to the chargers and depot load. Grid import, solar, peak demand and substation values are synthetic; upstream telemetry would need utility permission.

    3D POWER-FLOW TWIN

    Power flow

    GridSolar ChargersBase load
    Drag to rotate · Pan or right-drag to move · scroll to zoom · click an asset to fly to it
    SUN FOLLOWS SIM TIME
    PEAK MANAGEMENT

    Demand vs warning level

    ENERGY TODAY

    Where the energy went

    POWER CONSUMPTION

    Grid import, solar and limits

    kW · synthetic
    DEPOT ELECTRICALS

    Grid import vs contract demand

    Tick = warning level
    HOURLY ENERGY

    Grid and solar energy by hour

    kWh · today
    POWERSENSE AI · SUBSTATION DEMO REFERENCE

    Upstream substation

    Open PowerSense demo ↗
    Scope boundary

    Substation load, transformer and feeder monitoring requires utility permission and confirmed LDMS / RTU / SCADA interfaces. Read-only monitoring is the default. Existing electrical protection stays outside this application, and no autonomous electrical switching is proposed.

    DETECT → ASSIGN → ACT → VERIFY

    Turn an alert into an accountable response

    Rules detect exceptions and route them to an owner with a response deadline. The owner records an action, and closure needs evidence. Buttons only update local simulation records.

    OWNED INCIDENTS

    Response and closure register

    Safety & evidence

    Actions, assignments and closures are a simulated audit trail. Real chargers, vehicles and electrical assets are never controlled by this page. Any permitted control would need OEM support, authorisation and approved safety procedures.

    PILOT KPI SCORECARD

    Measure before making claims

    The six scorecard measures from the briefing, calculated from simulated data. Pilot outcomes would be compared with an agreed baseline; no savings or improvement is assumed.

    DRAFT PILOT ACCEPTANCE GATES

    Gate status

    DATA QUALITY

    Telemetry completeness by source

    Received / expected records
    DISPATCH

    Readiness time series

    GRID DEMAND

    Power demand time series

    KPI DEFINITIONS

    Agree the measurement rules before the pilot starts

    Telemetry qualityReceived records / expected records at agreed intervals; missing and stale data reported separately. Draft gate: 98%+.
    Alert workflowScripted critical scenarios: detect, route, assign, escalate and close with a timestamped audit trail. Draft gate: 100% pass.
    Dispatch readinessBuses meeting dispatch charge target / buses scheduled at the agreed cutoff. Target fixed jointly after baseline.
    Charger availabilityFunctional charger minutes / service window. Equipment fault is distinguished from communication loss.
    Incident responseAcknowledgement and closure timestamps by owner; adherence to agreed response windows.
    Energy cost / kmAgreed electricity cost allocation / matched operated km for a stated meter and cost boundary. Reconcile before any savings claim.
    SOURCE BRIEF · PILOT BOUNDARIES

    Prove one depot before deciding to expand

    The briefing proposes a focused one-depot pilot. Pune Depot in this simulator mirrors that scope. Nagpur and Nashik depots are an illustrative scale view only; expansion would need a separate decision.

    20–50E-buses
    5–10Chargers
    1 depotPower + energy monitoring
    1 substationSubject to utility approval
    01 · DISCOVERY~2 weeksSurvey, access matrix and baseline plan
    02 · INTEGRATE~6–8 weeksConnect data, app, dashboard and alerts
    03 · VALIDATE~2 weeksOperate, train, test and review results

    Indicative 10–12 weeks after access, site readiness and approvals are in place.

    DELIVERY READINESS

    Demo reference, pilot scope and later AI

    DEMONSTRATION REFERENCEPowerSense AISubstation monitoring demo
    PROPOSED PILOT INTEGRATIONFleet + charging + powerSubject to OEM / data access
    AFTER OPERATIONAL VALIDATIONPredictions + optimisationRequires reliable history

    Initial pilot: monitoring, rules and operator-led action. No autonomous electrical switching or vehicle dispatch is proposed.

    INTEGRATION DEPENDENCIES

    Data sources and safeguards

    Bus systemsGPS / telematics + dispatch system; OEM interface for battery metrics
    ChargersCharger OEM APIs / OCPP (Open Charge Point Protocol), if supported
    Depot powerMeters, gateways and available site feeds; field survey required
    SubstationLDMS / RTU / SCADA only with agreed utility permission
    SafeguardsLeast-privilege roles, encryption, audit trail, local buffering, agreed hosting, backup and recovery
    SCOPE AND READINESS

    What is proposed, and what must be validated

    MODULEPROPOSED SCOPEDEPENDENCYREADINESS POSITION
    FleetGPS, routes, service status, available battery dataTelematics + dispatch feedsIntegration to validate
    ChargingAvailability, charge sessions, faults, energy and queuesCharger APIs / OCPP supportIntegration to validate
    Depot energyGrid / generation, loading, peak demand and consumptionMeters, gateways, source feedsSite survey required
    PowerSense AISubstation load, equipment status, alarms and local viewUtility permission + field dataDemo reference
    AI / optimisationReadiness prediction, anomalies, maintenance and load planningReliable history + signed testsPhased roadmap
    GOVERNANCE

    Who is accountable?

    Department / operatorNodal officer, depot access, dispatch data and acceptance
    AlphansoSoftware, integrations, app, alerts and application support
    OEM / electrical partnersDevice data, field work, safety and hardware support
    COMMERCIAL CONTROL

    How the pilot is costed

    One-timeSoftware, integration, testing and training
    ConditionalMeters, gateways, networking and field installation
    RecurringHosting, connectivity, support and agreed maintenance
    QuotationItemised after site survey; no cost figure assumed. Department-controlled data access with agreed hosting, export and exit terms.
    REQUEST FOR DIRECTION

    Jointly scope a focused Maharashtra pilot

    1. 1Nominate a nodal officer and operator team.
    2. 2Select one depot and facilitate OEM / utility access.
    3. 3Permit joint scoping and review the pilot proposal.

    Today's request is for structured evaluation, not a statewide rollout commitment.

    PowerSense AISubstation demo referencepowersense.alphanso-ai.in ↗
    Content separation

    The source is a ministerial discussion proposal by Alphanso Technology. Depot operating data, bus and charger IDs, routes, energy values, incidents and charger states in this interface are invented for demonstration. No operational deployment, live integration or statewide rollout is claimed.