Covered by an FMCSA exemption for use on commercial motor vehicles in place of triangles and fusees.See the Smart Sequential Road Flares
Call Us: +1 (949) 415-9411
pi-lit CLOUD · MAKE LANE CLOSURES BETTER

Warn drivers before they reach your crew.

Your crew sets the taper. pi-lit Cloud warns approaching drivers and tracks every deployment automatically, across every connected Sequential Flare, Smarter Cone, smart taper lamp, and piLINK gateway.

Cloud access includedwith every connected system

Live device status, alerts and events, impact notifications, and reporting in one place.

pi-lit CLOUD · CORRIDOR TELEMETRYI-71 Southbound · Event #4819
DIGITAL ALERT ACTIVEAUTHORIZED FLEET LOCK
OPEN THRU LANE (58.3 MPH)LIGHT BAR + piLINK GATEWAYDriver Alert: Crew Ahead · 0.5 miLive navigation & connected-vehicle alertGeo-Stamped Taper · 41.4993° N, 81.6944° W10 devices placed · 580 ft MUTCD spacing verified
MEASURED SLOWDOWN-10.3 mph with piLINK
68.6 mph 58.3 mphFree-flow vs. active alert
AUTO-LOGGED TAPER RECORD4hr 02m 12s · 580 ft Taper10 devices geo-stamped · Activated by light bar
FLEET LOCK & CLOUD STATUSAccount Verified · LiveCustomer & Integrator API + WZDx v4.2 ready
01

App + Bluetooth

Included with every flare and cone set

02

piLINK Vehicle Gateway

Zero-touch automatic cellular and light-bar trigger

Explore piLINK
MEASURED DRIVER SLOWDOWN

Information rich, not just data rich.

Every deployment is matched to its own road segment and time window, then compared with that segment's free-flow baseline. You see the slowdown, not just the activation.

One utility fleet · 12 months · September 2025 to August 2026

16,594

Qualified deployments

8.9mph

Mean drop across the 864 deployments that slowed most

23.8%

Measurably slowed traffic

11,680

With usable speed data

One of these moved traffic. Telling them apart is what you are buying.

Matched on purpose: same road class, same 37 mph free-flow baseline, same daylight hours, near-identical length. One held traffic around 24 mph for four and a half hours. The other did not move it at all. Neither crew could have told you that; it is visible only because every deployment is measured against its own road segment.

Traffic slowed, and stayed slowed

Secondary road · 4h 32m · 273 speed readings

36.8mph free flow
23.8mph measured
−13.0mph difference
0153045 mph01h2h3h4hFree flowMeasured

Measured traffic speedFree-flow baseline for this segment

Secondary road, 4 hours 32 minutes, 273 readings. Free-flow baseline 37 mph. Traffic held around 24 mph for the whole deployment.

Read the values
Mean measured speed and free-flow baseline per half hour of the deployment, in mph
ElapsedMeasuredFree flowReadings
0 to 30 min25.636.731
30 to 60 min24.136.830
60 to 90 min23.836.930
90 to 120 min22.936.930
120 to 150 min23.837.030
150 to 180 min23.636.730
180 to 210 min23.636.730
210 to 240 min23.736.830
240 to 270 min23.537.030
270 to 272 min21.537.02

Mean of the individual readings in each half hour. The plot draws every reading.

Traffic did not respond

Secondary road · 5h 05m · 305 speed readings

37.0mph free flow
36.7mph measured
−0.3mph difference
0153045 mph01h2h3h4h5hFree flowMeasured

Measured traffic speedFree-flow baseline for this segment

Secondary road, 5 hours 5 minutes, 305 readings. Same 37 mph baseline, same road class, same daylight hours. Traffic did not change.

Read the values
Mean measured speed and free-flow baseline per half hour of the deployment, in mph
ElapsedMeasuredFree flowReadings
0 to 30 min37.037.030
30 to 60 min37.037.031
60 to 90 min37.037.030
90 to 120 min36.136.930
120 to 150 min37.037.030
150 to 180 min35.036.830
180 to 210 min37.037.029
210 to 240 min36.636.930
240 to 270 min37.037.030
270 to 300 min36.837.030
300 to 305 min37.037.05

Mean of the individual readings in each half hour. The plot draws every reading.

The deployment on the left is one of the 864 that slowed traffic by 6 mph or more, representing the top 7% of measured deployments. The one on the right is the common case: 76% of measured deployments show no change over 1 mph.

View full speed breakdown across all 11,680 events by road type

Where it worked, and where it did not

Mean traffic speed with and without piLINK, by road type, in miles per hour
Road typeEventsFree flowWith piLINKShare slowed
Secondary road5,49942.841.427.8%
Local road5,36637.836.921.4%
Major road36360.258.620.1%
Motorway45269.268.94.9%
All measured11,68042.140.923.8%

Speeds in mph, each deployment measured against its own road segment's free-flow baseline. A qualified deployment ran at least two minutes.

25%

Risk at 33 mph

10%

Risk at 25 mph

Why averages undersell it.

On the 864 deployments where traffic slowed most, the roads' normal speed was 33.5 mph and traffic measured 24.6 mph. That moves a struck worker from roughly a one-in-four chance of death to one in ten, and gives an approaching driver about 20 feet more road over a 1.5 second reaction. Nothing at dispatch marks those jobs out beforehand, which is the case for covering every deployment.

Measured population is piLINK gateway activations, 99.4% of them started by the vehicle light bar. Sequential Flares were recorded on under 1% of these deployments, so these figures measure the digital alert, not the flares. Traffic speeds from commercial real-time traffic probe providers, matched to each deployment's road segment and time window. Impact-speed risk from Tefft (2011), AAA Foundation for Traffic Safety; the curve describes outcomes if a collision occurs, not whether one occurs. Example figures are from one piLINK customer's 1 September 2025 to 31 August 2026 reporting period. Customer name withheld.

