123BIMLive
Upload a LiDAR scan or a CAD design. Get a road safety audit.
State‑of‑the‑art AI audits every mile of your LiDAR scan and connects the hazards it finds to your crash records. Fix what puts drivers at risk before someone gets hurt, and spend your safety budget where it saves the most lives, without putting a crew on the road.
LiDAR of a road you already own, or the CAD model of one you are still designing — Bentley MicroStation and OpenRoads, Autodesk Civil 3D. How a design run works
From RDV Systems, trusted by 19 state DOTs since 2005.
Why DOTs use it
Know where your network puts drivers at risk, and what to fix first
123BIMLive turns a LiDAR scan you already own into a safety audit of the whole corridor: what is deficient, what is blocking the view, and which fixes buy the most safety per dollar.
Audit every mile, not a sample
A field audit covers the sites someone can be paid to visit. Here every station on the corridor is checked, in both directions, so nothing ends up low priority only because no one drove it.
Spend the safety budget where it prevents crashes
Findings come ranked by crash risk. The Safety Dashboard tests them against your state's crash records and prices the fix — crashes prevented, annual benefit and benefit-cost ratio, in the form an HSIP application asks for.
Nobody stands in live traffic
Nothing is measured from the shoulder. No lane closures, no traffic control, no crew exposed to the road you are auditing.
Findings that hold up in review
Every check follows the AASHTO Green Book, the Roadside Design Guide and the MUTCD, applied the same way at every station, with the driver's view from the scan behind each verdict.
One upload, every analysis
Sight distance, curves, clear zone, glare, guardrail and the rest all run on the same scan. Adding one later reuses that scan instead of sending anyone back out to collect the data again.
Something to show, not just a report
Drive-through video, an online report for every road and a 3D viewer in the browser — what a commission meeting, a public hearing or a funding request actually needs.
The analyses
Choose what each corridor needs
Every analysis runs on the same scan, so adding one to a run never means collecting the data again.
Stopping sight distance
What it checksTests at every station whether a driver can see an object in the lane in time to stop, stepping through the AASHTO speed table to the highest speed the view supports.
What you getWhere drivers can't stop in time, what blocks the view (terrain, vegetation, a crest, guardrail, pole or sign) and a crash-risk score for ranking the fixes.
Passing sight distance
What it checksCompares the passing zones marked on the road with the sight distance a pass needs under AASHTO and MUTCD criteria.
What you getZones striped for passing where a driver can't see far enough to pass safely, the setting for head-on crashes.
Intersection sight distance
What it checksChecks each maneuver at each intersection against the AASHTO sight triangles for a vehicle waiting to turn or cross.
What you getWhich movements at which intersections have a blocked view, so clearing, signal or geometry work goes where it counts.
Horizontal curves
What it checksMeasures each curve's radius and superelevation from the scan and checks them against the AASHTO Green Book, with maximum superelevation set per route.
What you getCurves whose safe speed falls below the posted speed, the candidates for advisory speeds, chevrons or re-banking.
Flat spots
What it checksMeasures the longitudinal grade and cross slope of the pavement at every station.
What you getThe flat spots where water stays on the road, so drainage fixes target hydroplaning and ice risk.
Sun glare
What it checksBuilds a year-long calendar for every station of the times the sun sits near the driver's line of sight.
What you getWhich stretches blind drivers, and at what times of day and year.
Guardrail warrant
What it checksEvaluates embankment height and fill slope against the barrier warrant in the AASHTO Roadside Design Guide.
What you getWhere a barrier is warranted along the corridor, and where one is not, before crews install or remove guardrail.
Embankments
What it checksCuts 3D cross-sections through the embankments along the corridor.
What you getSide-slope geometry for designers, delivered as DXF cross-sections without sending a survey crew.
Clear zone
What it checksMeasures the clear zone width and side slopes, and finds the fixed objects and guardrails inside it.
What you getTrees, poles and slopes in the recovery area, where a vehicle that leaves the road has no room to recover.
Traffic signs
What it checksDetects signs in vehicle camera imagery, reads each one's MUTCD code and size, and places it with the LiDAR.
What you getA georeferenced sign inventory for the corridor, without a crew walking it.
Deliverables
One run, the whole package
Everything lands in the project folder together — nothing to request, export or chase afterwards.
- Word
- MP4
- CSV
- Shapefile
- DXF
The online report
Every station, in the browser
One page per road and direction, carrying every tested point on it — 17,274 of them on the corridor below. Pick a row and the scan jumps there: the driver’s eye view, the target it was measured against, a zoom on whatever is in the way and the point on the map.
- Visibility, obstruction, milepost, slope, tested speed and the speed the view actually supports, station by station
- Failures flagged in red with the obstruction named — vegetation here
- LRS location, milepost and a street-view link on every point, so a crew can find it
- Search a mileage or a speed, filter, sort — then share the link
Reports you can file
- Summary reportThe corridor's deficiencies, ranked, with the criteria each one failed.
- Comprehensive reportEvery station of every analysis, the numbers behind each verdict and the standard applied.
- One per road and directionSplit the way a project is reviewed, in PDF and in Word.
Show it to people
- Drive-through videoThe corridor as a driver sees it, findings drawn on the road, per analysis and direction.
- Glare heat mapsWhere and when the sun sits in the driver's eyes, through the year.
- Stills for the slide deckThe driver's view at each deficiency, ready for a commission meeting or a hearing.
Hand it to the engineers
- Station tablesCSV of every station: available and required sight distance, speed, grade, radius, superelevation.
- GIS layersShapefiles of every eye position, target, sight line and deficiency run — straight into ArcGIS.
- DXF cross-sectionsEmbankment sections cut from the scan, for design to work from.
- Sign inventoryEvery sign georeferenced, with its MUTCD code and size.
Take it to the program
- Priced countermeasuresCrashes prevented, annual benefit and benefit-cost ratio per site, in the form HSIP asks for.
- A ranked registerEvery deficiency with its crash-risk score and what blocks the view, so the worst is the first fixed.
Safety Dashboard
Connect the findings to the crashes
A deficiency is only half the story. The Safety Dashboard puts a corridor’s findings next to your state’s crash records — every crash, by severity, on the same mileposts — so a run of blocked sight distance stops being a note on a map and becomes a place where drivers are crashing.
RDV’s safety engineers work it with you: choose the analysis, the direction and the corridors, and the dashboard answers whether crashes really concentrate at the deficiencies, then prices what fixing them would be worth.
86
Crashes in the filter
on 10.11 mi of selected corridor
8.51
Crashes per mile
both directions of SR-102
1 / 13 / 71
Fatal / injury / property damage
severity split of those crashes
8
Stopping sight distance runs
0.36 mi — 3.6% of the corridor
8%
Crashes beside a run
within 0.1 mi, four of them inside one
$986K / yr
Expected savings
if the priced countermeasures are built
Ask one question at a time
Filter to an analysis, a direction, a milepost range and the corridors you care about. The map, the counts and the benefit figures all follow the filter.
Both layers on one map
Deficiency runs drawn by severity, crashes by severity — fatal, injury, property damage, animal strike — plus crash clusters, intersection sight-distance rings and glare-time matches.
Milepost by milepost
Under the map each corridor breaks down in route order: the crashes, the deficiency runs and the intersections on every stretch.
A statistical verdict, not a hunch
A permutation test against random placement on the same corridor says whether the crashes really do concentrate at the deficiencies, per analysis.
A priced countermeasure program
Crash modification factors from the FHWA CMF Clearinghouse and FHWA crash costs give crashes prevented, annual benefit and a benefit-cost ratio for every site — the numbers an HSIP application asks for.
Intersection priorities
Every junction in the state data ranked by comprehensive crash cost, or by what a countermeasure there would be worth.
Crash data comes from the state’s own dataset, matched to your corridors by milepost. Massachusetts is connected today; other states follow as their data is loaded.
Designs, not only scans
No LiDAR? No problem
If the road exists only as a design, the audit still runs. RSA 3D began on CAD models — sight distance checked on proposed geometry — and only later learned to read LiDAR of roads already built. Both still run on the same platform, against the same standards.
Send what your designers already work in
Bentley MicroStation and OpenRoads, Autodesk Civil 3D and InfraWorks, SketchUp, or a plain DGN or DWG. We build the 3D model from the design files themselves — nothing has to be redrawn for the audit.
The same analyses, the same standards
Stopping, passing and intersection sight distance, curves, clear zone and the rest, measured on the design surface against the same AASHTO criteria a scan is held to.
Findings while they are still cheap to fix
A sight line that fails on the model costs a design revision. The same failure found after construction costs a change order, a retrofit — or a crash record.
Alternatives, compared before anyone commits
Run each alternative and see which geometry actually drives safely, then take the answer to the design review with the model to show for it.
A design run hands back the same reports, video and tables, plus a colour-coded CAD drawing of the maximum safe speed at every location — in a form the design team can take straight back into the model. See it on the Henderson Interchange.
How a run works
From point cloud to findings, without a workstation
Upload the scan
LAS and LAZ point clouds, multi-gigabyte files included. Uploads resume after a dropped connection, and scans in state plane feet or WGS84 are reprojected to the project's coordinate system automatically.
Prepare the point cloud
The scan is split into tiles, the ground is classified, a Point Transformer V3 model finds the road surface and parked and passing vehicles are removed.
Run the analyses
Sight lines are rendered on GPUs station by station, across hundreds of parallel cloud jobs, and an AI model names what blocks each failing view.
Deliver the findings
Reports, an online report for every road, drive-through video, CSV tables and shapefiles land in the project folder, ready to review.
The platform
Built for the whole network
Cloud scale
A run fans out across up to 180 parallel jobs a stage, with GPU rendering for visibility. Reruns reuse the prepared scan instead of processing it again.
3D viewer in the browser
Stream the project in full 3D with saved views, environment settings, layers, animations and virtual tours.
Routes on the map
Draw paths and lanes over the scan on a map, or build routes from a road and milepost range where state milepost data is connected.
Secure sign-in
Two-factor sign-in with an authenticator app, and roles that keep each manager and user to their own projects.
Analyses follow the AASHTO Green Book (7th edition), the AASHTO Roadside Design Guide and the MUTCD.
Run your first corridor in 123BIMLive
Send us a LiDAR scan of one road and see every finding for it in your own project.