2005 Version 2.0 Architecture Changes
Stakeholders | System Inventory | Market Packages | Flows | Operating Concept | Funtional Requirements | Previous Updates
The following describe the minor changes to the VDOT NoVA ITS Architecture based on validation meetings with stakeholders, and other VDOT NoVA tasks since April 2005.
Stakeholder Updates
DeletionsThe following stakeholders names were deleted either because their roles have been covered by other stakeholder descriptions or to ensure consistency with MWCOG's architecture.
- Deleted DC/MD
- Deleted District of Columbia
- Deleted EZ Pass Administration
- Deleted FEMA
- Deleted Local Law Enforcement Agencies
- Deleted Maryland Arterial Management Agencies
- Deleted Maryland Toll Administration
- Deleted MTAG
- Deleted Pakring Management Agencies (this pertains to non-VDOT parking management; it was decided that they were not needed in the architecture)
- Deleted Partners in Motion as the stakeholder does not exist anymore
- Deleted Regional Data Archive Organziations - this is under CAPCOM
The following stakeholders have been deleted to simplify the representation of VDOT agencies - their functions are under VDOT Central Office as the stakeholder.
- IMMP - Removed as stakeholder - and added as an element under VDOT Central office and renamed it to Asset Management.
- VDOT Data Management Division
- VDOT Maintenance Division
- VDOT Traffic Engineering Division
- VDOT TEOC
Renamed
The following stakeholder names were renamed to better express their roles or to ensure consistency with MWCOG's architecture.- Renamed District of Columbia Public Safety Agencies to District of Columbia Public Safety and Emergency Agencies
- Renamed maryland Public Safety Agencies to Maryland Public Safety and Emergency Management.
- Renamed NoVA Public Safety Agencies to NoVA Public Safety and Emergency Management Agencies
- Renamed Rail Operators to Freight Rail Operators
- Renamed Virginia Emergency Management to Virginia Public Safety and Emergency Management and included in stakeholder group NoVA Public Safety and Emergency Management Agencies
- Renamed Video Clearinghouse Agencies to Video Clearinghouses
Additions
The following stakeholder names were added to address new developments or to ensure consistency with MWCOG's architecture.
- Under Federal Agencies – added Federal Installations and FEMA as elements(renamed National Advisory Warning system as FEMA)
- Added Maryland Transit Administration – based on COG’s description - No elements identified as yet in architecture
- Added Regional Transit Electronic Clearinghouse
- Added Federal Law Enforcement
- Added General Public
- Added CapCOM
System Inventory Updates
Entity Mapping Changes
The following list indciates changes to mapping national ITS architecture entities to inventory elements. The changes are either to correct previous discrepancies or to ensure consistency with MWCOG's regional architecture.
- Added Emergency Telecommunications System as an entity under National Park Services
- Changed entity mapping from Emergency Management to Other Emergency Management for Federal Installations
- Changed entity mapping from Emergency Management to Other Emergency Management for Federal Installations
- Changed the entity mapping from Archived Data User to Archived Data Management for NVTC Center
- Added ISP entity for NoVA Local Transit Centers element
- Added Emergency Management entity for MWAA Center element.
- Added ISP entity to Media Outlets element
- Removed other ISP entity from VDOT NoVA CSC
- Added Rail Operations entity to VRE Center element.
- Deleted Other Parking Management element
- Changed the name to Freight Rail Operators from Rail Operators
Renamed
The following lists the inventory elements which were renamed to ensure consistency with MWCOG's regional architecture.
- Changed the name of DDOT ITMS element to DCDOT ITMS/TOC
- Changed DC Emergency Preparedness Center element to DC Public Safety and Emergency Management Center. Also changed the description to remove FBI from this and added it under federal agencies.
- Changed element name from special event promoters to Event Promoters
- Changed IMMP element to VDOT Asset Management
- Changed name of VDOT NoVA TCC to VDOT NoVA CSC
- Renamed Mobile Unified Command to Mobile Unified Command Center
- Added FEMA as a separate element (under federal agencies as stakeholder)
- Added University of Maryland to the description for Research and Data Collection Centers element
- Added Regional Transit Electronic Clearinghouse element under Regional Transit Electronic Clearinghouse stakeholder
- Added Federal Law enforcement under Federal agencies as stakeholder
- Added element NoVA Local Transit Vehicle under NoVA Local Transit Agencies as stakeholder.
- Added new element Virginia Transportation Information Portal (VTIP) under VDOT as stakeholder
- Added VDOT NoVA Maintenance Vehicles as an element to VDOT NoVA Maintenance and Construction Operations stakeholder
- Added a new element Virginia Statewide Information Clearinghouse under VDOT as stakeholder.
- Added CAPCOM Center and RITIS as new elements under CAPCOM stakeholder
- Added the following WMATA new elements
- Added the following WMATA new elements:
WMATA Operations Centers
WMATA Transit Bus (BTRA)
WMATA Transit Police (MTPD) Operations Control Center
WMATA Smart Trip Card
WMATA In Station Displays & Kiosks - Added VDOT NoVA ITS MCO as an element under VDOT NoVA District as stakeholder - to represent ITS Maintenance activities which are expected to be delineated from the regular maintenance and construction operations.
Stakeholder Association Changes
- Moved Laptop Computers element to VDOT NoVA District stakeholder from VDOT stakeholder.
- Moved Statewide 511 Virginia element to VDOT Central Office from VDOT
- Moved VDOT NoVA Parking Management to VDOT NoVA District from VDOT.
- Moved RWIS element to VDOT Central Office
- Moved VDOT Mobility Store to VDOT Central office
Market Packages Updates
New Market Packages:
Added Probe Surveillance (ATMS 02) as a new market package with the following elements. The market package represents a desire of the NoVA STC to obtain travel time data from toll readers and toll administration agencies in the region.
Added Multimodal Coordination (APTS 7) to address transit signal priority with the following elements.
Updates to Existing Market Packages:
- Added new element CapCOM center to Network Surveillance (ATMS 01) Market package.
- Added new element CapCOM center to Freeway Control (ATMS 04) Market package.
- Added new elements CapCOM center and VDOT VOIS to Traffic Information Dissemination (ATMS 06)
- Added new elements CapCOM center, VDOT VOIS, RITIS, WMATA Operations Center, WMATA Transit Police (MTPD) Operations Control Center to Traffic Incident Management (ATMS 08)
- Added new elements WMATA Smart trip card to Parking Facility Management (ATMS 16)
- Added WMATA Operations Center and VRE Center elements to Regional Parking Management (ATMS 17) to address parking management cooperation between VDOT owned parking facilities and others.
- Added new elements CapCOM center, RITIS, VDOT NoVA GIS, VDOT NoVA CSC and VDOT VOIS to Roadway Closure Management (ATMS 21)
- Added new element VDOT Asset Management to Maintenance and Construction Vehicle Maintenance (MC 02)
- Added elements CapCOM center, VDOT NoVA STC, VDOT NoVA STSS, VDOT VOIS, Virginia Statewide Transportation Information Clearinghouse to Weather Information Processing and Dissemination (MC 04)
- Added elements CapCOM center, VDOT NoVA CSC, VDOT NoVA ITS MCO to Roadway Maintenance and Construction (MC 07)
- Added Asset Management, CapCOM center, RITIS, VDOT VOIS, VDOT NoVA ITS MCO to Maintenance and Construction Activity Coordination (MC 10)
- Added WMATA Operations Center and WMATA Transit Bus (BTRA) -Buses to Transit Fixed Route Operations (APTS 02)
- Added WMATA Operations Center to Transit Demand Responsive Operations (APTS 03)
- Added WMATA Operations Center, WMATA Smart trip card and WMATA Transit Bus (BTRA) -Buses to Transit Passenger and Fare Management (APTS 04)
- Added Local Transit Centers, Local Transit Vehicles, WMATA Operations Center, WMATA Transit Police (MTPD) Operations Control Center and WMATA Transit Bus (BTRA) -Buses to Transit Security (APTS 05)
- Added WMATA Operations Center, WMATA In-Station Displays_Kiosks and WMATA Transit Bus (BTRA) -Buses to Transit Traveler Information (APTS 08)
- Added VDOT VOIS to Interactive Traveler Information (ATIS 02) to account for current use of the VOIS system to gather data for the 511 service
- Added CapCOM center, Federal Law Enforcement, Maryland CHART, MWAA Center and VDOT Video Clearinghouse to Transportation Infrastructure Protection (EM 05)
- Added Adjacent STCs, CapCOM center to Wide Area Alert (EM 06)
- Added CapCOM center to Early Warning System (EM 07)
- Added elements CapCOM center, VDOT VOIS, WMATA Operations Center, WMATA Transit Police (MTPD) Operations Control Center to Disaster Response and Recovery (EM 08)
- Added elements CapCOM center, VRE Center, WMATA Operations Center, WMATA Transit Police (MTPD) Operations Control Center to Evacuation and Re-entry Management (EM 09)
- Added elements CapCOM center, WMATA Operations Center, WMATA In Station Displays_Kiosks, RITIS to Disaster Traveler Information (EM 10)
Information Flows Updates
Turbo software was used to build the information flows and the interfaces. Various new flows and interconnections were identified.All the information flow diagrams were recreated and the operational concept for each of them revised and updated. Several new diagrams were also added to the website including information flow diagrams featuring interfaces from/to CapCOM, WMATA and VDOT VOIS (all new elements in the architecture).
A new internal frame was added to each element page to enhance readability of flow information.
Operating Concept Updates
VDOT has identified a separate task (Task D-3) for a NoVA-specific Concept of Operations (COO) Development.In addition to roles and responsibility statements in the Turbo Database, VDOT NoVA architecture also defined operational concepts by information flow diagrams. Each information flow diagram has a concept of operations associated with it on the website. Another source for concept of operations is the customized market package descriptions on the website.
A separate tab was added to the main menu called "Op. Concept" which leads to a page with a list of all the available information flow diagrams.
Functional Requirements Updates
Functional requirements are high-level descriptions of what each part of the regional ITS system must do. They are normally expressed as “shall statements”.To ensure readability, the “shall” statements are not provided on the website. They are available in the Turbo database where these statements can be viewed by element.
The website only lists the functional area and the functional area description
for each element at the bottom of the element page.
Previous Updates
What's new in Version 1.2