UGAF-ITS: A Standards Harmonization Framework and Validation Tool for Multi-Framework AI Governance in Distributed Intelligent Transportation Systems
Organizations: Higher Colleges of Technology, Fujairah, United Arab Emirates · Central Michigan University, Mount Pleasant, United States of America
Abstract
Organizations deploying AI-enabled Intelligent Transportation Systems face fragmented governance: ISO/IEC42001 demands a certifiable management system, the EU AI Act imposes binding high-risk obligations from August2026, and the NIST AI Risk Management Framework structures voluntary practice. This paper introduces UGAF-ITS, a standards harmonization framework that consolidates 154 source obligations from the three instruments into 12 unified controls across eight governance domains through a reproducible five-phase crosswalk methodology. A three-tier operating model allocates each control to the vehicle, edge, or cloud tier where enforcement and defensible evidence production are feasible. An evidence backbone of 20 versioned artifacts supports a single audit package across all three frameworks without duplicating content. We evaluate UGAF-ITS through an open-source governance engine applied to four architecturally distinct ITS deployment scenarios. The engine encodes the complete crosswalk catalog and executes eight compliance computations. Three-tier deployments achieve 91.7% average scoped framework coverage with 45.9% evidence reduction, complete bidirectional traceability, and 80% of artifacts serving all three frameworks simultaneously. Partial deployments contract predictably, with reduction holding between 25% and 50% across archetypes. The siloed baseline is enumerated document by document and computed by the tool at run time. These results establish structural properties of the harmonized catalog under architectural variation. They do not establish operational compliance readiness, which external assessment with practitioners has yet to test. The tool, scenarios, and all reported results are publicly available for independent replication.
Figures & tables
| Framework | Structure | Key Requirements | ITS Relevance | Compliance |
| ISO/IEC 42001:2023 | Clauses 4–10 (PDCA cycle) + 38 Annex A controls across 9 control areas | AI management system; risk assessment & treatment; human oversight; data governance; continuous improvement | Certifiable management system for OEMs and service providers | Voluntary; Certifiable |
| EU AI Act (2024/1689) | Articles 8–15 (high-risk) + Annexes III, IV, VI; 45 obligations | Risk management system; technical documentation; transparency & human oversight; accuracy & robustness; cybersecurity | ITS classified high-risk (Annex III); mandatory for EU market | Mandatory; Aug 2026 |
| NIST AI RMF 1.0 | 4 functions: govern , map , measure , manage ; 72 subcategories across 19 categories | Trustworthy AI principles; context mapping & risk measurement; continuous monitoring; incident response; stakeholder engagement | Implementation guidance; U.S. federal alignment; international interoperability | Voluntary; Best practice |
| PDCA = Plan-Do-Check-Act. High-risk AI under the EU AI Act includes vehicle safety components (Annex III, §2) and traffic management AI affecting road safety. The 45 EU AI Act obligations listed here reflect the full high-risk requirement set; the crosswalk extraction (Section 4.1 ) scopes this to 37 implementable technical obligations after excluding conformity assessment body, market surveillance, and CE marking procedural items. | ||||
| Category | Reference | Domain | ISO 42001 | EU AI Act | NIST RMF | ITS Tiers | Crosswalk | Validation |
| General AI Governance | ||||||||
| Forrester AEGIS [ 26 ] | General AI | ● | ◐ | ● | ○ | ◐ | Conceptual | |
| Credo AI UCF [ 9 ] | General AI | ◐ | ● | ● | ○ | ○ | Colorado case | |
| CSA/ISACA [ 8 ] | General AI | ● | ● | ● | ○ | ○ | Guidance only | |
| Automotive & AV Safety | ||||||||
| ISO/PAS 8800 [ 17 ] | Automotive | ○ | ○ | ○ | ◐ | ○ | Standard | |
| T1 | T2 | T3 | Classification and action | Instance |
|---|---|---|---|---|
| ✓ | ✓ | sym. | Full alignment. One control, one artifact binding | UC-01 risk register |
| ✓ | ✓ | asym. | Dominant strictness. Control takes the stronger objective; weaker atom trace-linked; ADR recorded | UC-07, Annex IV dominant |
| ✓ | any | Evidence-divergent overlap. One control, several artifact bindings | UC-03 data quality | |
| ✓ | any | incomp. | Conjunctive merge. Control takes the conjunction; both atoms trace-linked | UC-05, UC-06 oversight |
| same obj. | n/a | Framework-specific extension. Trace-linked to nearest control, no merge | Annex IV sub-items | |
| ext. actor | n/a | External actor. Excluded at Phase 1, reported as gap class | Conformity assessment |
| Domain | UC | Control Name | Control Objective | ISO 42001 | EU AI Act | NIST RMF | T1 | T2 | T3 |
| D1 Risk Management | 01 | AI Risk Assessment | Identify and evaluate AI-specific risks incl. safety, bias, and security | Cl. 6.1; A.4.1–4.3 | Art. 9(2a–c) | map 5.1–5.2 | |||
| 02 | Risk Treatment | Implement controls to mitigate identified risks to acceptable levels | Cl. 8.3; A.5.1–5.2 | Art. 9(2d), 9(5) | mg 1.2–1.4 | ||||
| D2 Data Governance | 03 | Data Quality Assurance | Ensure training/validation data quality, completeness, representativeness | A.7.1–7.3 | Art. 10(1–4) | map 2.3; me 2.6 | |||
| 04 | Bias Detection & Mitigation | Monitor for and address unfair bias in data and model outputs | A.7.4 | Art. 10(2f–g) | me 2.10–2.11 | ||||
| D3 Human Oversight | 05 | Human Oversight Design | Design systems enabling effective human understanding and intervention | Cl. 5; A.15.1–15.2 | Art. 14(1–3) | gv 3.2; map 3.5 | |||
| 06 | Override & Intervention | Implement mechanisms for human override and safe system interruption | A.15.3–15.4 | Art. 14(4–5) | mg 2.4 |
| Stage | Result |
|---|---|
| Extraction | 12 atoms: ISO A.6.2.3, A.7.1–A.7.3; EU Art. 10(1)–10(5); NIST MAP 2.1–2.3 |
| Coding | Domain D2; tiers T2, T3; phases design, build, monitor |
| Intent test | Passes within the cluster; fails against bias atoms, which split to UC-04 |
| Strictness test | Asymmetric. Article 10 dominates; ISO and NIST atoms trace-linked |
| Extension | Art. 10(5) retained; no ISO or NIST counterpart |
| Unified control | UC-03 Data Quality Assurance, active at T2 and T3 |
| Tier | Components (examples) | Unified Controls | Evidence Sources (examples, operational strategic) | Owner |
|---|---|---|---|---|
| T1 Vehicle | ADAS perception, driver monitoring, V2X client, local planning under ODD constraints | UC-05, UC-06, UC-09, UC-10 UC-07 | Oversight Protocol; Intervention & Fallback Plan; Event & Override Logs; V&V Test Report (ODD-scoped); Security Test Report; Release Manifest | OEM vehicle operator |
| T2 Edge/RSU | VRU detection, adaptive signal logic, V2I gateways (e.g., SPaT/MAP), local decision engines | UC-03, UC-04, UC-08, UC-12 UC-06, UC-10 | Data Quality Report; Bias & Performance Report; Configuration Baseline (site + calibration); RSU Decision Logs; Monitoring & Alerting Plan; Escalation Record | Road authority + integrator |
| T3 Cloud | TMC analytics, cross-site monitoring, model registry, training/evaluation pipelines, OTA distribution | UC-01, UC-02, UC-07, UC-11, UC-12 UC-09, UC-10 | Risk Register + Treatment Log; Technical File; Supplier Audit Report; Third-Party Component Register; Incident Ticket Log; Model Change Notice; Deployment Record; Post-Deployment Monitoring Report | Authority ops / cloud operator |
| Configuration | Diverges | Framework response | Declared outside the model |
|---|---|---|---|
| Shared responsibility | A O | Split into production duty at O and acceptance duty at A | Evidence exchange contract |
| Outsourced operation | C A | UC-11 assessment at the procuring entity; Article 25 reclassification checked | Service contract and rebranding terms |
| Cross-tier ownership | E spans tiers | Control instantiated per tier with one lead instance | Consolidation lead and retention terms |
| Absent-tier accountability | A has no tier | Reported as ownership ambiguity (F4) | Contractual evidence flow-down |
| Level | Question answered | Procedure | Cannot support | Status |
|---|---|---|---|---|
| L1 Internal verification | Is the encoded catalog self-consistent? | Exhaustive traversal of forward and reverse trace links across 154 obligations, 12 controls, and 20 artifacts | Correctness of the mappings against expert judgment | Performed |
| L2 Scenario demonstration | Do structural properties hold as architecture varies? | Identical computations executed across four deployment archetypes from three-tier to single-tier | Audit adequacy or usability in a live deployment | Performed |
| L3 External validation | Do practitioners agree, and does the framework work in the field? | Independent expert assessment, practitioner audits with the engine, operational deployment | Not applicable, since the level is not performed | Outstanding |
| Dimension | Metric | Urban | Highway | Transit | Rural |
|---|---|---|---|---|---|
| Architecture | Active tiers | T1–T3 | T1–T3 | T2, T3 | T2 |
| AI components | 12 | 7 | 5 | 2 | |
| Stakeholders | 3 | 3 | 2 | 1 | |
| M1: Coverage | ISO/IEC 42001 | 94.5% | 94.5% | 94.5% | 92.7% |
| EU AI Act | 91.9% | 91.9% | 91.9% | 89.2% | |
| NIST AI RMF | 88.7% | 88.7% | 88.7% | 82.3% |
| Domain | ISO | EU | NIST | Total | UCs | Ratio |
|---|---|---|---|---|---|---|
| D1 Risk Management | 23 | 6 | 24 | 53 | 2 | 96% |
| D2 Data Governance | 5 | 7 | 5 | 17 | 2 | 88% |
| D3 Human Oversight | 7 | 5 | 3 | 15 | 2 | 87% |
| D4 Transparency | 5 | 3 | 3 | 11 | 1 | 91% |
| D5 Accuracy & Robustness | 3 | 5 | 8 | 16 | 2 | 88% |
| D6 Documentation | 4 | 8 | 4 | 16 | 1 | 94% |
| Clustering level | Controls | Consolid. | Tri-fw | Tier sigs. |
|---|---|---|---|---|
| L1 coarse, one per domain | 8 | 94.8% | 100% | 4 |
| L2 published, object action | 12 | 92.2% | 100% | 4 |
| L3 fine, one per framework | 36 | 76.6% | 0% | 4 |
| Criterion | Siloed | Fw-first | Control lib. | UGAF-ITS |
|---|---|---|---|---|
| Fw coverage | High | Part.–High | High | High |
| Control consolidation | None | Partial | Yes | Yes |
| Tier allocation | None | None | None | Yes |
| Evidence reuse | None | Partial | Partial | Yes |
| ITS specificity | No | No | No | Yes |
| Traceability | Per-fw | Partial | Partial | Bidirect. |
| Phase | Activity | Timeline | Key Output |
|---|---|---|---|
| 1. Architecture mapping | Map deployed AI components to vehicle, edge, and cloud tiers; identify ownership boundaries | Weeks 1–2 | Tier map and stakeholder RACI |
| 2. Gap assessment | Assess current artifacts against the 12 unified controls (Table 4 ) | Weeks 3–4 | Gap register per tier |
| 3. Evidence infrastructure | Establish the Technical File as shared infrastructure with version control and trace links | Weeks 5–8 | Technical File skeleton and trace map |
| 4. Priority closure | Close gaps for high-risk AI components and cross-tier incident pathways | Weeks 9–16 | Populated evidence backbone |
| 5. Audit readiness | Conduct an internal walkthrough simulating framework-specific audit questions | Week 17+ | Validated audit package |
Appendix figures & tables1 asset
Supplementary material from the paper’s appendix.
Appendix
| ID | Document | Source | Tiers | Evidences |
| ISO/IEC 42001 (15 documents) | ||||
| ISO-D01 | AI policy | Cl. 5.2 | T3 | UC-01 |
| ISO-D02 | AIMS scope statement | Cl. 4.3 | T3 | UC-01 |
| ISO-D03 | Roles and responsibilities record | Cl. 5.3 | T3 | UC-01 |
| ISO-D04 | AI risk assessment results | Cl. 6.1, 8.2 | T1–T3 | UC-01 |
| ISO-D05 | Risk treatment plan and Statement of Applicability | Cl. 6.1, 8.3 | T3 | UC-02 |