Skip to content
LaneWarden

Service

One team from the plan to the last report

The devices are half of a smart work zone. The other half is the plan, the testing, the daily watching, the moves as the work moves, and the records afterwards. We do all of it.

How a project runs

Five phases

The schedule follows the construction phases; the deliverables follow the specification.

  1. Before setup

    Plan

    We turn the traffic control plan into a smart work zone system plan: where every node goes, which rules run with which thresholds, which messages are approved and who gets which alert.

    Deliverables

    • System plan submitted at least 30 days before setup
    • Two-carrier cellular drive test of the whole corridor
    • Approved message library and alert matrix

  2. Setup

    Install and test

    Our crew sets up and commissions every node, then runs the operational test with the agency before the system goes live.

    Deliverables

    • Five-day operational test, including a sample of the WZDx feed
    • Operational test report
    • Training for the people who will receive alerts

  3. Every day of the project

    Operate

    Remote monitoring and a local on-call technician. We move devices as the work moves, approve and post messages with the agency, and fix what breaks.

    Deliverables

    • Data problems corrected within 1 hour
    • Field repairs within 24 hours
    • Relocations as traffic control phases change

  4. Weekly and monthly

    Report

    The records an agency needs to manage the project and settle questions later: device health, system performance, delay and queue compliance, and every intrusion alarm.

    Deliverables

    • Weekly device report
    • Monthly system performance report
    • Delay and queue compliance log; intrusion event log

  5. Project end

    Demobilize

    We remove every node, hand over the archive and sanitize every storage device before it leaves.

    Deliverables

    • Data archive kept at least 3 years or handed to the agency
    • Media sanitization to NIST SP 800-88, with records

Service levels

What we commit to design for

These are design targets. On a project they are written into the system plan and reported every month.
Command availability
99.9%
Monthly design target; specifications typically require 99%
Data correction
1 h
Bad or missing data corrected or flagged
Field repairs
24 h
From fault alert to working device
Archive
3 yr
All data, messages and alarms after the project ends

Who does what

Clear lines between us, the contractor and the agency

A smart work zone touches everyone's job. Writing down who leads each task is how nothing falls between teams.

  • Smart work zone system plan and device siting

    LeadsLaneWardenSupportsContractor

    Built around the contractor's traffic control plan

  • Traffic control plan, cones, flaggers and positive protection

    LeadsContractor

    The smart work zone adds to it; it never replaces it

  • Message library, message approvals and speed limit authorization

    LeadsAgencySupportsLaneWarden

    Command enforces what the agency approves

  • Install, test, relocate, maintain and remove every node

    LeadsLaneWarden

    Including the operational test and demobilization

  • Shift-start function check of the sensor cones and wearables

    LeadsContractorSupportsLaneWarden

    Run by the contractor's competent person; we train and supply spares

  • Monitoring, alerts, data quality and field repairs

    LeadsLaneWarden

    Data corrected within 1 hour, repairs within 24 hours

  • Reopening decisions on delay alerts

    LeadsContractorSupportsAgency

    Alerts at 15 and 20 minutes go to the traffic control supervisor

  • Reports, archive and the WZDx feed

    LeadsLaneWardenSupportsAgency

    Weekly, monthly and on request; archive kept at least 3 years

Next step

Planning a work zone that needs to be smart?

Tell us about the corridor, the schedule and the specification. We will walk you through how the system would be laid out and run.

Talk to usRun the live demo