Problem Statement / Industry Context

A significant majority of U.S. Departments of Transportation (DOTs) rely on AASHTOWare as a system of record for construction management workflows, including but not limited to:

• Daily Work Reports (DWRs)

• Inspections

• Quantity tracking and payment applications

• Change order management

• Safety and compliance forms

While Bentley Infrastructure Cloud (BIC) is increasingly used by DOTs, consultants, and contractors as a Common Data Environment (CDE) for design and construction information, AASHTOWare remains contractually and operationally required across many DOT programs. This creates a persistent challenge for field users—especially inspectors—who are forced to enter the same data twice across multiple platforms to satisfy both modern digital delivery initiatives and legacy/mandated systems.

DOTs and industry partners are explicitly asking for a seamless integration that allows BIC to coexist with AASHTOWare, rather than attempting to replace it.

Proposed Solution Overview

Introduce a first‑class API integration between Bentley Infrastructure Cloud Digital Forms and AASHTOWare (e.g., AASHTOWare Project) that allows form data entered in BIC—via web or mobile—to be programmatically transmitted into corresponding AASHTOWare records using AASHTOWare’s available Open APIs.

This integration would allow BIC to serve as the primary field data capture experience, while AASHTOWare continues to function as the DOT’s authoritative construction management system.

Example Workflow: Daily Work Reports (DWRs)

Current State (Pain Points)

• Inspectors enter Daily Work Reports in AASHTOWare Project.

• The same inspectors are often asked to also capture photos, notes, quantities, and locations in BIC for project documentation, digital delivery, or internal reporting.

• This results in:

  • Duplicate data entry

  • Increased field time and frustration

  • Higher risk of data inconsistency or errors

  • Reduced adoption of BIC forms in the field

Proposed Future State (Integrated Workflow)

1. Inspector completes a Daily Work Report using a BIC Digital Form

   • Accessible via BIC Web Portal or Mobile

   • Works online or offline (where supported)

2. Form captures structured “binding” data, such as:

   • Date

   • Inspector name

   • Project number

   • Station / Offset

   • Location (Latitude / Longitude)

   • Line item number for quantity claiming

   • Quantity installed or observed

   • Attachments (photos, PDFs, sketches)

3. BIC Form follows the configured workflow

   • Review and approval steps

   • Validation rules

   • Role‑based permissions

4. Upon submission or approval, BIC sends the bound data to AASHTOWare via API

   • Data is mapped to the appropriate AASHTOWare entity (e.g., DWR entry, quantity record)

   • Attachments are included or referenced per AASHTOWare API capabilities

   • Transaction status is logged for traceability

5. Result

   • Inspector enters data once

   • AASHTOWare remains fully populated and compliant

   • BIC remains the active CDE for construction documentation and collaboration

This aligns directly with industry feedback that AASHTOWare is deeply embedded in DOT workflows and that API‑based accommodation—not replacement—is the preferred path forward.

Key Value Proposition

For DOTs

• Maintains AASHTOWare as the required system of record

• Reduces data discrepancies between platforms

• Supports digital delivery mandates without disrupting existing programs

For Field Users (Inspectors, CEI Staff)

• Eliminates double data entry

• Enables mobile‑first workflows

• Reduces time spent on administrative tasks

For Bentley

• Positions BIC as the central construction CDE while respecting DOT constraints

• Improves adoption of Digital Forms and Mobile workflows

• Strengthens Bentley’s interoperability story against competitors

• Creates a scalable integration opportunity applicable to 80%+ of DOTs using AASHTOWare in some capacity

Technical Considerations (High‑Level)

• Leverage AASHTOWare Open APIs for data exchange

• Utilize BIC Digital Forms bindings as the canonical data mapping layer

• Support configurable field‑to‑field mappings per DOT implementation

• Allow integration to be delivered via:

  • BECS‑managed connector, or

  • Platform‑level integration service

Strategic Impact

This integration directly supports Bentley’s broader strategy of positioning Bentley Infrastructure Cloud as the hub for construction data, while acknowledging the contractual and regulatory realities faced by DOTs. It enables Bentley to meet agencies where they are today, while still advancing modern, mobile, and model‑centric workflows across the construction lifecycle.