Mobile pavement data collection system operating on a municipal roadway
Pavement & Asset Management

Know the network. Plan the work.

Engineer-led roadway assessments that turn pavement condition, geometry, imagery, and asset data into defensible maintenance priorities.

Engineer-led QA/QC Automated processing with accountable review
Condition + geometry PCI, IRI, rutting, imagery, and distress data as scoped
Esri-ready delivery Useful GIS data without unnecessary lock-in
Right-sized collection Roadway and sidewalk configurations
From data to action

One survey. Multiple decisions.

Eclipse combines right-sized field collection, efficient processing, and engineering judgement so municipalities can understand current conditions, set priorities, and build a practical capital plan.

01 / INSPECT

Capture the network

Collect synchronized geometry, location, and visual records while limiting traffic disruption and repeat field work.

02 / ANALYZE

Measure what matters

Translate raw observations into segment-level condition, deterioration, safety, and asset information.

03 / ACT

Prioritize the work

Connect condition to treatment timing, budget scenarios, and the next engineering or permitting decision.

Decision support

See the network clearly.

Move from scattered files to a map-based view of condition, assets, priorities, and planned investment.

Conceptual municipal pavement and asset management dashboard

Conceptual interface shown with synthetic data. Final dashboards and metrics are configured to the client's scope, standards, and systems.

Collection system

Built around the work.

Our planned modular platform combines complementary sensors instead of forcing every project into one fixed collection package.

01

Wide-field 3D LiDAR

A Blickfeld Robin W–based configuration is planned for roadway and right-of-way geometry, spatial context, and asset location.

02

Dual laser profilers

LMI Gocator line profilers support transverse pavement geometry, cross-section measurements, and rut-depth analysis.

03

360° imagery

An Insta360-based visual record connects observed conditions and assets to their real-world roadway context.

04

RTK positioning

RTK GNSS and inertial positioning tie field observations to usable coordinates and consistent project control.

05

Stationing + time sync

Wheel-encoder distance and synchronized timestamps align sensor streams for repeatable processing and review.

06

Modular deployment

A transferable hitch-mounted platform supports roadway collection, with a plug-in bike-trailer approach planned for sidewalks.

Equipment is configured and validated for the required deliverables; final sensors, methods, tolerances, and standards are confirmed during scoping.

Field operations

Collect with confidence.

A Linux-based acquisition workflow is planned to give the operator a clear view of route progress, sensor health, positioning, storage, and locations that need follow-up.

Live status for each connected sensor
Route progress and collection speed
Time synchronization and data storage checks
Operator marks for review or recollection
Conceptual field data collection dashboard

Conceptual field interface. The production layout will evolve through hardware integration, testing, and operator feedback.

Deliverables

Data your team can use.

Deliverables are tailored to the decision—not just the sensor—and can be structured for direct use in Esri and common municipal workflows.

01

Condition data

Segment ratings, distress locations, rutting and cross-section results, plus PCI or ride-quality measures when included in the validated scope.

02

Visual record

Georeferenced roadway imagery that helps staff verify findings, answer questions, and reduce unnecessary return trips.

03

Asset inventory

Signs, markings, curb ramps, sidewalks, curbs, and drainage assets can be inventoried when included in the project scope.

04

GIS delivery

Esri geodatabases, web maps, dashboards, tabular exports, and clear data dictionaries built around client ownership and reuse.

05

Treatment plan

Segment-level preservation, rehabilitation, and reconstruction recommendations linked to observed condition and service goals.

06

Budget scenarios

Prioritized programs and multi-year scenarios that show what different funding levels can accomplish across the network.

Our process

Clear from start to finish.

We define the decision first, then match the collection, analysis, and review effort to it.

01

Define

Confirm decisions, standards, assets, accuracy, and outputs.

02

Collect

Capture synchronized field data with in-field quality checks.

03

Process

Align, calculate, classify, and flag results for review.

04

Verify

Review flagged locations, spot-check outputs, and resolve gaps.

05

Deliver

Provide usable data, priorities, documentation, and next steps.

Quality control

Automation helps. Engineers decide.

Scripting and automated analysis can accelerate calculations, organize large datasets, and identify locations that need attention. Engineering review remains part of the deliverable.

Every flagged location reviewed
Independent checks of other calculations
Dedicated professional-engineer QC
Targeted field verification when needed
Why Eclipse

Right-sized by design.

The goal is not to collect the most data. It is to collect the right data, verify it, and turn it into a decision your team can defend.

01

Direct access

Work with the professionals responsible for the field plan, analysis, and recommendations.

02

Useful ownership

Receive documented, reusable data that fits your GIS and management workflow.

03

Next-step engineering

Carry findings into design, drainage, permitting, budgeting, and implementation support.

Start a conversation

Bring us the network question.

We will help define the collection level, deliverables, and quality controls needed to make the next decision.

Discuss your project