More consistent network records
Typed assets, units and connection rules help teams identify incomplete or incompatible records before they affect analysis.
MAPMYINDIA · UTILITY OPERATIONS
A connected view
of every utility.
Plan networks, assess service impact and guide field work across web, Android and iOS with Mappls maps and utility-specific engineering workflows.
Power, water, gas, telecom, wastewater, stormwater and district heating.
7utility domains
10work modules
4guided roles
Mapplsmaps and location services
THE WORK IT SUPPORTS
One record connects
the office and the field.
Keep equipment, connectivity, engineering evidence and work history together. Each decision starts with an identifiable asset and a known network revision.
Clearer service impact
Trace the services that depend on equipment, including recorded dependencies between utility networks.
Reviewable engineering work
Retain proposed designs, quantities, assessment results and recorded decisions through a controlled workflow.
Evidence for field handovers
Link checklists, measurements and inspections to the equipment revision and the person’s software role.
UTILITY COVERAGE
Each network has
its own engineering context.
Shared workflows support collaboration. Utility-specific models preserve the differences that matter to engineers.
Power
Know which assets and services depend on a feeder.
Voltage and phase validation, source tracing, transformer loading and electrical current screening.
Water
Understand supply paths and DMA boundaries.
Ring supply, valve isolation, pipe velocity, Hazen–Williams head loss and a period water balance.
Gas
Connect pressure records with integrity and service impact.
City gates, regulators, valves, MAOP checks, leak observations and connectivity isolation.
Telecom
Plan fibre services against available physical capacity.
Continuous strand allocation, endpoint ports, optical loss budgets and disjoint protection checks.
Wastewater
Follow collection flows to receiving works.
Directed traces, invert slope, accumulated flow and Manning full-pipe capacity screening.
Stormwater
Relate catchments to drainage capacity.
Rainfall intensity, rational runoff, receiving outfalls and maintenance observations.
District heating
Connect thermal demand with the circulating network.
Supply and return temperatures, mass-flow screening, heat loss and service dependencies.
THE PLATFORM
Ten modules for
the utility work cycle.
Every section includes an objective, responsibility, work steps and expected output for the signed-in role.
District overview
A shared picture of the district
Compare assets, open incidents, engineering flags and essential-service dependencies.
Network explorer
An asset register with geographic context
Search equipment, inspect connected segments, edit typed records and navigate with Mappls.
Engineering workbench
Explain how the network is connected
Trace sources and outfalls, apply barriers and inspect screening results with explicit units.
Incidents & isolation
Assess disruption before a reviewed response
Evaluate alternate paths, critical customers and cascading dependencies across utilities.
Fibre provisioning
Allocate capacity with a recorded service plan
Find feasible routes, check optical margin and reserve or release available strands.
Design & quantities
Keep proposals distinct from operating assets
Create revisioned drafts, review quantities and entered rates, then approve and commission.
Field operations
Tie work completion to asset evidence
Assign utility checklists, capture inspections and synchronize an offline inspection outbox.
Observations
Give readings an asset, unit and time
Record measurements, review exceptions and hand abnormal observations to an engineer.
Excavation review
Review shared corridors across utilities
Screen an alignment by distance and nominal depth, then retain an internal review record.
Data & integrations
Reconcile the network and retain its history
Validate GeoJSON, export inventory and analysis, and verify the change audit chain.
CROSS-UTILITY CONTEXT
A power incident can affect more than power.
A recorded transformer dependency can affect a gas regulator or a telecom exchange. The incident workspace shows the affected services and critical assets together so teams can prepare a coordinated handover.
Read the incident workflow ↗
ROLES AND GUIDANCE
The next step is clear
for each member of the team.
Operations administrator
Set review ownership, examine evidence, approve controlled changes and oversee the audit record.
Network engineer
Maintain verified records, investigate flags, prepare designs and allocate work or fibre capacity.
Field engineer
Identify assigned equipment, execute checklists and synchronize condition and measurement evidence.
Operations viewer
Review and export evidence, track progress and hand questions to the responsible owner.
Inline guidance supports an organisation’s approved SOPs. Role access in software does not confer authority to operate equipment.
FIELD CONTINUITY
Prepare online.
Capture in the field.
Reconcile on return.
Android and iOS native field apps bring downloaded assets, work checklists, GPS/photo inspections and utility measurements to the crew. An encrypted outbox retains evidence until synchronization; revision conflicts stay available for review.
Engineers and managers can also open all ten modules through the integrated online workspace inside each app.
Native apps are in pilot validation. Company signing and physical-device acceptance precede distribution. Mappls basemaps and engineering calculations require connectivity.
PRODUCT RESOURCES
Evaluate the platform.
Prepare your team.
Read the capability overview, discuss the product with stakeholders and use the operating guide to plan a pilot.
PPTX · USER MANUAL
Mobile app manual
54 illustrated slides covering native field tasks, role permissions, offline evidence and sync.
Download mobile manual ↗PPTX · USER MANUALWeb app manual
61 illustrated slides covering all ten modules, approvals, evidence and practice exercises.
Download web manual ↗PPTXProduct presentation
Release 0.5: web, Android and iOS capabilities, benefits and pilot approach.
Download presentation ↗PDFProduct datasheet
Release 0.5: utility coverage, native field workflows and delivery scope.
Download datasheet ↗USER GUIDEUtility operations guide
Objectives, definitions, responsibilities and software walkthroughs.
Read the guide ↗PILOT PLANNING
A pilot built around your network.
Start with an agreed operating area
Reconcile surveyed assets and connectivity, agree review owners and validate a small set of representative workflows before extending coverage.
Connect licensed services as required
Mappls maps, reverse geocoding and navigation provide geographic context. mGIS, telemetry, billing, ERP and workforce integrations require tenant access and project-specific data contracts.
Understand the analysis boundary
Engineering calculations provide screening and connectivity analysis. Specialised hydraulic, gas-flow, electrical load-flow and flood solvers remain separate integrations.
Retain operational authority
The platform records internal reviews. Switching, isolation, excavation and emergency response follow authorised procedures and field verification.
TALK TO US
Let’s discuss
your utility network.
Tell us about your utility, operating area and the workflow you want to improve. Your enquiry will reach the platform’s administrator inbox.
Please share project context only. Do not include passwords, customer personal data or sensitive infrastructure details.