View
9
Download
0
Category
Preview:
Citation preview
Traffic Management
Transit Management
Fixed Point-to-Fixed Point Communica
Roadway
Personal Information
Access
Communications
Vehicle
ITS ArchitectureWorkshop
Systems Engineering For ITSWorkshop
Quick-Starting YourRegional ITS Architecture Update
4: Starting at the Finish Line – Architecture Use (& Maintenance)
ITS ArchitectureWorkshop
The Ultimate Measure of Success- Productive Architecture Use
2. National ITS Architecture
3. Regional ITS Architecture Components
3E. Architecture Assessment
4. Architecture Use
5. Plan
4-2
ITS ArchitectureWorkshop Session Outcomes
Identify how the regional architecture can support long range planning activities Describe how an architecture can be used to
program/budget ITS projects Describe the relationship between
architecture and systems engineering
4-3
ITS ArchitectureWorkshop
Architecture Use in Project Life Cycle
Planning
Programming/Budgeting
Operations &Maintenance
IdentifiedProject
Implementation
FundedProject
Monitoring &Evaluation
Implemented Project
RegionalArchitecture Use=
4-4
ITS ArchitectureWorkshop
Reasons for Architecture Use in Transportation Planning
Architecture represents a consensus vision of Operations and Planning stakeholders for deployment of ITS systems Addresses both short range projects and
long range strategies
4-5
ITS ArchitectureWorkshop Connecting Stakeholder Visions
Regional architecture development and update can expand the interaction of planning and operations
0 5 10 15 20
Long Range Plan
Projects
Regional ITS Architecture
Planners
Operations
4-6
ITS ArchitectureWorkshop Transportation Planning Process
Evaluation & Prioritization of Strategies
Development of Long-Range Transportation Plan
Development of Transportation Improvement Programs (TIP/STIP)
Project Development
System Operations
Monitor System Performance
Alternate Improvement StrategiesOperations Capital
FeedbackRegional Goals and Objectives
4-7
ITS ArchitectureWorkshop
Need
Scope Stakeholders
Champions
Inventory
Needs and Services
Operational Concept
Functional Requirements
Project Sequencing
List of Agency Agreements
ITS Standards
Interconnects Information Flows
STEP #1: GET STARTED
STEP #2: GATHER DATA
STEP #3: DEFINE INTERFACES
STEP #4: IMPLEMENTATION
Architecture Development is a Planning Process
4-8
ITS ArchitectureWorkshop
Regional Architecture and Transportation Planning
Evaluation & Prioritization of Strategies
Development of Long-Range Transportation Plan (LRTP)
Development of Transportation Improvement Programs (TIP/STIP)
Project Development
System Operations
Monitor System Performance
Alternate Improvement StrategiesOperations Capital
Feedback
Regional ITSArchitecture
Regional Goals and Objectives
4-9
ITS ArchitectureWorkshop
Transportation Goals and Objectives
Goals • e.g., Improve transportation system reliability
Objectives• e.g., By 2020, decrease average annual
traveler delay associated with road closures, major incidents, and weather-related conditions on interstate highways by 20 percent from 2005 levels.
Regional Goals and Objectives
4-10
ITS ArchitectureWorkshop
Goals and Objectives and the Architecture
Regional architecture should be based on operations-related goals and objectives ▬ Ensure architecture and long range plan are guided
by the same operations objectives▬ Leverage architecture traceability▬ Use Architecture to identify associated performance
measures and define a framework for performance monitoring
Regional ITSArchitecture
Regional Goals and Objectives
4-11
ITS ArchitectureWorkshop Operational Strategies
Asset Management Access Management Traffic Signal Timing Congestion Mitigation Corridor Traffic Management Emergency Transportation
Operations Freeway Management
Freight Operations and Technology
Real Time Traveler Information Road Weather Management Tolling and Pricing Program Travel Demand Management Traffic Incident Management Work Zone Management
Alternate Improvement StrategiesCapital
Regional Goals and Objectives
Operations
4-12
ITS ArchitectureWorkshop
Objectives and Strategies-Example
Objective▬ Improve traffic flows by 50%
in peak traffic periods. Operations Strategies
▬ Continue maintaining and updating traffic signal coordination in response to…changes in traffic patterns
▬ Use changeable message signs to reroute traffic in high-volume corridors
Reference: Champaign County Long Range Transportation Plan
Alternate Improvement StrategiesOperations Capital
Regional Goals and Objectives
4-13
ITS ArchitectureWorkshop
Operational Strategies and the Architecture
Architecture services can point to operational strategies
Facilitate use by mapping operational strategies from the LRTP to architecture services▬ Look for gaps and inconsistencies
Regional ITSArchitecture
ITS Services(Service Packages)
Alternate Improvement StrategiesOperations Capital
4-14
ITS ArchitectureWorkshop Strategies and Services- Example
Alternate Improvement StrategiesOperations Capital
Objective: Improve traffic flows by 50% in peak traffic periods.Strategies Service Packagesa. Continue maintaining and updating traffic signal coordination in response to changes in traffic patterns.
ATMS03: Traffic Signal ControlATMS07: Regional Traffic Management (?)
b. Educate residents about alternative forms of transportation and alternative routes
Education initiatives not covered by ITS, but traveler information service packages could augment that outreach
c. Use changeable message signs to reroute traffic in high-volume corridors.
ATMS06: Traffic InformationDissemination
4-15
ITS ArchitectureWorkshop
Strategy Evaluation and Prioritization
Evaluation and prioritization of strategies are key planning activities
PotentialStrategies
LRTP
Evaluation & Prioritization of Strategies
SelectedStrategies
Alternate Improvement StrategiesOperations Capital
Regional Goals and Objectives
4-16
ITS ArchitectureWorkshop
Strategy Evaluation and Prioritization
Project Sequencing output contains info useful to evaluation/prioritization▬ Stakeholders▬ Benefits▬ Mapping to service packages
Define mid-long term projects in language suitable for the plan (e.g. as “strategies”)
Regional ITSArchitecture
ProjectSequencing
Evaluation & Prioritization of Strategies
4-17
ITS ArchitectureWorkshop
LRTP and Architecture Comparison
LRTP Goals, objectives,
strategies, and projects to achieve it
Covers at least the next 20 years
Leads to an intermodal system
Fiscally constrained Must be updated every
4-5 years
Architecture ITS Services and
projects
Long term timeframe
Covers multiple modes
Not fiscally constrained Updated per
maintenance plan
Development of Long-Range Transportation Plan (LRTP)
4-18
ITS ArchitectureWorkshop Architecture Use in LRTP
Architecture output could be used directly in LRTP
Development of Long-Range Transportation Plan (LRTP)
Executive summary material/graphics from the architecture could be appropriate for the LRTP
The Regional Intelligent Transportation Systems (ITS) Architecture for the Kansas City metropolitan region is a specific regional framework for documenting and ensuring institutional agreement and technical integration for the implementation of ITS projects in the region. The documentation of the regional integration among transportation systems enables comprehensive planning and deployment activities while also supporting the sharing of information and coordination of activities that enables efficient and effective operations. Kansas City Transportation Outlook 2040
4-19
ITS ArchitectureWorkshop Monitor System Performance
4-20
ITS ArchitectureWorkshop
Architecture Use in Performance Monitoring
Architecture defines collection of data from operational systems to support performance monitoring
Consider regional examples of Archived Data Management Subsystem (ADMS) to automate collection of data from:▬ Traffic▬ Transit▬ Emergency Services▬ Traveler Information
Archived Data Management
Regional Data Warehouse
Monitor System Performance
4-21
ITS ArchitectureWorkshop
Architecture Use in Planning for Operations
Applying the Regional ITS Architecture to Support Planning for Operations – A Primer
Timing of Updates: Architecture updated
prior to LRTP update Architecture updated
after LRTP update Both updates at same
time
4-22
ITS ArchitectureWorkshop
Usefulness of the Regional Architecture
In supporting long range plan development▬ Current regional
architecture may have limited usefulness
▬ Revise architecture outputs during update cycles to increase usefulness
Long Range Plan
Strategies,Evaluations,Documentation
Original outputs
Updatedoutputs
Regional Architecture
4-23
ITS ArchitectureWorkshop
Regional Architecture -Making it Useful
Explicitly connect architecture needs and services to objectives and strategies Describe mid-long term projects in language
suitable for the plan (e.g. as “strategies”) Create executive summary material/
graphics as part of architecture that would be appropriate for the LRTP Formally approve architecture
4-24
ITS ArchitectureWorkshop ITS Strategic Plan
ITSStrategic
Plan
Short Term Projects
Mid Term Projects
Long Term Projects
Regional Architecture
EmergencyManagement
Center
TrafficManagement
Center
TMCRoadwayDevices
Other TMCtrafficinformationcoordination
incident information
traffic flow
incident information
TrafficInformation
ServiceProvider
roadway information system data
EmergencyVehicles
incidentstatus
loggedspecial vehicle
route
traffic images
video surveillance control
OtherEMC
incident report
EventPromoter
event plans
incidentresponse
coordination
incidentcommandinformation
incidentinformation
Maintenance &Construction Management
incidentinformationmaint.
and constr.
resourcerequest
maint. and constr.resource request
Maint. and Const. Center
Personnel
maint. and constr.operations informationpresentation
maint. and constr.center personnel inputs
OtherMCM
maint. and constr.resource coordination
road networkconditions
Regions may also develop ITS specific plans (e.g. ITS Strategic Plan) to support planning
Regional Architecture
EmergencyManagement
Center
TrafficManagement
Center
TMCRoadwayDevices
Other TMCtrafficinformationcoordination
incident information
traffic flow
incident information
TrafficInformation
ServiceProvider
roadway information system data
EmergencyVehicles
incidentstatus
loggedspecial vehicle
route
traffic images
video surveillance control
OtherEMC
incident report
EventPromoter
event plans
incidentresponse
coordination
incidentcommandinformation
incidentinformation
Maintenance &Construction Management
incidentinformationmaint.
and constr.
resourcerequest
maint. and constr.resource request
Maint. and Const. Center
Personnel
maint. and constr.operations informationpresentation
maint. and constr.center personnel inputs
OtherMCM
maint. and constr.resource coordination
road networkconditions
4-25
ITS ArchitectureWorkshop ITS Strategic Plan (cont.)
Contains elements that go beyond the regional architecture requirements▬ Vision, Goals, and Objectives▬ Strategies for ITS deployment▬ Funding considerations▬ Detailed project definitions▬ Gaps in planned projects▬ Benefits analysis▬ Communications Plan
4-26
ITS ArchitectureWorkshop ITS Strategic Plan (cont.)
Connects the regional architecture with the strategies and projects in the long range plan/transportation improvement program
Regi
onal
Arch
itect
ure LRTP/TIP
ITS Strategic PlanITS Strategic Plan
4-27
ITS ArchitectureWorkshop
Architecture Use in Project Life Cycle
Planning
Programming/Budgeting
Operations &Maintenance
IdentifiedProject
Implementation
FundedProject
Monitoring &Evaluation
Implemented Project
RegionalArchitecture Use=
4-28
ITS ArchitectureWorkshop
RegionalArchitecture
Architecture Use in Programming/Budgeting
Planning Agency
Project
Project
Project
Project
Project w/ITS
Project w/ITS 1. Project
2. Project
3. ITS Project
ITS Project
ITS Project
4. Project w/ITS
RegionalArchitecture
Development of Transportation Improvement Programs (TIP/STIP)
Project Development
Development of Long-Range Transportation Plan
4-29
ITS ArchitectureWorkshop
Benefits of Architecture Use in Programming/Budgeting
Link objectives and needs of the region with ITS deployed in the field Take a regional view Begin coordination of projects of various
organizations by defining from the same reference point
4-30
ITS ArchitectureWorkshop
Architecture Provides a Regional Context for Planned Projects
Regional ArchitectureTransportation Improvement Program
CityTMC
Regional511
Bus RapidTransit
OtherSystems
OtherSystems
Agency Number Project Funding
City C11-321 City TMC $400K
CTrans T12-023 Bus Rapid Transit Ph1
$1.4M
DOT D11-843 Regional511 Ph2
$600K
4-31
ITS ArchitectureWorkshop Project Sponsors
Many agencies identify and plan projects simultaneously: Cities Counties Transit Agencies Toll Authorities State DOTs MPOs
Project Sponsors
4-32
ITS ArchitectureWorkshop Programming/Budgeting Process
Project Sponsors▬ Identify Projects▬ Scope Projects▬ Submit Project Applications
MPO/State DOTs▬ Prioritize Projects▬ Create TIP, STIP, Other
Programming documents
Project Sponsors
123
4
4-33
ITS ArchitectureWorkshop Use to Identify Projects
ITS Project
Integration Opportunities
EmergencyManagement
Center
TrafficManagement
Center
TMCRoadwayDevices
Other TMCtrafficinformationcoordination
incident information
traffic flow
incident information
TrafficInformation
ServiceProvider
roadway information system data
EmergencyVehicles
incidentstatus
loggedspecial vehicle
route
traffic images
video surveillance control
OtherEMC
incident report
EventPromoter
event plans
incidentresponse
coordination
incidentcommandinformation
incidentinformation
Maintenance &Construction Management
incidentinformation
maint. and
constr.resourcerequest
maint. and constr.resource request
Maint. and Const. Center
Personnel
maint. and constr.operations information
presentation
maint. and constr.center personnel inputs
OtherMCM
maint. and constr.resource coordination
road networkconditions
ITS ProjectITS
Project
1 IdentifyProjects
4-34
ITS ArchitectureWorkshop Use to Identify Projects
ITS Projects
ITS Architecture
1. Region description2. Stakeholder
identification3. ITS elements4. ITS services5. Operational concept6. Functional
requirements7. Interfaces /
Information flows 8. Standards
identification9. Project sequencing
10. Agreements11. Maintenance plan
9. Project sequencing
1 IdentifyProjects
4-35
ITS ArchitectureWorkshop
Project Identification from Architecture
State DOT First DivisionState DOT Traffic Management Center
City Police AgenciesCity Police Dispatch Centers
State DOT and State Department of ...State Police Dispatch Center
State DOT First DivisionState DOT TMC Field Equipment
County Traffic Engineering DepartmentCounty Traffic Operations Center
City Traffic Engineering DepartmentCity Traffic Management Center
road network conditionsroad network conditions
roadway information system dataroadway information system status
road network conditions
road network conditions
road network conditions
road network conditions
Project A
Project C
Project B
1 IdentifyProjects
4-36
ITS ArchitectureWorkshop
Use to Define Project Details
2 ScopeProjects
ITS Architecture
1. Region description2. Stakeholder
identification3. ITS elements4. ITS services5. Operational concept6. Functional
requirements7. Interfaces /
Information flows 8. Standards
identification9. Project sequencing
10. Agreements11. Maintenance plan
Project Description Stakeholders involved Stakeholder roles &
responsibilities Potential partners Elements involved Integration opportunities Dependencies Budget estimate
Project Scoping
4-37
ITS ArchitectureWorkshop
Minnesota Statewide ITS Architecture Example
ID: S03Project Title: Enhance Traveler Information Map for Mobile DevicesTimeframe: Short Term – Years 0-3Transportation Policy Area: Traveler Safety, Statewide Connections, Twin Cities Mobility, Greater Minnesota Metropolitan and Regional MobilityITS Service Area: ATISDescription: A traffic flow map showing real-time traffic conditions of freeways and selected expressways in the metro area is currently available on Mn/DOT’s website for use by mobile devices that can access the Internet. This project will…Project Champion and Stakeholder: Project Champion: Mn/DOT (RTMC), Private Companies. Stakeholders: Mn/DOTProject Elements: RTMC, 511 Traveler Information Website, User Personal Portable Computing DevicesMarket Package: ATIS01 – Broadcast Traveler InformationInterconnects• RTMC (website) and User Personal Portable Computing Devices• RTMC and 511 Traveler Information Website• 511 Traveler Information Website and User Personal Portable Computing DevicesTechnology Assessment: Traffic flow map for the metro area is already available on the Mn/DOT website. Technology for making information formatted in a way that is usable on handheld devices is readily available.Project Dependency: This project is not dependent upon any other projects.Cost Estimate: $35KNeeds and Objectives AddressedNeed: TI03 – Provide traffic flow maps showing recurring or predicted freeway congestion levelsObjectives: O-2 – Reduce crashes due to unexpected congestion, O-24 – Reduce congestion and delay,…Agreement: Agreements may be required for this project between Mn/DOT and Private Companies thatdistribute handheld devices that disseminate traveler information.
2 ScopeProjects
4-38
ITS ArchitectureWorkshop
Common Programming Process
C- Project Prioritization by MPO/State DOT
B- Project Submittals by Project Sponsors
A- MPO/State DOT issues Request for Projects
D- Recommend Projects to Project Selection Committee/etc.
B- Project Submittals by Project Sponsors• Commitment to comply with Rule/Policy• Identify components of architecture in project
3 SubmitProjects
4-39
ITS ArchitectureWorkshop
Identify Architecture Components
MAG ITS Project Application Form FY09-13
3 SubmitProjects
4-40
ITS ArchitectureWorkshop
Common Programming Process
C- Project Prioritization by MPO/State DOT• Use criteria for architecture/integration
B- Project Submittals by Project Sponsors
A- MPO/State DOT issues Request for Projects
D- Recommend Projects to Project Selection Committee/etc.
4 PrioritizeProjects
4-41
ITS ArchitectureWorkshop
Example of Use during Project Prioritization
Rhode Island State Planning CouncilAddition of new criteria
4 PrioritizeProjects
4-42
ITS ArchitectureWorkshop
Use in Programming/BudgetingKeys for Success
Define near term projects in more specificity to feed into programming and budgeting processes Promote integration projects in
region Establish process that uses
architecture
4-43
ITS ArchitectureWorkshop
Architecture Use in Project Life Cycle
Planning
Programming/Budgeting
Operations &Maintenance
IdentifiedProject
Implementation
FundedProject
Monitoring &Evaluation
Implemented Project
RegionalArchitecture Use=
4-44
ITS ArchitectureWorkshop
Traditional Project Development Process Has Led to Success
Performance of products and materials well understood
Requirements well defined and understood
Proven, well-known technology Documented, proven designs
ProjectInitiation
PreliminaryEngineering
Plans, Specs &
EstimatesConstruction Project
CloseoutOperations &Maintenance
Result Long-Lasting Highways
are Designed, Built, and Tested
4-45
ITS ArchitectureWorkshop
Traditional Process Can Work for Low Risk ITS Projects
ProjectInitiation
PreliminaryEngineering
Plans, Specs &
EstimatesConstruction Project
CloseoutOperations &Maintenance
ITS infrastructure expansion projects Requirements Defined Product Performance Solid Technology Proven Designs Documented
4-46
ITS ArchitectureWorkshop
Traditional Process Does NOT Work for Complex ITS Projects
ProjectInitiation
PreliminaryEngineering
Plans, Specs &
EstimatesConstruction Project
CloseoutOperations &Maintenance
4-47
ITS ArchitectureWorkshop
SystemValidation
Concept ofOperations
Systems Engineering Project Lifecycle
Time Line
SystemRequirements
SystemVerification/
Deployment
SubsystemVerification
Unit / DeviceTesting
High-LevelDesign
DetailedDesign
Software / HardwareDevelopment
Field Installation
System Validation Plan
System Verification Plan(System Acceptance)
SubsystemVerification Plan
(Subsystem Acceptance)
Unit / DeviceTest Plan
Implementation
Document/Approval
Operationsand
Maintenance
Changesand
UpgradesRetirement/
Replacement
SystemValidation
RegionalArchitecture(s)
Feasibility Study/ Concept
Exploration
Concept ofOperations
4-48
ITS ArchitectureWorkshop
SystemValidation
Concept ofOperations
Systems Engineering and Traditional Project Development
SystemRequirements
SystemVerification/
Deployment
SubsystemVerification
Unit / DeviceTesting
High-LevelDesign
DetailedDesign
Software / HardwareDevelopment
Field Installation
ProjectInitiation
PreliminaryEngineering
Plans, Specs &
EstimatesConstruction Project
CloseoutOperations &Maintenance
Operationsand
Maintenance
Changesand
UpgradesRetirement/
Replacement
SystemValidation
RegionalArchitecture(s)
Feasibility Study/ Concept
Exploration
Concept ofOperations
4-49
ITS ArchitectureWorkshop
Systems Engineering Reduces Risk of Project Failure
Source: Standish Group Extreme Chaos 2009
4-50
ITS ArchitectureWorkshop
Purpose of Systems Engineering
Improve the chances of developing a system on-time and on-budget that meets the users’ needs▬ Reduce risk
▬ Control costs and schedule
▬ Satisfy users’ needs
▬ Improve system quality
4-51
ITS ArchitectureWorkshop
Systems Engineering Analysis Requirements
Rule/Policy requires all Highway Trust Fund-funded projects to be based on a systems engineering analysis▬ Identifies seven requirements “at a minimum”▬ Scale commensurate with project scope
1. Portion of Regional ITS Architecture 2. Participating agencies roles and responsibilities3. Requirements definitions4. Alternatives analysis5. Procurement options6. ITS standards and testing procedures7. Operations and management procedures and
resources
23 CFR 940.11
4-52
ITS ArchitectureWorkshop
Step by Step Architecture Use in Project Development
Regional ITSArchitecture
Concept ofOperations
SystemRequirements
High-LevelDesign
DetailedDesign
1
2
3
4
4-53
ITS ArchitectureWorkshop
Mapping ITS Project to the Regional Architecture
Identify the portion of the regional ITS architecture relevant to the project▬ ITS Services▬ Inventory Elements ▬ Functional Requirements▬ Interfaces/Information Flows
Should be identified early – before firm cost estimates are established
1
4-54
ITS ArchitectureWorkshop
Mapping ITS Project to the Regional Architecture (cont.)
The best approach depends on your regional architecture Potential entry points
▬ ITS Services▬ Project Sequencing▬ Inventory▬ Stakeholders
Develop a roadmap that identifies the best entry point and how to find other related items
ITSServices
ProjectSequencing Inventory
Stakeholders
1
4-55
ITS ArchitectureWorkshop
Example Entry Point for Architecture
Project Sequencing
Standards Identification
Operational Concept
Functional Requirements
Interfaces/ Information
Flows
Stakeholder Identification
Region Description
ITS Services
ITS Elements
Agreements
4-56
ITS ArchitectureWorkshop
Mapping ITS Project to the Regional Architecture (cont.)
Regional architecture will include more integration opportunities than can be implemented in a single project▬ Account for future integration requirements
in current project▬ Consider how current project will support
future extensions▬ Phased implementation
1
4-57
ITS ArchitectureWorkshop
Example Maine DOT DMS Project Architecture Subset
Maine Department of TransportationMaine DOT Communications Center
MEMA EOC Maine Department of TransportationPortable Work Zone Field Devices
Maine Department of TransportationMaine DOT Field Devices
Maine Department of TransportationCARS
Local Traffic Operations Center Maine Turnpike 24HR CommunicationsCenter
alert statusemergency traffic control information
alert notificationemergency traffic control request
roadway information system dataroadway information system status
roadway information system dataroadway information system status
road network conditionstraffic information coordination
traffic information coordination
DMS ProjectFuture Project
1
4-58
ITS ArchitectureWorkshop
Step by Step of Architecture Use in Project Development
Regional ITSArchitecture
Concept ofOperations
SystemRequirements
High-LevelDesign
DetailedDesign
1
2
3
4
4-59
ITS ArchitectureWorkshop Concept of Operations
Get agreement on:▬ Goals, objectives, and
expectations▬ Project Scope▬ Stakeholder
responsibilities▬ How the system will
operate▬ Operational and support
environmentOperator MaintainerUser
* Adapted from ANSI/AIAA G-043-1992
Concept ofOperations 2
4-60
ITS ArchitectureWorkshop
Architecture Use in aConcept of Operations
Concept of Operations*
1. Scope
2. Referenced Documents
3. User-Oriented Operational Description
4. Operational Needs
5. System Overview
6. Operational Environment
7. Support Environment
8. Operational Scenarios
* Outline per ANSI/AIAA G-043-1992
Concept ofOperations 2
ITS Architecture
1. Region description2. Stakeholder
identification3. Operational Concept4. Agreements5. Functional
requirements6. Interfaces /
Information flows 7. Standards
identification8. Project sequencing9. Maintenance plan
10. ITS Elements11. ITS Services
4-61
ITS ArchitectureWorkshop
Example of Architecture Use in Con Ops
Maine DOT DMS Project Roles and ResponsibilitiesArchitectureRoles and Responsibilities
Project Roles and ResponsibilitiesMaine DOT M&O
Develop DMS System Operate DMS System Maintain DMS System Coordinate with partners
Maine DOT (Other Areas)
Support System Development
City of Portland
Coordinate diversion/detours with Maine DOT
Adapt signal control (future)
… …
Maine DOT Provides the roadside elements of traffic information dissemination including DMS and HAR
Local Traffic Departments
Share traffic information with other transportation agencies
… …
Concept ofOperations 2
4-62
ITS ArchitectureWorkshop System Requirements
Quality Requirements Necessary Unambiguous Complete Measurable Consistent Achievable Testable Technology independent
Specify exactly whatis to be accomplished, how well it is to be accomplished, and under what conditions it is to be accomplished
SystemRequirements
3
4-63
ITS ArchitectureWorkshop
Architecture Use inRequirements
Concept ofOperations
High-LevelDesign
DetailedDesign
SystemRequirements
3
SystemRequirements
ITS Architecture
1. Region description2. Stakeholder
identification3. Operational Concept4. Agreements5. Functional
requirements6. Interfaces /
Information flows 7. Standards
identification8. Project sequencing9. Maintenance plan
10. ITS Elements11. ITS Services
4-64
ITS ArchitectureWorkshop
Example of Architecture Use in Requirements
Maine DMS Architecture Requirements
ElementFunctional Area ID Requirement
Maine DOT Communications Center
TMC Traffic Information Dissemination
1 The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
Maine DMS Project Requirements– 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
SystemRequirements
3
4-65
ITS ArchitectureWorkshop System Design
Appropriate selection of system components and their interconnection to meet the system requirements
andThe preparation of specifications that describe the design
High-LevelDesign
DetailedDesign
4
4-66
ITS ArchitectureWorkshop Architecture Use in Design
Concept ofOperations
SystemRequirements
High-LevelDesign
DetailedDesign
4
High-LevelDesign
DetailedDesign
ITS Architecture
1. Region description2. Stakeholder
identification3. Operational Concept4. Agreements5. Functional
requirements6. Interfaces /
Information flows 7. Standards
identification8. Project sequencing9. Maintenance plan
10. ITS Elements11. ITS Services
4-67
ITS ArchitectureWorkshop
Example Architecture Use in Design
High-LevelDesign
DetailedDesign
4
Maine Department of TransportationMaine DOT Communications Center
MEMA EOC Maine Department of TransportationPortable Work Zone Field Devices
Maine Department of TransportationMaine DOT Field Devices
Maine Department of TransportationCARS
Local Traffic Operations Center Maine Turnpike 24HR CommunicationsCenter
alert statusemergency traffic control information
alert notificationemergency traffic control request
roadway information system dataroadway information system status
roadway information system dataroadway information system status
road network conditionstraffic information coordination
traffic information coordination
DMS ProjectFuture Project
4-68
ITS ArchitectureWorkshop
Example Architecture Use in Design (cont.)
Architecture interfaces are a starting point for project interface design
CommunicationsCenter
Cabinet/SignController
Local Computer
Sign
ICD 123-1(NTCIP)
ICD 123-2(NTCIP)
ICD 123-3
High-LevelDesign
DetailedDesign
4
NTCIP 1203, …
Maine Department of TransportationMaine DOT Communications Center
Maine Department of TransportationMaine DOT Field Devices
roadway information system dataroadway information system status
4-69
ITS ArchitectureWorkshop
Providing Feedback to the Architecture Maintainer
ITS Architecture
1. Region description2. Stakeholder
identification3. Operational Concept4. Agreements5. Functional
requirements6. Interfaces /
Information flows 7. Standards
identification8. Project sequencing9. Maintenance plan
10. ITS Elements11. ITS Services
Concept ofOperations
SystemRequirements
High-LevelDesign
DetailedDesign
Architecture Maintainer
4-70
ITS ArchitectureWorkshop
A Regional ITS Architecture is a Living ‘Document’
To remain useful, the architecture must be kept up to date Need a Plan to maintain it Required in the Rule/Policy:
▬ The agencies and other stakeholders participating in the development of the regional ITS architecture shall develop and implement procedures and responsibilities for maintaining it, as needs evolve within the region.
4-71
ITS ArchitectureWorkshop Update the Maintenance Plan
4-72
WHO will be responsible? ▬ Suggesting, approving, making changes
WHEN will updates occur?▬ How often, under what circumstances
WHAT will be maintained? ▬ Databases, website, documents
HOW will changes be managed?▬ Change management procedures▬ Version controls, naming conventions▬ Stakeholder notification
ITS ArchitectureWorkshop Session Outcomes
Identify how the regional architecture can support long range planning activities Describe how an architecture can be used to
program/budget ITS projects Describe the relationship between
architecture and systems engineering
4-73
Recommended