WORKZONE-1 acts as the active lane-closure source while VEH-1 and VEH-2 represent traffic approaching the corridor.
Connected work-zone safety pilot
PingNet work zone safety pilot.
PingNet turns local lane-closure and corridor events into signed, shareable safety messages for approaching vehicles, observer nodes, infrastructure, and emergency responders.
6/6
Nodes observed
100%
Delivery reliability
100%
Signature validation
36-299 ms
P95 latency range
Pilot video
The table-top pilot shows the safety message path end to end.
The edited demo follows six nodes representing a work zone corridor: infrastructure, approaching vehicles, a lane-closure source, observation, and emergency response.
CABINET-1, OBS-1, and EMS-1 demonstrate how infrastructure, observation, and responder roles can receive and validate the message.
The pilot produces logs, receipts, validation status, and KPI output suitable for sponsor review and field-pilot planning.
Validated pilot logs can be mapped into WorkZoneFeed-style and DeviceFeed-style GeoJSON artifacts for agency workflow review.
Validated baseline
A measured baseline, not just a concept slide.
PingNet's April 26, 2026 pilot baseline was validated across three consecutive dry runs: run-20260426-002, run-20260426-003, and run-20260426-004.
Each run produced the expected evidence package.
Downstream receipt tracking completed successfully.
Invalid signatures were not accepted by the pilot.
The baseline met the internal sponsor-readiness threshold.
KPI summary generated from the validated six-node pilot baseline.
Pilot topology
The current proof mirrors a real work-zone corridor.
Each table-top node maps to a stakeholder a DOT or responder partner already understands. The pilot keeps the first public story focused on the work-zone safety use case while leaving broader platform mechanics for private technical review.
Represents the roadside or cabinet-side infrastructure node receiving corridor safety messages.
Represent vehicles entering the work-zone area and receiving signed hazard context.
Acts as the origin of the active work-zone message in the pilot demonstration.
Shows how observation nodes can participate in local safety awareness without being the hazard source.
Models responder entry into the corridor and confirms the message reaches public-safety participants.
Captures receipts, validation decisions, KPI output, and CWZ/WZDx-aligned exports that can support a field-pilot review.
Why it matters
A practical bridge between today's work zones and tomorrow's connected corridors.
PingNet is being positioned as a local safety-message layer for scenarios where latency, trust, and resilience matter more than a polished dashboard alone.
For DOT safety teams
Demonstrate how lane-closure and incident context can reach approaching traffic, observation assets, and responders while producing agency-readable export artifacts.
For responders
Show a path toward role-aware message handling for emergency vehicles entering or crossing an active work zone.
For strategic investors
Start with validated work-zone proof, then expand toward infrastructure-free V2X, distributed trust, CWZ/WZDx-aligned interoperability, and mixed human-machine participation.
Founder-led pilot
Built and led by Jonathan Garrett Jr.
PingNet is still at the stage where founder judgment matters. Jonathan is a U.S. Army veteran and former SIGINT/cyber operator who has worked across electronic warfare, secure communications, and mission-driven systems.
After transitioning into technology, he began building PingNet around a practical question: how can vehicles, infrastructure, drones, and responders share trusted safety information locally when conventional connectivity is limited, congested, or unavailable?
His current focus is turning the validated six-node baseline into a corridor-scale 20-30 node pilot that can produce reliability, latency, delivery, replay-rejection, uptime, time-to-awareness, and CWZ/WZDx-aligned export evidence for public-sector review.
Where PingNet goes next
Validated pilot today. Agency-readable export path next.
PingNet's roadmap extends from work-zone pilot evidence into resilient local messaging, responder-aware workflows, CWZ/WZDx-aligned exports, distributed trust, and crisis-response communication for connected corridors.
Baseline complete
Six local nodes validated message delivery, signature checks, receipts, and KPI generation in repeatable dry runs.
Field pilot package
Translate the table-top pilot into a DOT-ready corridor demonstration with WorkZoneFeed-style and DeviceFeed-style GeoJSON outputs.
Responder integration
Extend the current EMS node role into responder-priority workflows and operational review with public-safety partners.
Trust and crisis layer
Advance distributed trust, privacy-aware identity, and crisis-mode propagation for resilient connected-safety deployments.
Research brief
A concise evidence packet for partner review.
The research brief and pilot evidence package support conversations with DOT innovation teams, work-zone safety programs, emergency response stakeholders, and strategic investors evaluating the next field validation and CWZ/WZDx-aligned export step.
Review the pilot or discuss a field demonstration.
PingNet is ready for targeted conversations around DOT work-zone pilots, responder workflows, CWZ/WZDx-aligned evidence exports, and strategic validation partnerships.