SCDMV & Toll Interface Gateway
Tier 1 — CriticalLegacy gateway between SCDOT systems and the SCDMV Phoenix mainframe: real-time vehicle registration verification for oversize/overweight permits, toll violation owner lookups for the toll interoperability program, and CDL verification batch jobs.
- Business Owner
- P. Ashford — Director of Right of Way & Permits
- Right of Way & Permits
- Technical Owner
- W. Greer — Legacy Systems Supervisor
- Hosting
- Mainframe
- State IBM z/OS (DTO-managed); CICS transactions + nightly batch to SCDMV Phoenix
- Platform / Vendor
- COBOL/CICS on state IBM z/OS (Phoenix interfaces)
- Data Classification
- Restricted
- User Base
- OSOW permit office (~40 staff), toll back office, automated batch consumers
Business Impact Assessment
Scored 1 (negligible) to 5 (severe) across the six impact categories from the Phase I BIA scope.
OSOW permit issuance (~$14M/yr) and toll violation recovery halt.
Toll interoperability agreements (E-ZPass Group) carry lookup-timeliness obligations.
Highest-fragility item in the portfolio: aging COBOL, one remaining developer, batch-window contention with DTO workloads.
Recovery Objectives
Proposed via BIA- Minimum availability
- 99%
- Service window
- Business hours (CICS) + nightly batch 22:00–02:00
Workaround Feasibility
Manual SCDMV phone verification possible at ~10% throughput; toll lookups have no manual path at volume.
Dependencies
Systems, vendors, data feeds, infrastructure, and personnel this application depends on. Single points of failure are flagged.
| Dependency | Type | SPOF | Notes |
|---|---|---|---|
| SCDMV Phoenix mainframe | System | SPOF | External agency system; single interconnect |
| DTO z/OS platform operations | Infrastructure | — | — |
| Sole COBOL/CICS maintainer | Personnel | SPOF | Key-person risk: retirement eligible 2027 |
| Nightly batch window | Infrastructure | — | Contended with DTO batch schedule |
Tier Assignment Traceability
Financial and legal scores of 4 with revenue stoppage and interstate tolling obligations (R2 boundary case): assigned Tier 1 given likelihood 4 and absence of scalable workaround.