Ingress / Case Studies / State DOT Data Analytics

One dashboard for eight bureaus, built in-boundary.

A state Department of Transportation unified reporting across 8 bureaus, automated monthly reports, and delivered 14 executive dashboards in Azure Government.

SectorState Government
TypeData Analytics
Staff4,200
The Challenge

Eight bureaus, eight separate reports.

A state Department of Transportation with 4,200 staff across 8 bureaus generated monthly reports in Excel. No unified data warehouse. No cross-bureau visibility. No real-time dashboards.

The Situation

Each bureau reported separately: project status, spend, staffing, infrastructure condition. Data lived in 8 different systems (project management, finance, HR, maintenance logs). The state DOT director received roll-up summaries weeks after month-end, built manually by analysts combining spreadsheets.

No real-time visibility. No way to cross-check spending across bureaus. GIS data on road conditions and asset maintenance sat in a separate system, rarely integrated. Monthly reporting took 300+ hours of analyst time.

The Opportunity

Azure Government and Power BI offered a path to centralized reporting. A single data warehouse could pull from all 8 source systems, apply row-level security to maintain bureau-level data access, and serve live dashboards for executives and bureau directors.

Automation could replace manual month-end consolidation. GIS integration would enable visual asset and condition reporting. StateRAMP-aligned infrastructure would meet compliance requirements.

Our Approach

Centralized warehouse with bureau-level security.

We built a data integration and reporting platform on Azure Government, respecting state data boundaries and bureau autonomy.

01
Data Inventory & Requirements
Audited 8 bureau systems. Identified data sources: project management (Smartsheet), finance (SAP), HR (PeopleSoft), maintenance logs (custom apps), GIS (Esri ArcGIS). Documented data quality, completeness, and compliance requirements. Bureau directors defined dashboard requirements and KPIs.
Weeks 1-6
02
Azure Government Data Warehouse
Built centralized schema on Azure SQL Database (Azure Government). Defined fact tables (projects, spend, staffing) and dimensions (bureaus, cost centers, locations). Optimized for 2-year rolling data and fast query performance for 100+ concurrent dashboard users.
Weeks 6-14
03
Data Integration via ADF
Implemented Azure Data Factory pipelines to pull from 8 source systems nightly. Data quality checks and reconciliation. Daily refresh ensures dashboards show yesterday's data. Logging and monitoring in Azure Monitor.
Weeks 12-20
04
Power BI Reporting & Security
Built 14 dashboards: 8 bureau-specific, 5 executive cross-bureau, 1 compliance/audit. Implemented row-level security: bureau staff see only their data, directors see their bureau plus state totals. GIS visualization for asset and road condition mapping.
Weeks 16-28
05
Training & Rollout
Power BI training for 80 bureau analysts and directors. Change management communication. Month-end reporting process redesigned and automated. Live go-live across all bureaus.
Weeks 24-30
The Outcomes

Automation, visibility, and compliance.

8

Monthly Reports Automated

Excel-based bureau reports replaced by automated Power BI delivery. Dashboards refresh nightly. 300+ analyst hours per month saved and reallocated to strategic analysis.
65%

Faster Report Prep

Month-end closing process reduced from 15 days to 5 days. Data consolidation is now automatic, freeing analysts for insights and exception investigation.
14

Executive Dashboards Live

Real-time visibility into projects, spend, staffing, and infrastructure condition across all 8 bureaus. Bureau directors have instantaneous access to their data and state totals.
Tech Stack

Azure Government + Power BI + Esri GIS.

1

Azure Government

Sovereign cloud for state data. SQL Database for warehouse, Data Factory for ETL, Monitor for logging. StateRAMP-aligned boundary.
2

Azure Data Factory

Orchestrates nightly extracts from 8 source systems. Data quality checks, transformation logic, and error handling. Pipelines logged and monitored.
3

Power BI Premium

Enterprise reporting and dashboarding. Row-level security by bureau. Dashboards embedded for bureau staff and directors. Refresh schedule: daily, with 4-hour delta for intraday updates.
4

Esri ArcGIS

GIS integration for road network and asset visualization. Road condition mapping tied to maintenance and project data. Spatial analysis of infrastructure priorities.
Key Lessons

Why unified reporting works in government.

Bureau Autonomy, Not Centralization

We didn't force data standardization or consolidate bureau systems. We built a reporting layer on top of existing systems, with row-level security that let each bureau see only their data by default. Security and autonomy, plus visibility at the state level.

GIS as Strategic Asset

Integrating ArcGIS unlocked visual, spatial analysis of road conditions and asset maintenance. Executives could now see where potholes were concentrated, where maintenance was overdue, and prioritize spending geographically. Map-based insights drove better decisions.

Data Quality Requires Ongoing Discipline

The first month revealed data inconsistencies: project codes that didn't match across systems, spend allocated to wrong cost centers, incomplete maintenance logs. We built reconciliation dashboards that surfaced these discrepancies weekly. Bureau directors quickly fixed data entry processes.

StateRAMP Alignment from Day One

Building on Azure Government and documenting controls upfront meant compliance reviews were straightforward. No retrofit. The system was born StateRAMP-aligned, which shortened agency sign-off and reduced ongoing audit risk.

Start a conversation

Tell us what's worth doing.

// 30 minutes โ†’ a written brief.

Bring the problem. We'll come back with a written brief: what to build, what to defer, and where AI actually moves the number. No deck pitches.

Emailconnect@ingressits.com
GSA MAS#47QTCA26D000K
Reply< 24 hrs