Road Inventory Management System
Tier 2 — ImportantInventory of record for the 41,000+ centerline-mile state system: route logs, pavement/lane attributes, functional classification, and traffic counts. Produces the annual HPMS submission that drives federal apportionment data.
- Business Owner
- S. Delgado — Director of Planning
- Planning & Environmental
- Technical Owner
- V. Okafor — Data Services Manager
- Hosting
- On-Premises
- SCDOT data center; Oracle 12c — past extended support
- Platform / Vendor
- Legacy Oracle Forms (modernization candidate)
- Data Classification
- Internal
- User Base
- ~180 planning and district staff
Business Impact Assessment
Scored 1 (negligible) to 5 (severe) across the six impact categories from the Phase I BIA scope.
HPMS submission (June 15 annually) feeds federal apportionment; late/incomplete data has direct funding consequence.
Old but stable; database platform past extended support is the main risk.
Recovery Objectives
Proposed via BIA- Minimum availability
- 99%
- Service window
- Business hours
Workaround Feasibility
Read-only extracts cover most consumers; edits queue. During HPMS season (Apr–Jun) tolerance drops sharply.
Dependencies
Systems, vendors, data feeds, infrastructure, and personnel this application depends on. Single points of failure are flagged.
| Dependency | Type | SPOF | Notes |
|---|---|---|---|
| Traffic count program feed | Data Feed | — | — |
| OneMap Enterprise GIS | System | — | Bi-directional LRS sync |
| Oracle 12c platform (unsupported) | Infrastructure | SPOF | Past extended support; restore path fragile |
| FHWA HPMS portal | Data Feed | — | — |
Tier Assignment Traceability
Federal compliance score of 5 tied to an annual deadline with workaround capacity (R3): Tier 2, with a documented seasonal tolerance change during HPMS season.