Technical Report Documentation Page

1. Report No. FHWA-JPO-08-042 EDL Number 14422	2. Government Accession No.	3. Recipient's Catalog No.
4. Title and Subtitle System Requirement Specification for the I-394 Integrated Corridor Management System (ICMS) in Minneapolis, Minnesota	5. Report Date March 31, 2008
6. Performing Organization Code
7. Author(s) Minneapolis Pioneer Site Team	8. Performing Organization Report No.
9. Performing Organization Name and Address Minneapolis Pioneer Site Team	10. Work Unit No. (TRAIS)
11. Contract or Grant No.
12. Sponsoring Agency Name and Address U.S. Department of Transportation Research and Innovative Technology Administration ITS Joint Program Office 1200 New Jersey Avenue, SE Washington , DC 20590	13. Type of Report and Period Covered
14. Sponsoring Agency Code
15. Supplementary Notes RITA Contact: Brian Cronin FHWA Contact: Dale Thompson FTA Contact: Steve Mortensen
16. Abstract This System Requirement Specification (SRS) defines the requirements for the I-394 Corridor Integrated Corridor Management System (ICMS). These requirements describe ‘what’ the ICMS will do to fulfill its role as part of the overall I-394 Integrated Corridor Management approach. In some cases, the actions of the ICMS will require actions of other systems that are currently performed by the existing systems. In these circumstances, detailed functional requirements are not defined because the systems already exist and need not be built by this project. However, high level ‘External Requirements’ are identified describing these actions that the ICMS needs in order to function properly. This integration of systems and agencies will be accomplished by the design, development and implementation of the ICMS. The purpose of this system is to support the I-394 stakeholders at executing the Incident Corridor Management (ICM) strategies they have identified and prioritized for this corridor. Section 1 of this document provides an introduction. Section 1 provides a general system description. Section 3 presents the detailed requirements for the System of Systems for the I-394 ICMS. Section 4 presents the detailed system requirements for the individual systems of I-394 ICMS. Section 5 defines the Hardware Requirements, Section 6 describes the Interface Requirements, and Section 7 defines the Documentation and Training Requirements.
17. Key Words ICM, Integrated Corridor Management, Requirements, I-394, Minneapolis, Twin Cities Metropolitan Area, Hennepin County, Freeway, Arterial, Transit, Intelligent Transportation Systems, ITS, HOV, Parking Facilities, HOT lanes, Toll	18. Distribution Statement
19. Security Classification (of this report) Unclassified	20. Security Classification (of this page) Unclassified	21. No of Pages 177	22. Price

1. Report No.

FHWA-JPO-08-042
EDL Number 14422

2. Government Accession No.

3. Recipient's Catalog No.

4. Title and Subtitle

System Requirement Specification for the I-394 Integrated Corridor Management System (ICMS) in Minneapolis, Minnesota

5. Report Date

March 31, 2008

6. Performing Organization Code

7. Author(s)

Minneapolis Pioneer Site Team

8. Performing Organization Report No.

9. Performing Organization Name and Address

Minneapolis Pioneer Site Team

10. Work Unit No. (TRAIS)

11. Contract or Grant No.

12. Sponsoring Agency Name and Address

U.S. Department of Transportation
Research and Innovative Technology Administration
ITS Joint Program Office
1200 New Jersey Avenue, SE
Washington , DC 20590

13. Type of Report and Period Covered

14. Sponsoring Agency Code

15. Supplementary Notes

RITA Contact: Brian Cronin
FHWA Contact: Dale Thompson
FTA Contact: Steve Mortensen

16. Abstract

This System Requirement Specification (SRS) defines the requirements for the I-394 Corridor Integrated Corridor Management System (ICMS). These requirements describe ‘what’ the ICMS will do to fulfill its role as part of the overall I-394 Integrated Corridor Management approach. In some cases, the actions of the ICMS will require actions of other systems that are currently performed by the existing systems. In these circumstances, detailed functional requirements are not defined because the systems already exist and need not be built by this project. However, high level ‘External Requirements’ are identified describing these actions that the ICMS needs in order to function properly.

This integration of systems and agencies will be accomplished by the design, development and implementation of the ICMS. The purpose of this system is to support the I-394 stakeholders at executing the Incident Corridor Management (ICM) strategies they have identified and prioritized for this corridor. Section 1 of this document provides an introduction. Section 1 provides a general system description. Section 3 presents the detailed requirements for the System of Systems for the I-394 ICMS. Section 4 presents the detailed system requirements for the individual systems of I-394 ICMS. Section 5 defines the Hardware Requirements, Section 6 describes the Interface Requirements, and Section 7 defines the Documentation and Training Requirements.

17. Key Words

ICM, Integrated Corridor Management, Requirements, I-394, Minneapolis, Twin Cities Metropolitan Area, Hennepin County, Freeway, Arterial, Transit, Intelligent Transportation Systems, ITS, HOV, Parking Facilities, HOT lanes, Toll

18. Distribution Statement

19. Security Classification (of this report)

Unclassified

20. Security Classification (of this page)

Unclassified

21. No of Pages

177

22. Price

Form DOT F 1700.7 (8-72)

Reproduction of completed page authorized

Table of Contents | Next