AUTOMATED TAPER RECORD & ANNUAL FLEET REPORTING

One deployment, or the whole year.

SCENE & TAPER RECORD

Every cone and flare knows where it was put down.

The app geo-stamps each connected device as the crew places it. When the road reopens, the taper is still in the record: length, spacing, placement order, and how long it took to set, read against the MUTCD guidelines your agency configures. Nobody measures a taper with a wheel, and nobody files a report for this to exist.

Scroll sideways to follow the closure.

TrafficResponse vehicle · piLINK gateway123456789B62 ft · widest gapA268 ft measured · 320 ft guideline at 40 mphAdvance warningMerging taperBufferWork area

What the record says about this closure

9

Connected devices geo-stamped

In placement order, with the time each went down

268 ftTo review

AMerging taper length

320 ft guideline at 40 mph across a 12 ft lane

33.5 ftWithin guideline

Mean device spacing

40 ft guideline maximum in a taper

62 ftTo review

BWidest gap, devices 5 to 6

40 ft guideline maximum in a taper

3 min 08 s

Time to place the taper

First device down to last device down

Read the values
Each connected device in placement order, with the time it was placed and its distance from the device before it
DevicePlacedFrom previousAlong taper
10:00-0 ft
20:2231 ft31 ft
30:4434 ft65 ft
41:0633 ft98 ft
51:2832 ft130 ft
62:0862 ft192 ft
72:2826 ft218 ft
82:4825 ft243 ft
93:0825 ft268 ft

Illustrative deployment: a diagram of what the analysis reads, not a screenshot and not customer data. Longitudinal distance is compressed about five times against lane width: a 268 ft taper across a 12 ft lane is far shallower on the road than it can be drawn on a page. Guideline values follow the MUTCD merging-taper formula (L = W × S² ÷ 60 at 40 mph or less) and the taper device-spacing guidance of one foot per mph, and are configurable per agency. pi-lit Cloud flags geometry for review; it does not make a compliance determination.

One deployment

Review this deployment

The scene map, placement order and timings, taper length and spacing against your own configured guidelines, attached to the after-action report the crew already generates.

Across the fleet

Improve every deployment

The same read across every crew, vehicle and region. Find the gap that repeats, see whether TIM training moved it, and export the trend for the supervisor who has to defend the program.

WHAT COMES WITH THE PLATFORM

One click, and the year looks like this.

Nobody assembled this. Every bar is deployments your crews already made, logged the moment the warning went live, and waiting on the dashboard whenever someone needs to show what the program actually did.

December ran 1,950 deployments against April's 1,091, with the busiest month almost double the quietest. Whatever drove that, the record already knows which roads, for how long and how traffic behaved, and nobody has to reconstruct it by hand in front of a budget conversation.

05001,0001,5002,000SepOctNovDecJanFebMarAprMayJunJulAug1,950
16,594 deployments · 24,651 hours of live warning · 4,855 named roads · median job 47 minutes
Read the values
Deployments, hours of live warning and named roads by month
MonthDeploymentsHoursMedian lengthNamed roads
September 20251,3201,50836 min766
October 20251,3361,60336 min789
November 20251,3191,48736 min801
December 20251,9502,42540 min1,082
January 20261,1161,54651 min666
February 20261,1811,76655 min698
March 20261,2173,81254 min727
April 20261,0911,97959 min659
May 20261,2981,88453 min796
June 20261,6742,48857 min989
July 20261,7782,35750 min1,074
August 20261,3141,79749 min797
Total16,59424,65147 min4,855

Named roads do not sum down the column because the same road appears in more than one month. The total is the count of distinct road names across the year.

One piLINK customer's own year, September 2025 to August 2026. Same account and same method as the measured figures above.

16,594deployments recorded in a year

Every deployment, in context

Start and end time, duration, road name and class, what triggered it, weather, temperature, daylight or night. Nobody filled in a form for any of them; the record is a by-product of the warning going live.

11,680with a measured traffic response

Live and historical speed traces

Each deployment plots real traffic speed against that road segment's own free-flow baseline for that hour, live while the truck is out and kept afterwards. That is the difference between knowing a light was on and knowing whether drivers slowed.

4,855named roads, broken out by class

Cut the way you actually manage

By vehicle, by shed, by road class, by day or night. A 45 mph road is a different risk than a 25 mph road, and a crew that never activates is a different problem than one that activates on the wrong roads.

24,651hours of live warning, in one page

One click to the report

Pick a date range and get a one-page summary you can hand to a director or attach to a renewal. Monthly snapshots arrive on whatever cadence you set.

WHAT EVERY CONNECTED SYSTEM GETS

Know what is on the road, and what happened there.

  • Live device status

    Every connected flare, cone, lamp and gateway is named by account and serial number, with its live status on one map.

  • Temporary traffic control alerts and events

    Activations, alerts and closures are logged as events the moment a deployment goes live, with time and location.

  • Impact notifications

    Get notified when a connected device in the taper is struck or knocked down, so the crew hears about it right away.

  • Reporting

    Pick a date range and get a summary you can hand to a director or bring to a budget conversation.

Cloud access is included with every connected system. Talk to us about plan options for your fleet.

Get cloud pricing
GET STARTED WITH pi-lit CLOUD

Already own pi-lit sets or outfitting a fleet?

Talk to us about connecting your fleet. We can quote hardware and cloud access on the same purchase order.