Should maintenance be scheduled by calendar or by usage?

By whichever variable actually drives wear on that asset. Engine-hour meters on light towers and generators are the right trigger for service intervals; deployment days are the right trigger for inspecting a trailer that has been vibrating on a shoulder for three weeks. Pure calendar scheduling over-services equipment that sat in the yard and under-services equipment that has been out continuously.

What should be inspected at every pickup rather than in the yard?

Anything whose condition is evidence. Damage photographed at the site, timestamped and located, is attributable to a specific job; the same damage found three days later in the yard is an argument you will lose. Pickup is also when you know the deployment duration, which is the variable that tells you whether an inspection is due.

How do we stop the same unit failing repeatedly?

Keep the history on the asset rather than in a work-order pile. A unit with three similar repairs in eight months is telling you something — either it was damaged in a way that was never properly repaired, or it is being used outside what it was built for. Neither is visible when each repair is filed separately.

Is a spare unit cheaper than fast repairs?

Frequently, for the assets where an outage stops a job. The comparison is between the carrying cost of a spare and the combined cost of emergency rental, lost jobs and overtime when the unit is down. Companies usually discover they should have bought the spare during the week they could not get one.

Who should do the daily checks?

The crew that takes the unit out, as part of the load-out routine, on a short list. Anything longer than a handful of items stops being done honestly within about two weeks. The detailed inspection belongs to whoever handles maintenance, on a schedule.

Does maintenance history matter for compliance?

For the categories where an agency or an insurer may ask about the device, yes. Crashworthiness eligibility and device condition standards are questions about specific units, and answering them requires an asset register that carries acquisition, standard and service history rather than a count of how many you own.

Equipment Maintenance Programs for Traffic Control Fleets

Arrow boards, attenuator trailers, light towers and message signs fail in predictable ways at the worst possible moment. Here is how to build a maintenance program that matches how this equipment is actually used.

Most traffic control companies manage maintenance reactively, and the reason is understandable: the equipment mostly works, the failures feel random, and there is always something more urgent than servicing a trailer that is currently running fine.

The failures are not random. They cluster in known places, and they concentrate at the worst possible moment — because the units that fail are the ones that have been out continuously, which are the ones on the jobs that matter.

What actually fails, and why

Traffic control equipment has an unusual duty cycle. It is not used intensively for an hour and returned like a rental tool; it is deployed for days or weeks, unattended, outdoors, adjacent to traffic, in whatever weather arrives.

Arrow boards and portable message signs. Batteries and charging systems first, by a wide margin. A solar-charged unit deployed under tree cover or through a fortnight of overcast weather is running a deficit nobody can see until the panel goes dark at 2 a.m. Then lamp or module failures, then the mast and winch mechanism, then controller faults from moisture ingress.

Light towers and generators. Engine hours drive it — oil, filters, fuel system. The failure mode that costs most is fuel contamination from long storage between seasons.

Attenuator and AFAD trailers. Hydraulics, tyres, wiring harnesses and lighting. These live at the roadside, get struck occasionally, and vibrate continuously.

Trailers generally. Tyres, bearings and lights. Unglamorous, and the single most common reason a unit does not make it to a job.

Portable traffic signals. Battery systems, radio link reliability, and the controller.

The pattern: the batteries, the tyres and the wiring account for most unplanned downtime, and all three are cheap to inspect and expensive to discover.

The three-tier program

A maintenance program that gets followed has three tiers, distinguished by who does it and how long it takes.

Tier 1: the load-out check

Performed by the crew taking the unit, in under two minutes, on a fixed short list. Tyres and lights on the trailer, battery state, fluid levels, obvious damage, safety chains and coupling.

The discipline that makes this work is brevity. A twenty-item checklist at 5:30 a.m. becomes a ticked box within a fortnight, and a ticked box is worse than no check because it creates a false record. Five to eight items, every unit, every time.

Tier 2: the pickup inspection

Performed at retrieval, at the site, before the unit is loaded. This is the tier most companies skip, and it is the highest-value one for two reasons.

Damage found at the site is attributable. A photograph taken at the job, timestamped and located, belongs to that job and that customer. The same damage discovered in the yard three days later belongs to nobody and gets absorbed. Charging for damaged and lost traffic control devices covers the commercial side of that distinction.

