Site, zone and scan IDs keep new observations attached to the same physical place.
AssetGuard™ / Infrastructure evidence layer
From field observation
to a useful asset record.
For transportation and public-infrastructure teams, AssetGuard by SlabWorx organizes repeat observations into identified, evidence-linked records that a human reviewer can compare, approve, and hand off. It sits above the capture tools you already use, giving each asset a durable memory without replacing the responsible inspector or engineer.
THE SELLABLE UNIT One bounded asset class · one shared evidence record · one measurable comparison.
SYNTHETIC DEMONSTRATION This example is fictional. It is not a VTrans asset, inspection, finding, endorsement, or funded project. The background image is conceptual—not field evidence.
Read the signal
The value is continuity.
This demonstration is designed to make one operational question easy to test: can the next inspection produce a more complete, comparable and portable record than the last one?
A baseline and follow-up show how a reviewer can describe change without inventing a diagnosis.
Approved records can travel as a versioned manifest alongside the team’s existing workflow.
Decision support stays reviewable, attributable and bounded before it reaches a deliverable.
01 / Capture and compare
The record can be checked,
not just admired.
Switch between two approved, fictional observations. A field reviewer entered the measurements and condition classification. The outlook summarizes change; it does not diagnose a structure or certify safety.
Illustrative concrete bridge approach slab
Fictional Zone N-1 · North approach · Vermont example geography, no actual address
- Record
- AG-DEMO-001
- Capture
- Phone imagery + field notes
- Operator
- Illustrative field reviewer
- Status
- Approved for demo
A baseline observation establishes an identified zone record. A comparable follow-up is needed before a direction of change can be described.
Stable IDs keep observations on the same physical area.
Capture metadata and field notes remain attributable.
Draft records do not enter the approved outlook or export.
The package omits pricing, private tickets, secrets, and raw media.
Download a synthetic, versioned AssetGuard/NEDD JSON package for the follow-up record. It is an example manifest, not a live VTrans integration or raw evidence bundle.
02 / Evaluation, not a promise
A small pilot with a clear control.
Start with a VTrans-selected asset class and a conventional inspection baseline. Compare the same defined zones and deliverables before deciding whether AssetGuard adds value.
Agree the test
Choose assets, access rules, condition taxonomy, retention requirements, a technical champion, and the existing inspection workflow.
Capture both ways
Run the existing practice and AssetGuard-assisted field capture on the same bounded sample; preserve reviewer authority.
Measure the difference
Compare field time, report turnaround, repeatability, defect evidence completeness, and usefulness of the longitudinal record.
Decide with evidence
Document results and limits. Scope any next phase through the applicable competitive research or procurement process.
Site/zone records, approved observations, evidence-linked condition outlook, PDF report generation, and an authorized NEDD JSON export exist in the web app.
VTrans-specific taxonomy, data-sharing authorization, IT/security review, baseline metrics, agency-system integration, and any field validation are not yet complete.
No autonomous structural diagnosis, automatic GPR interpretation, stamped engineering opinion, VTrans certification, agency endorsement, or guaranteed funding.
Built in Vermont · By SlabWorx
Give the next inspection
a better memory.
Discuss a bounded comparison, the data contract, and the technical questions before anyone commits to a larger rollout.