A journey with context.
Review the journey location, event timeline and available observations, including gaps or low-confidence data.
Better context for
public-safety decisions.
Murli V Tech is developing ACTEDS to help teams review journeys that may need attention. Start with one participating fleet, one review team and a pilot built around your department’s existing operations.
Discuss a government pilotWHY THIS MATTERS FOR INDIAHelp useful evidence
Help useful evidence
reach the people
who can act.
India’s emergency-response infrastructure already brings calls, location and dispatch together. Our opportunity is to connect journey evidence to that operational picture.
Explore the government pathway4,80,583Road accidents reported in India in 2023.Source: MoRTH data, published by Uttarakhand Transport ↗
112India’s unified emergency-response number, with state-centric response systems.Source: Ministry of Home Affairs ↗
AN ILLUSTRATIVE JOURNEYWhat would your team
What would your team
actually see?
A participating cab makes an unexpected stop and departs from its planned route. Either change may have an ordinary explanation. ACTEDS is designed to assess available context over time before treating the journey as needing attention.
The 15-channel approach considers available journey, movement and device context alongside passenger verification. The pilot establishes which inputs are available and how the department’s team will review eligible events.
A clearer check-in status.
Where a passenger check-in is appropriate, distinguish a request that was not delivered from a delivered request awaiting a response.
An accountable next step.
An authorised reviewer assesses the event. The department’s agreed process determines the next action; a signal does not establish that a crime occurred.
A PILOT WE DEFINE TOGETHERStart small.
Start small.
Know who does what.
The proposed technology scope.
Scope the ACTEDS assessment layer, supported data connections, event-review tools and technical support for the pilot.
The operational decisions.
Identify a use case and responsible team. Agree permitted data sources, access, review duties and the response process.
A measured rollout decision.
Test agreed scenarios and measure missed events, false alerts, delivery delays and reviewer workload before deciding whether to expand.
CONNECT THE PIECESYour infrastructure.
Your infrastructure.
Our intelligence layer.
YOUR SYSTEMSApps & fleetsJourney and device observations
MURLI V TECHVV / ACTEDSSignal quality · context · persistence
YOUR OPERATIONSReview & responseAlerts, evidence and authorised workflowsExisting systemsAPI or agreed integration
Start with the data and systems you already have. Define each connection around your environment.
Already operating a fleet or journey-tracking system? We first assess which journey data your systems can provide. Supported inputs and interfaces are agreed for the pilot; availability of all 15 signal channels is not assumed.
See integration pathwaysERSS-112 / PROPOSED INTEGRATION PATHWAYBuild around the response
Build around the response
infrastructure already in place.
The Ministry of Home Affairs describes ERSS-112 as a state-centric system that receives distress information through multiple channels and supports dispatch with incident data. Murli V Tech’s proposed role is an additional source of structured evidence for an agreed workflow.
Direct connectivity to ERSS-112 or a government command centre requires the responsible department’s approval, interface agreement and acceptance testing. A live government connection is not claimed on this site.
Read the MHA description of ERSS-112 ↗THE PILOT CONVERSATIONA clear scope for
A clear scope for
the people accountable.
Operational purpose
Choose the fleet, transport setting or safety-review problem. Name the team receiving the output and define what it can do with it.
Data & responsibility
Agree approved sources, permitted uses, access, retention, incident ownership and escalation responsibilities.
Acceptance criteria
Measure detection on defined cases, false alarms, latency, data-quality handling and the workload created for reviewers.
Technical handoff
Test interfaces, authentication, delivery failure, operator acknowledgement and the agreed response process.
Commercial scope
Compare integration effort, service costs, infrastructure and departmental operating costs before deciding on a wider rollout.
VVGOV / LOCAL RESPONSEThe right context.
The right context.
For the right station.
Participating cabs, employee transport and material trucks send journey observations through your integration. VVGov brings assigned vehicles, active events and station handoffs into one local view.
A focused queue is designed to reduce irrelevant alerts. A pilot measures that workload, coverage and response handoffs before wider deployment.
Open VVGovILLUSTRATIVE AREA VIEW / NOT LIVE DATA
Station A selected. The illustration highlights participating vehicles assigned to this area.
Configured proximity assigns vehicles. Hexagons illustrate coverage; they are not official jurisdiction boundaries.Authorised access
Local context · station handoffs
Local context · station handoffs
WHY AN ADDITIONAL SAFETY LAYERWhen pressing SOS
When pressing SOS
isn’t possible.
A person facing coercion, sexual violence or a medical emergency in a cab may be unable to reach a phone or ask for help. An incident can remain unnoticed while a journey still appears active.
VV is designed to bring eligible journey signals and sustained deviations to an authorised reviewer’s attention. Signals support assessment; they do not prove a crime. Response depends on the agreed operational process and available responders.
Context beyond a button.
Review unusual journey patterns alongside signal quality and persistence, with human assessment before action.
Keep the journey visible.
Review participating trucks, route changes and unexpected stops. Cargo condition or theft confirmation requires additional data and investigation.
Add a layer. Keep your systems.
Connect through an agreed API workflow, define ownership and evaluate detection, false alerts and handoffs on a limited pilot.
VISUAL PERSPECTIVE
Context for the people responding.
A visual concept for coordinated operations. Authorised integrations and a partner pilot are needed for a live deployment.
MURLI V TECH / WORK WITH USStart with one use case.
Start with one use case.
Establish the evidence.
Tell us your department, the fleet or journey use case, the systems already in place and who would review events. We can then scope the integration, responsibilities, costs and measures for a pilot.
Discuss a pilotCONNECTED OPERATIONSEvery observation.
Every observation.
A clearer picture.
Bring participating journeys and reviewable evidence into a defined operational workflow.
Explore the VVGov demonstration ↗CONNECTION STUDY / ILLUSTRATION
PUBLIC SAFETY / PILOT DESIGNA focused pilot.
01 02 03 Define a pilot with us ↗
A focused pilot.
A measurable decision.
Existing infrastructure
Start with participating vehicles and an agreed integration. Define which systems and teams own each action.
A manageable review queue
Evaluate coverage, duplicate alerts and station handoffs. Measure workload rather than promising zero additional work.
Evidence before expansion
Agree detection, false-alert, latency and acknowledgement measures before scaling the pilot.
PROPOSED OPERATOR & STATION PILOTFaster evidence review.
Faster evidence review.
A clearer integration plan.
Explore the driver-evidence workflow and our proposal for a limited operator and police-station trial. No partnership or deployment is claimed.
Explore driver evidence ↗ Open the pilot presentation ↗