Intelligent Transportation Systems
Run every corridor alternative through microsimulation and carry the results straight into the ConOps, requirements, and estimate.
How the work changes
ITS engineers go from building and re-running each model by hand to setting the calibration targets, reviewing what the Sinusoidal platform runs, and weighing more alternatives than they had time for.
The Challenge
The model has no fixed price
Calibrating the microsimulation from field counts and translating results into a ConOps and requirements is multi-week work for every alternative.
Skipping ahead has a price tag
Locking a design before alternatives are weighed carries risk the federal systems engineering process exists to catch. [FHWA SEITS ↗]
Why Sinusoidal
Builds and iterates the model
Runs your corridor's microsimulation (VISSIM, Synchro, Aimsun, or SUMO) against every alternative, calibrated to field counts.
Drafts the ConOps and requirements
Each requirement traces back to the simulation run that supports it, the traceability federal rules require before procurement.
Compiles the estimate
Quantities and costs for the signal, detection, and comms hardware roll up straight from the simulated design.
The Benefits
More alternatives weighed before anything locks
Engineers compare several signal-timing and detection options instead of committing early just to hold the schedule.
A tighter package reaches procurement
Requirements and the estimate trace back to the same simulation results, so the package holds up in review.
Working alongside your team
We start on one corridor, calibrate against your own counts with your modelers, and hand over a repeatable setup your team can run on the next one.