ITS Architecture Development

Transcription

1 Personal Information Access Transit Management Traffic Management Communications Fixed Point-to-Fixed Point Communica Vehicle Roadway ITS Architecture Development Systems Engineering For ITS Kickoff Workshop Workshop 3: Regional ITS Architecture 101 These materials developed under the ITS Joint Program Office s National ITS Architecture Program

2 Session Outcomes 1. Define regional ITS architecture 2. List the components typically found in a regional ITS architecture Interfaces Scope Functions Stakeholders Services Inventory Ops Concept 2

3 ITS Use of information and communications technologies to meet transportation needs 3

4 ITS Architecture Framework for Developing Integrated Transportation Systems Identifies: Organizations Systems operated Functions performed Communications Information exchanged 4

5 ITS Architectures are a Framework for Integration I-93 Closed at Decatur Blvd. Traffic Traffic Information Traveler Info Providers Request for Traffic Information Transit Emergency Service Providers 5

6 Regional ITS Architecture A framework for ensuring institutional agreement and technical integration for the implementation of ITS projects in a particular region 6

7 Regional ITS Architecture Benefits Orderly and efficient deployments over time Better communications Between people Between systems Reduce design costs and development time Lower risk Help comply with ITS Architecture & Standards Rule/Policy 7

8 Regional ITS Architecture Components ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan 8

9 Architecture Region ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Scope of architecture: Geographic area Time horizon Breadth of ITS services 9

10 Architecture Geographic Area Options MPO area Statewide & multi-state ITS corridor ITS project funding boundary Service area Air quality non-attainment area 10

11 Architecture Time Horizon How far into the future to consider Short Medium Long Corresponds to time horizon of: TIP LRTP

12 Architecture Breadth of Services Include statewide services? 511 traveler information Commercial vehicle operations Include only publicly funded services? Consider other architectures Traffic Payment Transit Centers 12

13 Region for PennDOT District 2-0 Architecture Geographic Area Time horizon = 20 years Service scope = Major rural ITS issues 13

14 Stakeholders ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Someone who deploys, owns, operates, maintains, or is impacted by, an ITS system 14

15 Stakeholders of North Dakota Statewide Architecture 15

16 Inventory of ITS Elements ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan A list of ITS elements and the elements that interface with them And an element is: An ITS system or piece of a system An architecture is built around an inventory of existing and future ITS systems Know what you have today Plan for future systems 16

17 Inventory of ITS Elements (cont.) Group types of elements Not a detailed listing of each device ITS Systems ITS Inventory Elements 17

18 Mapping Elements to Subsystems and Terminators Element: State DOT Freeway Operations Center Subsystems Traffic Management Center Emergency Management Center 18

19 ARC-IT is a Framework and a Template 19

20 Importance of Mapping to Subsystems and Terminators Requirements Interfaces Standards Traffic Management Center Emergency Management Center 20

21 Partial Inventory from Memphis Regional ITS Architecture Stakeholder Name Description Entity Status City of West Memphis DARTS City of West Memphis TOC West Memphis MPO Data Archive DARTS Data Archive DARTS Demand Response Vehicles DARTS Dispatch Center Traffic operations center for the City of West Memphis. Responsible for the operation of the traffic signal system and any other ITS infrastructure deployed by the City. Archive of regional transportation data used in planning. Delta Area Rural Transit System transit ridership statistics used by the National Transit Database, FTA, and MDOT. Delta Area Rural Transit System demand response vehicle fleet. Delta Area Rural Transit System dispatch center responsible for the tracking, scheduling and dispatching of DARTS demand response services. Traffic Management Archived Data System Archived Data System Transit Vehicle Transit Management Emergency Management Planned Planned Planned Existing Existing 21

22 ITS Services ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan ITS capabilities you use to meet operational goals and objectives Examples: Traffic Incident Management System Electronic Toll Collection Smart Roadside and Virtual WIM 22

23 Service Packages ITS services in the ARC-IT Traffic Management Public Transportation Maintenance and Construction Commercial Vehicle Operations Public Safety Parking Management Vehicle Safety Traveler Information Data Management Support Sustainable Travel Weather 23

24 Service Packages and a Regional ITS Architecture Service Packages provide a menu of ITS services Select Service Packages of interest Map to your inventory and tailor Traffic Management Public Safety Data Management Commercial Vehicle Operations Parking Management Maintenance and Construction Vehicle Safety Public Transportation Traveler Information Support Sustainable Travel Weather Transit Vehicle Tracking Transit Fixed-Route Operations Dynamic Transit Operations Transit Fare Collection Management Transit Security 24

25 Service Packages from the Cincinnati (OKI) Regional Arch PT02 Transit Fixed Route Operations - CTC Service Package Service Package Instance 25

26 Service Package Customization ARC-IT Service Package definition is a template to be revised as needed to describe the service in the region 26

27 Operational Concept ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Identifies the roles and responsibilities of stakeholders in the operation, implementation and maintenance of the ITS systems 27

28 Roles and Responsibilities Roles ITS functions of a stakeholder Responsibilities Duties or obligations of a stakeholder in delivering one or more ITS services in a region 28

29 Incident Management (Simplified) County Emergency Services State DOT ACCIDENT AHEAD MERGE LEFT Provide incident information to State DOT TMC Dispatch emergency vehicles to incident Monitor roadways and provide incident information to Emergency Services Share CCTV control with Emergency Services 29

30 Operational Concept of DC ITS Architecture Coordinate maintenance activities with DPW and with maintenance organizations in adjoining jurisdictions. Provide automated maintenance status information on maintenance vehicles to the District maintenance dispatch and equipment repair facility. Collect environmental information from District field equipment, and from public and private weather service providers. 30

