Real-Time System Management Information Program Data Exchange Format Specification

Printable version [PDF 1.5 MB]
You may need the Adobe® Reader® to view the PDFs on this page.
Contact Information: OperationsFeedback@dot.gov

Table of Contents

Executive Summary

Real-Time System Management Information Program (RTSMIP)

Data Exchange Format Specification (DXFS)

Users of the DXFS

1. Introduction

1.1 Scope

1.2 References

1.3 General Statements

1.4 Terms

1.5 Abbreviations

2. Concept of Operations

2.1 Introduction

2.2 Background, Objectives, and Current System or Situation

2.2.1 Background

2.2.2 Objectives of the DXFS

2.2.3 Description of the Current Situation

2.2.4 Stakeholders

2.3 Reference Physical Architecture

2.3.1 Transportation Agency Systems

2.3.2 Transit Agency Systems

2.3.3 Peer Transportation Agency Systems

2.3.4 Public Safety Agency Systems

2.3.5 Private Data Collection Organization Systems

2.3.6 Travelers

2.3.7 Public Traveler Information Provider Systems

2.3.8 Private Third Party Providers Systems

2.3.9 Other Public Agencies Systems

2.4 Architectural Needs

2.5 Features

2.5.1 Introduction to User Needs

2.5.2 Travel Time User Needs

2.5.3 Incident Information User Needs

2.5.4 Construction Information User Needs

2.5.5 Weather Information User Needs

2.5.6 Transit Information User Needs

2.5.7 Roadway Network Information Needs

2.5.8 Connection Management User Needs

2.6 Security

2.7 Operational Policies and Constraints

2.8 Relationship to the National ITS Architecture

2.8.1 Entities

2.8.2 Interfaces

2.9 Operational Scenarios

2.9.1 Introduction to Operational Scenarios

2.9.2 Managing the Surface Transportation System Using Real Time Information

2.9.3 Maintaining the Surface Transportation System Using Real Time Road Weather Information

2.9.4 Share Information with the Traveling Public

2.9.5 Share Information with State and Local Government Agencies

2.9.6 Share Information with Public Traveler Information Providers

2.9.7 Share Information with Private Third Party Providers

3. Functional Requirements

3.1 Tutorial

3.2 Scope of the Requirements

3.3 Needs to Requirements Traceability Matrix (NRTM)

3.3.1 Notation

3.3.2 Needs to Requirements Traceability Matrix (NRTM) Table

3.4 Architectural Requirements

3.4.1 Connection Management

3.4.2 Support Request-Response

3.4.3 Support Subscription-Publication

3.4.4 Support Error Handling Report

3.5 Functional Requirements

3.5.1 Provide Information on Organizations and Centers

3.5.2 Events Information Sharing

3.5.3 Share Roadway Network Data

3.5.4 Provide Device Inventory and Status

3.5.5 Transit Related Requirements

3.5.6 Weather Alert Requirements

3.6 Performance Requirements

3.6.1 Message Transmission Time – Publication Updates

3.6.2 Response Time

4. Design Reference

4.1 Design Scope

4.2 Requirements Traceability Matrix (RTM)

4.2.1 Requirement ID and Requirement

4.2.2 Data Concept Type (DC Type)

4.2.3 DC Instance Name, DC ID, and DC Class Name

4.2.4 Comment

4.2.5 RTM Table Selection

List of Tables

Table 1. Terms and Definitions.

Table 2. Abbreviations.

Table 3. Minimum Service Quality Levels.

Table 4. Mapping to National ITS Architecture Entities.

Table 5. Private Data Collection Organization to Transportation Agency Interface.

Table 6. Transportation Agency to Peer Transportation Agency.

Table 7. Transportation Agency to Public Traveler Information Provider.

Table 8. Transportation Agency to Private Third Party Provider.

Table 9. Public Traveler Information Provider to Private Third Party Provider.

Table 10. Transportation Agency to Travelers.

Table 11. Public Traveler Information Provider to Travelers.

Table 12. Transportation Agency to Other Public Agency.

Table 13. Other Public Agency to Transportation Agency.

Table 14. Actor Definitions and Associated Stakeholders.

Table 15. Operational Scenario – Using Real Time Information.

Table 16. Operational Scenario – Using Real Time Weather Information.

Table 17. Operational Scenario – Sharing Information with Traveling Public.

Table 18. Operational Scenario – Sharing Information with State and Local Government Agencies.

Table 19. Operational Scenario – Sharing Information with Public Traveler Information Providers.

Table 20. Sharing Information with Private Third Party Providers.

Table 21. Conformance Symbols.

Table 22. Predicate Notations.

Table 23. Predicates.

List of Figures

Figure 1. Diagram. RTSMIP Context Diagram

U.S. Department of Transportation
Federal Highway Administration
Office of Operations
1200 New Jersey Avenue, SE
Washington, DC 20590
www.ops.fhwa.dot.gov

Publication #: FHWA-HOP-13-047

August 2013