Start with the vehicle.
A machine-generated crash event can begin the notification workflow when an occupant is unable to call or explain what happened.
Automotive intelligence. Public safety action.
The airbag deploys.
The response
begins.
ADAP-to-RTIC connects the moment of impact to the people who can act—bringing trusted vehicle crash telemetry directly to real-time public safety intelligence.
Airbag Deployment Automation Protocol → Real Time Intelligence Center
CONNECTED SAFETY / ADAPCONCEPT WORKFLOW
EVENT: AIRBAG_DEPLOYMENT
PAYLOAD: CONNECTED VEHICLE EMERGENCY DATASET
PAYLOAD: CONNECTED VEHICLE EMERGENCY DATASET
01Vehicle detects the crash
02Clearinghouse verifies the message
03RTIC receives actionable intelligence
One trigger.Airbag deployment initiates the data event.
Trusted data.Structured telemetry supports machine verification.
Coordinated care.RTIC intelligence informs an agency-led response.
Why ADAP-to-RTIC
Give the crash a digital voice.
Connect automotive software and public safety operations through a common, actionable exchange.
Send more than a location.
Available vehicle and occupant signals can help agencies assess the incident and identify the information responders need.
Inform the next decision.
Deliver verified crash intelligence into RTIC and CAD workflows to support drone, EMS, and trauma-system coordination.
How it works
From a vehicle event
to public safety intelligence.
The architecture brings detection, data exchange, verification, and operational response into one connected workflow.
Crash Monitor Agent
Recognizes airbag deployment and gathers available vehicle signals through the vehicle data interface.
IoT Clearinghouse
Feeder, Verifier, and Cloud Server services support structured crash-message delivery and verification.
RTIC / CAD
Receives crash intelligence for integration into participating agencies’ incident-management workflows.
Responders & care
Supports agency-authorized Drone First Responder, EMS, and hospital coordination where integrated.
LSL ARCHITECTURE / OCTOBER 2026
The ADAP-to-RTIC blueprint
Explore the supplied reference architecture, including the vehicle server, VSS and occupant signals, VISS v3.2, Connected Vehicle Emergency Dataset, and clearinghouse.
The 2–3 second goal refers to crash-data delivery to the RTIC. Drone launch and responder arrival are separate operational measures.
Open full architecture ↗
By the ecosystem. For the ecosystem.
Your role in connected post-crash care.
Choose your perspective to explore the integration questions and a practical starting point.
A shared language for crash intelligence
Interoperability starts with the dataset.
VEHICLE SIGNALS
VSS & VISS
Vehicle Signal Specification provides a common vocabulary for vehicle signals. The supplied architecture uses VISS v3.2 as its vehicle-data interface.
EMERGENCY PAYLOAD
CVED
The Connected Vehicle Emergency Dataset is under development within the COVESA initiative to structure vehicle emergency data for machine-to-machine exchange.
TRUST & OPERATIONS
Verification & integration
Define sender trust, message validation, data minimization, access controls, and CAD handling during scoping and controlled evaluation.
Development initiative: this site presents the proposed architecture and participation pathway. It does not assert a finalized CVED standard, certified interoperability, or nationwide operational availability.
Resources
Understand the model.
Scope the next step.
ADAP-to-RTIC reference diagram
The October 2026 blueprint for connecting a vehicle-generated crash event to RTIC intelligence.
Download diagram ↓ASAP-to-PSAP
The Monitoring Association’s ASAP program demonstrates the alarm industry’s approach to digital notifications and CAD workflows. It is an inspiration for this automotive pathway, not an LSL affiliation.
Explore the ASAP program ↗LiDAR Saving Lives
Explore LSL’s connected-safety mission, coalition activity, and pathway from co-design to operational validation.
Visit the coalition ↗Frequently asked questions
What industry
needs to know.
What is ADAP-to-RTIC?
Airbag Deployment Automation Protocol-to-Real Time Intelligence Center is an automotive emergency-data pathway that connects a detected airbag deployment to verified crash intelligence for public safety operations.
Is this the same as ASAP-to-PSAP?
No. ASAP serves alarm monitoring and emergency communications centers. ADAP-to-RTIC applies a similar digital-exchange concept to connected vehicles and RTIC workflows. The programs have different domains, payloads, and integration requirements.
Does an airbag event automatically launch a drone?
Drone dispatch depends on agency policy, operational readiness, aviation requirements, and the deployed integration. The crash event supplies intelligence; each participating agency defines its authorized response.
Is CVED a completed standard?
CVED is under development. Dataset definitions, verification requirements, and implementation profiles must be agreed and validated with participating stakeholders.
How can my organization get started?
Start with an LSL Automotive IoT Scoping Services engagement to map available signals, receiving systems, trust requirements, and a bounded demonstration plan. Services are fee-based; scope and fees are agreed before work begins.
Get connected
Make your next integration
a lifesaving one.
Work with LiDAR Saving Lives to scope your ADAP-to-RTIC use case—from vehicle signals and trusted exchange to CAD workflows and demonstration readiness.
FEE-BASED AUTOMOTIVE IoT SCOPING SERVICES