31 Functional Requirements ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan High-level descriptions of what ITS elements will do in the region NOT detailed design requirements Typically written as shall statements 31

32 Using Functional Requirements from ARC-IT Functional requirements are defined for every functional object in ARC-IT Select relevant requirements for your region Traffic Management Center TMC Environmental Monitoring TMC Evacuation Support TMC Signal Control 1. The center shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures. 2. The center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. 32

33 Requirements from ND Statewide Architecture NDDOT Maintenance Vehicles Requirement The maintenance and construction vehicle shall track its current location. The maintenance and construction vehicle shall send the time stamped vehicle location to the controlling center. 33

34 Functional Requirements are the Starting Point Maine DMS Architecture Requirements Element Functional Object ID Requirement Maine DOT Communications Center TMC Traffic Information Dissemination Maine DMS Project Requirements Parent requirement: The center shall remotely control dynamic message signs Add detailed child requirements to: Activate and display a message Prioritize messages Define a message (pick list, spell check) Blank the sign Schedule messages for display 1 The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers. 34

35 Interfaces ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces // Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Identify Interconnects Which systems will share info? Define Information Flows What information will they share? SHP State Highway Patrol Vehicles Metro Police Department Metro Police Emergency System Local Traffic Department Local Traffic Signal Control System State DOT Freeway Management Center SHP State Highway Patrol Emergency System Suburban Traffic Depart. Suburban Traffic Signal Control System Metro Fire Department Metro Fire Emergency System Metro Traffic Department Metro Signal Control System State DOT State DOT Web Site 35

36 Interconnects are made up of Information Flows ITS Element A Interconnect ITS Element B ITS Element A Information Flow 1 Information Flow 2 Information Flow N ITS Element B Triple: Source, Interface Flow, Destination 36

37 Information Flows Between Elements Event Promoter event plans TMC incident information resource request... incident information resource deployment status Public Safety Dispatch 37

38 Interface Diagram from NY Region 10 Regional ITS Architecture 38

39 ITS Standards ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Over 100 ITS Standards Cover Transit, Traffic, CVO, Toll, Traveler Information, 39

40 Identifying ITS Standards By Interface From ARC-IT 40

41 Identifying ITS Standards From ARC-IT By Interface Triple: Source, Interface Flow, Destination 41

42 Standards from DRCOG Regional ITS Architecture SAE Advanced Traveler Information Systems (ATIS) Bandwidth Limited Standards Group Source Element Destination Element Flow Name COTrip Traveler Information CDOT Kiosks broadcast traveler information RTD Traveler Information RTD Fare and Information Kiosks broadcast traveler information Commerical ISP Personal Computing Devices traveler alerts Commerical ISP Vehicle traveler alerts COTrip Traveler Information CDOT ITS Data Warehouse traveler archive data COTrip Traveler Information CDOT Kiosks broadcast traveler information COTrip Traveler Information Personal Computing Devices traveler alerts COTrip Traveler Information Vehicle traveler alerts DRCOG Traveler Information Personal Computing Devices traveler alerts DRCOG Traveler Information Vehicle traveler alerts Event Promoter Commerical ISP event information Event Promoter COTrip Traveler Information event information 42

43 Project Sequencing ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Order in which ITS projects should be implemented Impacted by: Technical issues Institutional issues 43

44 Process for Sequencing Projects 1. Identify and define projects 2. Evaluate project dependencies 3. Sequence projects over time Project A Project B Project A Project B Project C Near Term Medium Term Long Term Project C 44

45 ITS Projects Can be deployment of software and/or hardware that provides an ITS service or services (Stand-Alone) Can be traditional construction or enhancement project that contains ITS elements (Embedded) 45

46 Incident Management Maintenance Dispatch Info Provider 911 Other TMC TMC Dispatch Other 911 Center TRAFFIC MANAGEMENT PROJECT EMERGENCY MANAGEMENT PROJECT 46

47 Project Definition in MN Statewide ITS Architecture 47

48 Project Sequencing Excerpt from MN Statewide ITS Architecture 48

49 Agreements ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Document institutional integration in region May be required for interjurisdictional interfaces Define: Integration plans Maintenance & operations plans Funding responsibilities 49

50 Types of Agreements Handshake agreement Memorandum of Understanding (MOU) Interagency agreement Intergovernmental agreement Operational agreement Funding agreement Master agreement 50

51 Agreements from Las Cruces Regional ITS Architecture Potential Parties to Agreement NMDOT, Mesilla Valley Regional Dispatch Authority, Elephant Butte Irrigation District, City of Las Cruces, Dona Ana County, NMDPS NMDPS, Regional Public Safety Agencies, NMDOT, New Mexico State University NMDPS, Regional Public Safety Agencies, NMDOT Purpose Provide early warning information Coordinating emergency plans for disasters Coordinating emergency plans for disasters, evacuations and reentry 51

52 Regional Architecture Maintenance ITS Architecture 1. Region description 2. Stakeholder identification 3. ITS elements 4. ITS services 5. Operational concept 6. Functional requirements 7. Interfaces / Information flows 8. Standards identification 9. Project sequencing 10. Agreements 11. Maintenance plan Factors that cause changes to an architecture: ITS project deployments Changes in project plans Shifts in ITS goals and objectives and the services to meet them Additional stakeholders Errata & enhancements 52

53 Maintenance Plan Components WHO will be responsible? WHEN will updates occur? WHAT will be maintained? HOW will the changes be made? 53

54 Relationship between Architecture Components Region Description Stakeholder Identification ITS Elements Functional Requirements Operational Concept ITS Services Interfaces/ Information Flows Agreements Project Sequencing Standards Identification Maintenance Plan 54

55 Session Outcomes 1. Define regional ITS architecture 2. List the components typically found in a regional ITS architecture 55