Office of Operations
21st Century Operations Using 21st Century Technologies
Publications

Model Systems Engineering Documents for Dynamic Message Sign (DMS) Systems

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

United States Department of Transportation logo.

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

FHWA-HOP-18-080

September 2018

Table of Contents

[ Notice and Quality Assurance Statement ] [ Technical Report Documentation Page ] [ Glossary ]

Executive Summary
No Value Part of an ITS Implementation Process
No Value What the User Will Do
No Value Procurement Support
Chapter 1. Concept of Use
No Value Purpose
No Value Process
No Value Concept of Operations
No Value Requirements Document
No Value Verification Plan
No Value Validation Plan
No Value Procurement
No Value Assembling Your Documents
No Value Summary
Chapter 2. Concept of Operations Guidance
No Value Scope (Chapter 1 of the ConOps Document)
No Value No Value Document Purpose and Scope
No Value No Value Project Purpose and Scope
No Value No Value Procurement
No Value Referenced Documents (Chapter 2 of the ConOps Document)
No Value User-Oriented Operational Description (Chapter 3 of the ConOps Document)
No Value No Value General Actors
No Value No Value Use Cases
No Value Operational Needs (Chapter 4 of the ConOps Document)
No Value Envisioned DMS System Overview (Chapter 5 of the ConOps Document)
No Value DMS System Operational Environment (Chapter 6 of the ConOps Document)
No Value No Value Operational Environment
No Value No Value Physical Environment
No Value DMS System Support Environment (Chapter 7 of the ConOps Document)
No Value Proposed Operational Scenarios Using a DMS System (Chapter 8 of the ConOps Document)
Chapter 3. System Requirements Guidance
No Value Scope of System or Sub-system (Chapter 1 of the Requirements Document)
No Value References (Chapter 2 of the Requirements Document)
No Value Requirements (Chapter 3 of the Requirements Document)
No Value Verification Methods (Chapter 4 of the Requirements Document)
No Value Supporting Documentation (Chapter 5 of the Requirements Document)
No Value Traceability Matrix (Chapter 6 of the Requirements Document)
No Value Glossary (Chapter 7 of the Requirements Document)
Chapter 4. Verification Plan Guidance
No Value Purpose of the Document (Chapter 1 of the Verification Plan Document)
No Value Scope of Project (Chapter 2 of the Verification Plan Document)
No Value Referenced Documents (Chapter 3 of the Verification Plan Document)
No Value Conducting Verification (Chapter 4 of the Verification Plan Document)
No Value Verification Identification (Chapter 5 of the Verification Plan Document)
Chapter 5. Validation Plan Guidance
No Value Purpose of the Document (Chapter 1 of the Validation Plan Document)
No Value Scope of Project (Chapter 2 of the Validation Plan Document)
No Value Referenced Documents (Chapter 3 of the Validation Plan Document)
No Value Conducting Validation (Chapter 4 of the Validation Plan Document)
No Value Validation Identification (Chapter 5 of the Validation Plan Document)
Chapter 6. Purchasing a System Using Systems Engineering Documents
No Value Traditional Approaches are Risky for Technology Projects
No Value Reducing Risk Using Requirements
No Value Reducing Risk Further by Using Requirements for Selection
No Value Sole-Source Acquisitions
No Value Services and Infrastructure
Appendix A: Concept of Operations Table of Sample Statements
Appendix B: System Requirements Table of Sample Statements
Appendix C: Suggested Requirements Verification Methods
Appendix D: Verification Plan Sample Cases
Appendix E: Validation Plan Sample Cases
Appendix F: Standardized Communications Protocol Stack Interface Diagrams
Appendix G: Acknowledgements

LIST OF FIGURES