Deployment duration is known at pickup. How long a unit has been out is the variable that determines whether it is due for service, and it is available at exactly this moment and awkward to reconstruct later.

Tier 3: the scheduled service

Performed by whoever handles maintenance, triggered by hours, deployment days, or calendar — whichever drives wear on that asset class. This is where the manufacturer's intervals live, along with anything requiring tools.

Triggering on the right variable

The most common structural mistake is scheduling everything by calendar. It produces two errors simultaneously: units that sat in the yard all quarter get serviced anyway, and units that were deployed continuously for eleven weeks get serviced on the same cycle as if they had not been.

Use the variable that drives the wear:

Engine hours for anything with a motor.
Deployment days for anything that lives at the roadside — the trailer that spent six weeks on a shoulder has aged differently from the identical one that went out twice.
Cycles for masts, winches and anything raised and lowered.
Calendar for genuinely time-based items — fluid degradation, certifications, registrations.

This is only practical if you know deployment days per unit, which is the same data that produces your rental billing. Companies that track deployments properly get maintenance triggers for free; companies that track a warehouse quantity cannot build this at all. Tracking traffic control devices by job site covers the underlying model.

Keep the history on the asset

The second structural mistake is filing repairs as work orders rather than against the unit.

A repair pile tells you what you spent. An asset history tells you which units are costing you money, and that is a different and more useful question. Three similar repairs on one arrow board in eight months means either the first repair was not a repair, or the unit is being used in a way it was not built for, or it is at the end of its life. None of that is visible when each repair is a separate ticket.

Asset history is also what turns replacement planning from a guess into a decision. Equipment fleet replacement planning covers the economics; the input it needs is cost-per-unit-per-year, which only exists if repairs were attributed.

And it matters for compliance in the categories where an agency or an insurer may ask about a specific device — acquisition date, manufacturer, and the standard it was built to. MASH compliance for work zone devices covers the crashworthiness framework, and sign retroreflectivity and device condition standards covers condition. A yard that knows only how many it owns cannot answer either question.

Why downtime is a safety issue, not just a cost

An arrow board that fails at 2 a.m. on a lane closure is not a scheduling inconvenience. It is the removal of the primary advance warning on a live closure.

Work zones are a genuinely hazardous environment: the National Work Zone Safety Information Clearinghouse records 763 fatal work zone crashes and 850 work zone fatalities in 2024 from NHTSA FARS data, and FHWA's tabulation for 2022 records 891 work zone fatalities with rear-end collisions accounting for 21% of fatal work zone crashes and speeding a factor in 34%.

Rear-end collisions and speeding are precisely the failure modes advance warning devices exist to address. A dark arrow board is not a maintenance backlog item; it is a work zone operating with less warning than the plan specified. Arrow boards and message signs explained covers what they are doing, and barricade lights and warning light types covers the smaller equivalent problem — which is more common and even easier to ignore.

Spares, and when they are worth it

The question to ask about any powered asset is: if this unit is down for a week, what happens?

If the answer is "we call around for a rental and lose a day" or "the job does not run", the carrying cost of a spare deserves a serious look against the combined cost of emergency rental, lost revenue and the overtime that surrounds a scramble. Renting vs buying traffic control equipment covers the general economics.

The related risk worth planning for at the same time is equipment theft and vandalism, which produces the same outcome — a unit that is not available — through a different route.

Making it run without a dedicated person

Under roughly fifteen powered assets, most companies cannot justify a full-time maintenance role, and the program has to run as a by-product of normal work. That means:

the load-out check is part of load-out, on the same device or paper the crew already uses
the pickup inspection is part of pickup, with photographs attached to the job
service triggers fire from deployment and hour data that already exists
repairs are recorded against the asset, not in a pile

Traffic OS holds equipment as assets with deployment history and condition against the job record, so deployment days and pickup photographs arrive without a parallel process, and a unit's history stays with the unit. It is priced in flat monthly tiers — $499, $949 and $1,499 as of September 2026 — with no per-user charge, which matters because the person doing the load-out check is usually a field employee. The features page has the detail; a walkthrough is the quickest way to see whether it fits your yard. The broader yard question is covered in yard organization for traffic control companies.

Device condition standards and inspection requirements vary by state, county and city, and your contract may specify more than the manual does. Verify with the authority having jurisdiction on your job.