Figure 1Reference Architecture for a DMS System with the scope of the DMS Model SE Documents
Figure 2Concept of Use Process for SE Model Documents
Figure 3High-Level Representative DMS System Project Architecture Diagram
Figure 4Communications Protocol Standards Example for the NTCIP-SMTP Triple of DMS Management System ⇒ roadway dynamic signage data ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 5Consumer Reports acquisition approach.
Figure 6Low-bid process supported by requirements.
Figure 7RFP-based technical selection acquisition process.
Figure 8Complex project with both system services and infrastructure, and both pilot and full implementation phases.
Figure 9Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Management System ⇒ roadway dynamic signage data ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 10Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Field Equipment ⇒ roadway dynamic signage status ⇒ DMS Management System based on the DMS System Project Architecture Diagram
Figure 11Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Field Equipment ⇒ field equipment status ⇒ DMS Management System based on the DMS System Project Architecture Diagram
Figure 12Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Management System ⇒ field equipment configuration settings ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 13Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Management System ⇒ field equipment commands ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 14Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Management System ⇒ field equipment software install/upgrade ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 15Communications Protocol Standards for the NTCIP-SMTP Triple of Field Support Computer ⇒ roadway dynamic signage data ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 16Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Field Equipment ⇒ roadway dynamic signage status ⇒ Field Support Computer based on the DMS System Project Architecture Diagram
Figure 17Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Field Equipment ⇒ field equipment status ⇒ Field Support Computer based on the DMS System Project Architecture Diagram
Figure 18Communications Protocol Standards for the NTCIP-SMTP Triple of Field Support Computer ⇒ field equipment configuration settings ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 19Communications Protocol Standards for the NTCIP-SMTP Triple of Field Support Computer ⇒ field equipment commands ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 20Communications Protocol Standards for the NTCIP-SMTP Triple of Field Support Computer ⇒ field equipment software install/upgrade ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 21Communications Protocol Standards for the NTCIP-SNMP Triple of DMS Management System ⇒ roadway dynamic signage data ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 22Communications Protocol Standards for the NTCIP-SNMP Triple of DMS Field Equipment ⇒ roadway dynamic signage status ⇒ DMS Management System based on the DMS System Project Architecture Diagram
Figure 23Communications Protocol Standards for the NTCIP-SMTP Triple of DMS Field Equipment ⇒ field equipment status ⇒ DMS Management System based on the DMS System Project Architecture Diagram
Figure 24Communications Protocol Standards for the NTCIP-SNMP Triple of DMS Management System ⇒ field equipment commands ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 25Communications Protocol Standards for the NTCIP-SNMP Triple of DMS Management System ⇒ field equipment configuration settings ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 26Communications Protocol Standards for the NTCIP-SNMP Triple of DMS Management System ⇒ field equipment software install/upgrade ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 27Communications Protocol Standards for the NTCIP-SNMP Triple of Field Support Computer ⇒ roadway dynamic signage data ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 28Communications Protocol Standards for the NTCIP-SNMP Triple of DMS Field Equipment ⇒ roadway dynamic signage status ⇒ Field Support Computer based on the DMS System Project Architecture Diagram
Figure 29Communications Protocol Standards for the NTCIP-SNMP Triple of DMS Field Equipment ⇒ field equipment status ⇒ Field Support Computer based on the DMS System Project Architecture Diagram
Figure 30Communications Protocol Standards for the NTCIP-SNMP Triple of Field Support Computer ⇒ field equipment commands ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 31Communications Protocol Standards for the NTCIP-SNMP Triple of Field Support Computer ⇒ field equipment configuration settings ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 32Communications Protocol Standards for the NTCIP-SNMP Triple of Field Support Computer ⇒ field equipment software install/upgrade ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Figure 33Communications Protocol Standards for the RSE Field to Field Triple of DMS Field Equipment ⇒ roadway equipment coordination ⇒ External Devices based on the DMS System Project Architecture Diagram
Figure 34Communications Protocol Standards for the RSE Field to Field Triple of External Devices ⇒ roadway equipment coordination ⇒ DMS Field Equipment based on the DMS System Project Architecture Diagram
Office of Operations