Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
ITS CANDIDATE SYSTEMS, STANDARDS, AND PRODUCTS REPORT
June 24, 2003
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
ITS CANDIDATE SYSTEMS, STANDARDS, AND PRODUCTS REPORT
Prepared by
PB Farradyne
For
The Minnesota Department of Transportation Office of Traffic Engineering, Security and Operations
Although manufacturer and product names are used throughout this report, it is to be recognized that such use in no manner constitutes an endorsement by Mn/DOT, their project sponsors or the report authors. Trade or manufacturer names have been used solely because they are considered essential to the objective of this report. Likewise, it is acknowledged that certain product names as used in this report are the registered trademarks of specific corporations.
ITS Candidate Systems, Standards, and Products Final Report
June 24, 2003 i
TABLE OF CONTENTS
TABLE OF CONTENTS...........................................................................i
EXECUTIVE SUMMARY................................................................................ii
CHAPTER 1- INTRODUCTION .......................................................................1
CHAPTER 2 - SUMMARY LISTING OF MINNESOTA’S ITS SYSTEMS FOR STANDARDS CONSIDERATION .....................................................................2
CHAPTER 3 - ITS SYSTEMS GROUPED BY MARKET PACKAGES......................4 ITS Data Mart (AD1) ........................................................................................................4 ITS Data Warehouse (AD2) ..............................................................................................5 Transit Vehicle Tracking (APTS1) .....................................................................................6 Transit Fixed-Route Operations (APTS2) ...........................................................................7 Demand Response Transit Operations (APTS3) ................................................................8 Transit Passenger and Fare Management (APTS4)............................................................9 Transit Security (APTS5) ................................................................................................10 Multi-modal Coordination (APTS7) ..................................................................................11 Broadcast Traveler Information (ATIS1) ..........................................................................12 Interactive Traveler Information (ATIS2) ..........................................................................13 Network Surveillance (ATMS01) .....................................................................................14 Surface Street Control (ATMS03) ....................................................................................16 Freeway Control (ATMS04) ............................................................................................17 HOV Lane Management (ATMS05).................................................................................18 Traffic Information Dissemination (ATMS06) ....................................................................18 Regional Traffic Control (ATMS07)..................................................................................19 Incident Management System (ATMS08) ........................................................................20 Traffic Forecast and Demand Management (ATMS09) ....................................................21 Virtual TMC and Smart Probe Data (ATMS12) .................................................................22 Standard Railroad Grade Crossing (ATMS13).................................................................23 Advanced Railroad Grade Crossing (ATMS14) ...............................................................24 Parking Facility Management (ATMS16) .........................................................................25 Reversible Lane Management (ATMS17)........................................................................26 Road Weather Information System (ATMS18) ..................................................................27 Regional Parking Management (ATMS19).......................................................................28 Fleet Administration (CVO01) .........................................................................................29 Emergency Response (EM1)..........................................................................................30 Emergency Routing (EM2) .............................................................................................31 Mayday Support (EM3)..................................................................................................32
CHAPTER 4 – SYSTEM DESCRIPTIONS AND CONTACT RESOURCE LISTING .. 34 Table 4.1 – System Description and Contact Resource Information..................................35
CHAPTER 5 – MINNESOTA ITS STANDARD MIGRATION MATRIX................. 52
CHAPTER 6 –PRODUCT AVAILABILITY FOR MINNESOTA ITS SYSTEMS ....... 53
CHAPTER 7 - SUMMARY........................................................................... 64
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
ii June 24, 2003
EXECUTIVE SUMMARY
Mn/DOT, as with transportation operating agencies throughout the nation is striving to take advantage of the benefits of standardization and comply with the requirements for the use of ITS standards as set forth by the US DOT. Mn/ DOT, to an extent far greater than many operating agencies, have an existing freeway management system infrastructure and have carried out an extensive ITS research and testing program (i.e. FHWA Field Operational Tests). Many of these test applications have been transitioned into on-going deployments. In other cases, completely new ITS projects and systems have been deployed or are planned by Mn/DOT or other Minnesota transportation operating agencies.
This “ITS Candidate Systems, Standards and Products Report” is an important but only one step in an organized, multi–faced, multi-year program for Mn/DOT and other Minnesota agencies to migrate to the routine use of available and beneficial standards.
The report provides an inventory of existing and planned Minnesota ITS systems then proceeds to relate these systems to the national ITS architecture and in turn applicable standards. The report further notes the development status of these standards and presents information on the status of actual products incorporating these standards.
FHWA review comments were solicited on draft versions of this report and have been reflected in this final report.
A “ITS Standards Recommendations Report” will follow this “ITS Candidate Systems, Standards and Products Report”. Since a number of units of Mn/DOT plus other Minnesota agencies will be responsible for implementing the applicable standards, both reports will draw upon the views of not only national standards experts but the perspectives of Minnesota stakeholders as well.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
1 / 64 June 24, 2003
CHAPTER 1- INTRODUCTION
This ITS Candidate Systems, Standards, and Products Report provide a basis for recommendations regarding the implementation of Intelligent Transportation Systems (ITS) standards for Minnesota Department of Transportation (Mn/DOT) ITS systems and selected ITS systems of other agencies. This report identifies the following:
a.) ITS systems that currently exist or are planned in the near future,
b.) ITS standards that apply to those systems along with the current status and availability of the standards, and
c.) The availability of products that conform to ITS standards.
A system, as used in this report, may be an automated hardware or software application as well as a manual process.
The systems examined in this report are organized by Market Packages listed on the National ITS Architecture and Minnesota Statewide ITS Architecture completed in 2001. This report contains a summary description of existing and planned Mn/DOT ITS Systems, and also maps the associated Market Packages. Each Market Package contains a description and graphic from the national ITS architecture for that Market Package and identifies the associated Minnesota projects.
A separate “ITS Standards Recommendation Report” will follow this “ ITS Candidate Systems, Standards, and Products Report”. Recommendations based upon information developed in preparing the two reports are envisioned to include: (1) immediate adoption of matured ITS standard-based equipment; for new systems where ITS standards are available and mature and where products are available; (2) testing of ITS standard-based equipment that is available but unfamiliar to Mn/DOT; and (3) do nothing until a future time when standards for those systems may be more mature or more standard based products are available. Where standards are not yet available nor do not meet Mn/DOT's needs, Mn/DOT may participate in the standards development process as appropriate to ensure the resulting standards work for Mn/DOT
.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
2 / 64 June 24, 2003
CHAPTER 2 - SUMMARY LISTING OF MINNESOTA’S ITS SYSTEMS FOR STANDARDS CONSIDERATION
In order to analyze which standards may be applicable to Minnesota ITS operations, it is first necessary to establish a base line inventory or listing of potentially applicable “ITS Systems” that are existing or planned in Minnesota. Following, by title only, is a listing of these existing and planned systems. Subsequent chapters of the report will show the association of these various systems with one or more of the “Market Package” breakdowns used in the National ITS Architecture, as well as the associated national Standard(s). Also contained in Chapter 4 of this report is a table with a brief description of each system and point of contact for more detailed information.
The listing of Minnesota ITS Systems is as follows: • TMC 30 Seconds Detector Volume/Occupancy Archive • TMC Incident Log Archive • Automatic Traffic Recorder (ATR) Data • Transit Scheduling System (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth
Metrolink Transit, Metro Mobility, Dakota Area Resources and Transportation for Seniors [DARTS] etc.)
• Transit Driver Assignment (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink Transit, Metro Mobility, DARTS etc.)
• Transit Dispatch (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink Transit, Metro Mobility, DARTS, etc.)
• Transit Automatic Vehicle Location (AVL) System (Metro Transit, DARTS [planned], Duluth Transit [planned], etc.)
• Transit Passenger Counters • Transit Vehicle Video Cameras • Metro Park and Ride Surveillance Cameras • Freeway and Arterial Surveillance Systems (St. Paul, MPLS, Hennepin County, TH 55, ICTM,
etc.) • RWIS Video Surveillance System • AXIS Server - Snapshot • Portable Traffic Management System (PTMS) Video Surveillance Component • Transit Bus Priority system (Metro Transit, St. Cloud, etc.) • Traffic Signal Priority/Pre-Emption Equipment • TMC Data Distribution Server • KBEM • Metro Transit Telephony System • Scenic Byways Kiosk System • 511 • Orion Parking Garage Monitors • Transit Schedule Web Pages • Transit Trip Planner • Metro Traffic Management Web Pages • 511 Web Pages • ST. Paul Advanced Parking Information System (APIS) • Minneapolis Parking Management System • Commercial Vehicle Information Systems and Networks (CVISN) • Closed Loop Signal Controllers & Detectors • Centralized Traffic Signal Systems & Detectors (St. Paul, MPLS, & Icons)
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
3 / 64 June 24, 2003
• Isolated Signal Controllers & Detectors • Lane Control Signals
• Ramp Meter and Detector Stations • TH 55 Automatic Vehicle Identification (AVI) System (License plate readers) • Condition Acquisition and Reporting System (CARS) and the Maintenance Driver Automated
Recording System (MDARS) • Virtual Transportation Operation Center (VTOC) Software • Integrated Corridor Traffic Management (ICTM) • High Occupancy Vehicle (HOV) Lane Gate System • HOV Lane Open/Closed Sign System • PTMS Dynamic Message Sign Component • Freeway and Arterial Dynamic Message Signs • Computer Aided Dispatching System for 911 (CAD 911) / State Patrol AVL System • Highway Helper AVL System (Current Ball system and planned Intergraph system) • I-90 Gate Control System (Existing and planned) • Highway Railroad Intersection System (Existing and Planned) • Train Detectors • Mn/DOT Statewide Road Weather Information System (RWIS) • Automatic Weather Observing Systems (AWOS) • Safety Automatic Intelligent Locator (SAIL) Maintenance AVL System (Existing and future
planned expansion) • Intelligent Vehicle Initiative (IVI) Systems (TH 7, TH 19, TH 101, etc) • Mayday System
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
4 / 64 June 24, 2003
CHAPTER 3 - ITS SYSTEMS GROUPED BY MARKET PACKAGES
This Chapter represents the various ITS systems in the State of Minnesota and shows the mapping of these systems to the ITS National Systems Architecture Market Packages. The list of Minnesota ITS Systems, related Market Packages and applicable Standards discussed in this report are those viewed to be the primary responsibility of public transportation agencies as opposed to say those standards primarily the responsibility of a vehicle manufacturer. The MnDOT specific Market Packages were developed with Version 3.0 of the National ITS Architecture. Although version 4.0 of the National ITS Architecture is available, this report does not need to be updated since the newer version does not affect which specific ITS systems are being considered, but only the groupings.
The ITS National Architecture has been developed and is being routinely updated under the guidance of the USDOT with wide stakeholder input. Given that there is such a variety of potential ITS applications and interactions in an ITS Architecture (i.e., individual travelers, regular vehicles, roadways, transit vehicles, commercial vehicles, etc.), the various components have been grouped by what has come to be known as “Market Packages”. Market Packages identify the pieces (i.e., information flows) of the architecture needed to implement a specific service (i.e., a Road Weather Information System (RWIS)).
The Minnesota Statewide ITS Architecture developed the following Market Packages that are viewed to be applicable to Minnesota Systems. :
ITS Data Mart (AD1)
This market package provides a focused archive that houses data collected and owned by a single agency, district, private sector provider, research institution, or other organization. This focused archive typically includes data covering a single transportation mode and one jurisdiction that is collected from an operational data store and archived for future use. It provides the basic data quality, data privacy, and meta data management common to all ITS archives and provides general query and report access to archive data users.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
5 / 64 June 24, 2003
Archived DataManagement
Government Reporting System Support
Archived Data Administrator
Archived Data User Systems
archiverequests +
archivestatus
archived data products archive management data
trafficarchivedata
archived data products requests
archive management data requests
TrafficManagement
Traffic Data Collection
ITS Data Repository
Any of the following ITS data source can be the source for an ITS Data Mart. The Traffic Management Subsystem is shown as an example.Data Sources:•Commercial Vehicle Administration•Emergency Management•Emissions Management •Information Service Provider•Parking Management•Roadway Subsystem•Toll Administration•Traffic Management•Transit Management
•Construction and Maintenance•Intermodal Freight Depot•Map Update Provider•Multimodal Transportation Service Provider•Other Data Sources•Weather Service
government reporting system data
GovernmentReportingSystems
AD1 - ITS Data Mart
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, and Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • TMC 30 Seconds Detector Volume/Occupancy Archive • TMC Incident Log Archive • ATR System
ITS Data Warehouse (AD2)
This market package includes all the data collection and management capabilities provided by the ITS Data Mart, and adds the functionality and interface definitions that allow collection of data from multiple agencies and data sources spanning across modal and jurisdictional boundaries. It performs the additional transformations and provides the additional meta data management features that are necessary so that all this data can be managed in a single repository with consistent formats. The potential for large volumes of varied data suggests additional on-line analysis and data mining features that are also included in this market package in addition to the basic query and reporting user access features offered by the ITS Data Mart.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
6 / 64 June 24, 2003
Archived DataManagement
On-Line Analysisand Mining
ITS Data Repository
Government Reporting System Support
Traffic and RoadsideData Archival
TrafficManagement
TrafficData Collection
Toll Administration
Toll Data Collection
EmergencyManagement
Emergency Data Collection
EmissionsManagement
Emission Data Collection
ParkingManagement
ParkingData Collection
Roadway
RoadsideData Collection
CommercialVehicle Adm.
CVData Collection
TransitManagement
TransitData Collection
Archived Data User Systems
WeatherService
Archived Data Administrator
IntermodalFreight Depot
Construction& Maintenance
Multimodal Transportation
Service Provider
sensor & surveillance control
archive request confirmation +archived data products
archive management data
Other DataSources
archive analysis results
archive data product requests
archive management requests
Government Reporting
Systems
government reportingdata receipt
weatherinfo.
intermodal freight archive data
multimodalarchive
data
transit archive data
emissions archive data
parking archive data
toll archive datatraffic archive data
commercial vehicle archive data
emergency archive data
roadside archive data
other data sourcearchive data
archive requests
archive requests
archive requests
archiverequests
archive requests
archive requests
archiverequests
Information ServiceProvider
Emergency Data Collection
travelerarchive data
archiverequests
construction &maintenance
AD2 - ITS Data Warehouse
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram.
List of Systems Under this Market Package:
[None exist]
Transit Vehicle Tracking (APTS1)
This market package provides for an Automated Vehicle Location System to track the transit vehicle’s real time schedule adherence and updates the transit system’s schedule in real-time. Vehicle position may be determined either by the vehicle (e.g., through GPS) and relayed to the infrastructure or may be determined directly by the communications infrastructure. A two-way wireless communication link with the Transit Management Subsystem is used for relaying vehicle position and control measures. Fixed route transit systems may also employ beacons along the route to enable position determination and facilitate communications with each vehicle at fixed intervals. The Transit Management Subsystem processes this information, updates the transit schedule and makes real-time schedule information available to the Information Service Provider Subsystem via a wireline link.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
7 / 64 June 24, 2003
APTS1 - Transit Vehicle Tracking
TransitManagement
Transit Center Trackingand Dispatch
Transit Vehicle
On-board TripMonitoring
InformationService Provider
transit and fareschedules
transit informationrequest
transit vehiclelocation data
Vehicle
vehiclelocation
transit vehicle schedule performance
Vehicle LocationDetermination
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Transit AVL System (Metro Transit, DARTS [planned], Duluth Transit [planned], etc.)
Transit Fixed-Route Operations (APTS2)
This market package performs automatic driver assignment and monitoring, as well as vehicle routing and scheduling for fixed-route services. This service uses the existing AVL database as a source for current schedule performance data, and is implemented through data processing and information display at the transit management subsystem. This data is exchanged using the existing wire line link to the information service provider where it is integrated with that from other transportation modes to provide the public with integrated and personalized dynamic schedules.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
8 / 64 June 24, 2003
APTS2 - Transit Fixed-Route Operations
TransitManagement
Transit Center Fixed Route Operations
Transit Vehicle
On Board Fixed Route Schedule Management
InformationService Provider
transit and fareschedules
transit informationrequest
driver instructions
traffic information
for transit
Transit Garage Operations
Transit Driver
route assignment
transit driver
availability
TrafficManagement
transit vehicleschedule performance
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: Dispatching for: • Transit Scheduling System (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth
Metrolink Transit, etc.) • Transit Driver Assignment (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth
Metrolink Transit, etc.) • Transit Dispatch (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink
Transit, etc.)
Demand Response Transit Operations (APTS3)
This market package performs automatic driver assignment and monitoring as well as vehicle routing and scheduling for demand response transit services. This package uses the existing AVL database to monitor current status of the transit fleet and supports allocation of these fleet resources to service incoming requests for transit service while also considering traffic conditions. The Transit Management Subsystem provides the necessary data processing and information display to assist the transit operator in making optimal use of the transit fleet. The Information Service Provider Subsystem may be either be operated by transit management center or be independently owned and operated by a separate service provider. In the first
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
9 / 64 June 24, 2003
scenario, the traveler makes a direct request to a specific paratransit service. In the second scenario, a third party service provider determines the paratransit service is a viable means of
satisfying a traveler request and uses wireline communications to make a reservation for the traveler.
APTS3 - Demand Response Transit Operations
TransitManagement
Transit Center Paratransit Operations
Transit Vehicle
On-Board ParatransitOperations
transit and fareschedules
transit vehicle passenger and use data
driver instructions
Transit GarageOperations
selected routes
demand responsivetransit plan
traffic informationfor transit
Transit Driver
route assignment
transit driver
availability
TrafficManagement
InformationService
Provider
demand responsivetransit request
transit information request
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Transit Scheduling System (Metro Mobility, DARTS, etc.) • Transit Driver Assignment (Metro Mobility, DARTS, etc.) • Transit Dispatch (Metro Mobility, DARTS, etc.)
Transit Passenger and Fare Management (APTS4)
This market package allows for the management of passenger loading and fare payments on-board vehicles using electronic means. The payment instrument may be either a stored value or credit card. This package is implemented with sensors mounted on the vehicle to permit the driver and central operations to determine vehicle loads, and readers located either in the infrastructure or on-board the transit vehicle to allow fare payment. Data is processed, stored, and displayed on the transit vehicle and communicated as needed to the Transit Management Subsystem using existing wireless infrastructure.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
10 / 64 June 24, 2003
Remote TravelerSupport
TransitManagement
Transit Center Fare and Load Mgmt
Transit Vehicle
On-Board TransitFare and Load Mgmt
InformationService Provider
transit requestconfirmation
transit informationrequest
transit vehicle passenger and use data
bad tag list
Remote TransitFare Management
transit farepayment
request
transit fare payment responses
PaymentInstrument
paymentrequest forpayment
FinancialInstitution
paymentrequest
transactionstatus
EnforcementAgency
violationnotification
payment
request for payment
fare and payment status
APTS4 Transit Passenger and Fare Management
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Transit Passenger Counters
Transit Security (APTS5)
This market package provides for the physical security of transit passengers. An on-board security system is deployed to perform surveillance and warn of potentially hazardous situations. Public areas (e.g. stops, park and ride lots, stations) are also monitored. Information is communicated to the Transit Management Subsystem using the existing or emerging wireless (vehicle to center) or wireline (area to center) infrastructure. Security related information is also transmitted to the Emergency Management Subsystem when an emergency is identified that requires an external response. Incident information is communicated to the Information Service Provider.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
11 / 64 June 24, 2003
APTS5 - Transit Security
Remote TravelerSupport
TransitManagement
Transit Center Security
Transit Vehicle
On-Board TransitSecurityemergency
acknowledge
emergencynotification
emergencyacknowledge
emergencynotification
transitemergency
data
transitemergency coordinationdata
Secure Area Monitoring
secure area monitoring support
InformationService Provider
transitincident information
EmergencyManagement
secure areasurveillance data
Remote Mayday I/F
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Transit Vehicle Video Cameras • Metro Park and Ride Surveillance Cameras
Multi-modal Coordination (APTS7)
This market package establishes two-way communications between multiple transit and traffic agencies to improve service coordination. Intermodal coordination between transit agencies can increase traveler convenience at transfer points and also improve operating efficiency. Coordination between traffic and transit management is intended to improve on-time performance of the transit system to the extent that this can be accommodated without degrading overall performance of the traffic network. More limited local coordination between the transit vehicle and the individual intersection for signal priority is also supported by this package.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
12 / 64 June 24, 2003
APTS7 - Multi-Modal Coordination
TrafficManagement
TransitManagement
Transit Center Multi-modal Coordination
Transit Vehicle
On-board TransitSignal Priority
transit vehicleschedule performance
TMC Multi-modalCoordination
Roadway
Roadside SignalPriority
localsignalpriorityrequest
trafficcontrol priorityrequest
signal control data
request forright-of- way
trafficcontrolprioritystatus
transitsystem
data
transit parking lot response
transit parkingcoordination
Other TransitManagement
TRMScoordination
ParkingManagement
Multimodal TransportationService Provider
transit multimodalinformation
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Transit Bus Priority system (Metro Transit, St. Cloud, etc.) • Traffic Signal Priority/Pre-Emption Equipment
Broadcast Traveler Information (ATIS1)
This market package provides the user with a basic set of ATIS services; its objective is early acceptance. It involves the collection of traffic conditions, advisories, general public transportation, toll and parking information, incident information, air quality and weather information, and the near real time dissemination of this information over a wide area through existing infrastructures and low cost user equipment (e.g., FM subcarrier, cellular data broadcast). Different from the market package ATMS6--Traffic Information Dissemination--which provides the more basic HAR and DMS information capabilities, ATIS1 provides the more sophisticated digital broadcast service. Successful deployment of this market package relies on availability of real-time traveler information from roadway instrumentation, probe vehicles or other sources.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
13 / 64 June 24, 2003
ATIS1 - Broadcast Traveler Information
Remote TravelerSupport
Remote BasicInformation Reception
Vehicle
Basic VehicleReception
Personal InfoAccess
Personal BasicInformation Reception
broadcastinformation
broadcastinformation
TrafficManagement
TransitManagement
InformationService Provider
Basic InformationBroadcast
trafficinformation
transit and fareschedules
request for traffic information
transit informationrequest
broadcastinformation
EmergencyManagement
ParkingManagement
Media
WeatherService
weatherinformation
traveler information for media
incidentinformation
parkinginformation
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram.
List of Systems Under this Market Package: • KBEM
Interactive Traveler Information (ATIS2)
This market package provides tailored information in response to a traveler request. Both real-time interactive request/response systems and information systems that "push" a tailored stream of information to the traveler based on a submitted profile are supported. The traveler can obtain current information regarding traffic conditions, transit services, ride share/ride match, parking management, and pricing information. A range of two-way wide-area wireless and wireline communications systems may be used to support the required digital communications between traveler and the information service provider. A variety of interactive devices may be used by the traveler to access information prior to a trip or en-route to include phone, kiosk, Personal Digital Assistant, personal computer, and a variety of in-vehicle devices. Successful deployment of this market package relies on availability of real-time transportation data from roadway instrumentation, probe vehicles or other means.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
14 / 64 June 24, 2003
ATIS2 - Interactive Traveler Information
Personal InfoAccess
Remote TravelerSupport
Vehicle
Personal InteractiveInformation Reception
Remote InteractiveInformation Reception
Interactive VehicleReception
TrafficManagement
TransitManagement
InformationService Provider
Interactive InfrastructureInformation
trafficinformation
transit and fareschedules
request fortraffic information transit information
request
traveler information
travelerinformation
traveler requesttraveler request
travelerrequestMedia
traveler information
traveler informationfor media
ParkingManagement
parking information
WeatherService
weather information
EmergencyManagement
incidentinformation
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Metro Transit Telephony System • Scenic Byways Kiosk System • 511 • Orion Parking Garage Monitors • Transit Schedule Web Pages • Transit Trip Planner • Metro Traffic Management Web Pages • 511 Web Pages
Network Surveillance (ATMS01)
This market package includes traffic detectors, other surveillance equipment, the supporting field equipment, and wireline communications to transmit the collected data back to the Traffic Management Subsystem (agencies that were mapped to this category in the system inventory). The derived data can be used locally such as when traffic detectors are connected directly to a signal control system or remotely (e.g., when a CCTV system sends data back to the Traffic Management Subsystem). The data generated by this market package enables traffic managers to monitor traffic and road conditions, identify and verify incidents, detect faults in
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
15 / 64 June 24, 2003
indicator operations, and collect census data for traffic strategy development and long range planning. The collected data can also be analyzed and made available to users and the
Information Service Provider Subsystem (agencies that were mapped to this category in the system inventory).
ATMS01 - Network Surveillance
TrafficManagement
Collect TrafficSurveillance
Roadway
Roadway BasicSurveillance
InformationService Provider
trafficinformation
request fortraffic information
traffic flow
sensor andsurveillance control
Traffic Maintenance
traffic images
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Closed Loop Signal Controllers & Detectors • Centralized Traffic Signal Systems & Detectors (St. Paul, MPLS, & Icons) • Freeway and Arterial Video Surveillance Systems (St. Paul, MPLS, Hennepin County, TH 55,
ICTM, etc.) • PTMS Video Surveillance Component • RWIS Video Surveillance System • Metro Park and Ride Surveillance Cameras • Ramp Meter and Detectors Stations • TH 55 AVI System (License plate readers) • VTOC Software
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
16 / 64 June 24, 2003
Surface Street Control (ATMS03)
This market package provides the central control and monitoring equipment, communication links, and the signal control equipment that support local surface street control and/or arterial traffic management. A range of traffic signal control systems are represented by this market package ranging from static pre-timed control systems to fully traffic responsive systems that dynamically adjust control plans and strategies based on current traffic conditions and priority requests. Additionally, general advisory and traffic control information can be provided to the driver while en-route. This market package is generally an intra-jurisdictional package that does not rely on real-time communications between separate control systems to achieve area-wide traffic signal coordination. Systems that achieve coordination across jurisdictions by using a common time base or other strategies that do not require real time coordination would be represented by this package. This market package is consistent with typical urban traffic signal control systems.
ATMS03 - Surface Street Control
TrafficManagement
TMC SignalControl
Roadway
RoadwaySignal Controls
signal control data
TrafficMaintenance
signal control status
traffic flow
request for right-of-way
traffic images
sensor and surveillance control
Driver
driverinformation
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Isolated Signal Controllers & Detectors • Closed Loop Signal Controllers & Detectors • Centralized Traffic Signal Systems & Detectors (St. Paul, MPLS, & Icons)
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
17 / 64 June 24, 2003
Freeway Control (ATMS04)
This market package provides the communications and roadside equipment to support ramp control, lane controls, and interchange control for freeways. Coordination and integration of ramp meters are included as part of this market package. This package is consistent with typical urban traffic freeway control systems. This package incorporates the instrumentation included in the Network Surveillance Market Package to support freeway monitoring and adaptive strategies as an option. This market package also includes the capability to utilize surveillance information for detection of incidents. Typically, the processing would be performed at a traffic management center; however, developments might allow for point detection with roadway equipment. For example, a CCTV might include the capability to detect an incident based upon image changes. Additionally, this market package allows general advisory and traffic control information to be provided to the driver while en-route.
ATMS04 - Freeway Control
TrafficManagement
TMC FreewayManagement
Roadway
RoadwayFreeway Control
freeway control data
TrafficMaintenance
freeway control status
traffic flow
traffic images
Driver
driverinformation
sensor andsurveillance control
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Freeway and Arterial Video Surveillance Systems (St. Paul, MPLS, Hennepin County, TH 55,
ICTM, etc.) • Lane Control Signals • Ramp Meter and Detector Stations • VTOC Software • I-90 Gate Control System (future when integrated into VTOC software)
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
18 / 64 June 24, 2003
HOV Lane Management (ATMS05)
This market package manages HOV lanes by coordinating freeway ramp meters and connector signals with HOV lane usage signals. Preferential treatment is given to HOV lanes using special bypasses, reserved lanes, and exclusive rights-of-way that may vary by time of day. Vehicle occupancy detectors may be installed to verify HOV compliance and to notify enforcement agencies of violations.
ATMS05 - HOV Lane Management
TrafficManagement
TMC HOV Lane Management
Roadwayfreeway control data
Roadway HOV Control
HOV data
traffic flow
EnforcementAgency
violationnotification
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Note - No equipment is used for this function.
Traffic Information Dissemination (ATMS06)
This market package allows traffic information to be disseminated to drivers and vehicles using roadway equipment such as dynamic message signs or highway advisory radio. This package provides a tool that can be used to notify drivers of incidents; careful placement of the roadway equipment provides the information at points in the network where the drivers have recourse and
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
19 / 64 June 24, 2003
can tailor their routes to account for the new information. This package also covers the equipment and interfaces that provide traffic information from a traffic management center to
the media (for instance via a direct tie-in between a traffic management center and radio or television station computer systems), transit management center, emergency management center, and information service provider.
ATMS06 Traffic Information Dissemination
TrafficManagement
TMC Traffic InfoDissemination
Roadway
roadway informationsystem status Roadway Traffic Info
Dissemination
roadway informationsystem data
InformationService
Provider
trafficinformation
Driver
driverinformation
Mediatraffic information
for media
Basic Vehicle
broadcastadvisories
EmergencyManagement
TransitManagement current
networkconditions
traffic informationfor transit
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Freeway and Arterial Dynamic Message Signs • TMC Data Distribution Server • PTMS Dynamic Message Sign Component • APIS • Minneapolis Parking Management System • CARS and MDARS
Regional Traffic Control (ATMS07)
This market package advances the Surface Street Control and Freeway Control Market Packages by adding the communications links and integrated control strategies that enable integrated Interjurisdictional traffic control. This market package provides for the sharing of traffic information and control among traffic management centers to support a regional control
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
20 / 64 June 24, 2003
strategy. The nature of optimization and extent of information and control sharing is determined through working arrangements between jurisdictions. This package relies principally on
roadside instrumentation supported by the Surface Street Control and Freeway Control Market Packages and adds hardware, software, and wireline communications capabilities to implement traffic management strategies that are coordinated between allied traffic management centers. Several levels of coordination are supported from sharing of information through sharing of control between traffic management centers.
ATMS07 - Regional Traffic Control
TrafficManagement
Roadway
freeway control data
freeway control status
signal control data
signal control status
TMC RegionalTraffic Control
Other TM
traffic flow
trafficcontrol
coordination
trafficinformationcoordination
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • ICTM
Incident Management System (ATMS08)
This market package manages both predicted and unexpected incidents so that the impact to the transportation network and traveler safety is minimized. Requisite incident detection capabilities are included in the freeway control market package and through the regional coordination with other traffic management and emergency management centers, weather service entities, and event promoters supported by this market package. Information from these diverse sources are collected and correlated by this market package to detect and verify incidents and implement an appropriate response. This market package provides Traffic Management Subsystem equipment that supports traffic operations personnel in developing an appropriate response in coordination with emergency management and other incident response personnel to confirmed incidents. The response may include traffic control strategy modifications and presentation of information to affected travelers using the Traffic Information
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
21 / 64 June 24, 2003
Dissemination market package. The same equipment assists the operator by monitoring incident status as the response unfolds. The coordination with emergency management might
be through a CAD system or through other communication with emergency field personnel. The coordination can also extend to tow trucks and other field service personnel.
ATMS08 - Incident Management System
EmergencyManagement
TrafficManagement
TMC Incident DispatchCoord/Communication
Roadway
Other TM
trafficinformationcoordination
incident information
Emergency ResponseManagement
incident data
incident information
InformationService Provider
trafficinformation
roadway information system data
EmergencyVehicle
incidentstatus
TMC IncidentDetection
Roadway IncidentDetection
WeatherService
weatherinformation
loggedspecial vehicle
route
Construction &Maintenance
maintenance resource request
maintenance resource response
closure coordination
traffic images
sensor and surveillance control
OtherEM
incident report
EventPromoter
event plans
incidentresponse
coordination
incidentcommandinformation
incident information
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Freeway and Arterial Video Surveillance Systems (St. Paul, MPLS, Hennepin County, TH 55,
ICTM, etc.) • PTMS Video Surveillance Component • CARS and MDARS • CAD 911 / State Patrol AVL • Highway Helper AVL System • I-90 Gate Control Sign System
Traffic Forecast and Demand Management (ATMS09)
This market package includes advanced algorithms, processing, and mass storage capabilities that support historical evaluation, real-time assessment, and forecast of the roadway network performance. This includes the prediction of travel demand patterns to support better link travel time forecasts. The source data would come from the Traffic Management Subsystem itself as
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
22 / 64 June 24, 2003
well as other traffic management centers and forecasted traffic loads derived from route plans supplied by the Information Service Provider Subsystem (systems identified in the inventory). In
addition to short-term forecasts, this market package provides longer-range forecasts that can be used in transportation planning. This market package provides data that supports the implementation of TDM programs, and policies managing both traffic and the environment.
ATMS09 - Traffic Forecast and Demand Management
TrafficManagement
TMC Traffic NetworkPerformance Evaluation
InformationService Provider
Other TM
trafficinformationcoordination
Event Promoters
eventplans
trafficinformation
traffic flowRoadway
TMC Toll/ParkingCoordination
ParkingManagement
TransitManagement
TollAdministration
parking demand management response
parking demand management request
toll demand management response
toll demand management request
transit demandmanagement
response
transit demand management request
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • TMC 30 Seconds Detector Volume/Occupancy Archive • ATR System • CARS and MDARS • APIS • Minneapolis Parking Management System
Virtual TMC and Smart Probe Data (ATMS12)
This market package provides for special requirements of rural road systems. Instead of a central TMC, the traffic management is distributed over a very wide area (e.g., a whole state or collection of states). Each locality has the capability of accessing available information for assessment of road conditions.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
23 / 64 June 24, 2003
ATMS12 - Virtual TMC and Smart Probe Data
In-Vehicle SigningSystem
Vehicle
Roadway
Roadway Environment
Roadway
Automated RoadSigning
Roadway Probe Beacons
Smart Probe
roadway informationsystem data
vehicle probe data
vehicle signage data
vehicle probe data
roadwaycharacteristics
TrafficManagement
weatherconditions
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package:
• CARS and MDARS
Standard Railroad Grade Crossing (ATMS13)
This market package manages highway traffic at highway-rail intersections (HRIs) where operational requirements do not dictate more advanced features (e.g., where rail operational speeds are less than 80 miles per hour). Both passive (e.g., the crossbuck sign) and active warning systems (e.g., flashing lights and gates) are supported. (Note that passive systems exercise only the single interface between the roadway subsystem and the driver in the architecture definition.) These traditional HRI warning systems may also be augmented with other standard traffic management devices. The warning systems are activated on notification by interfaced wayside equipment of an approaching train. The equipment at the HRI may also be interconnected with adjacent signalized intersections so that local control can be adapted to highway-rail intersection activities. Health monitoring of the HRI equipment and interfaces is performed; detected abnormalities are reported to both highway and railroad officials through wayside interfaces and interfaces to the traffic management subsystem.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
24 / 64 June 24, 2003
ATMS13 - Standard Railroad Grade Crossing
TrafficManagement
HRI TrafficManagement
Roadway
Standard Rail Crossing
RailOperations
WaysideEquipment
hri status
Traffic
trafficcharacteristics
hri request
Pedestrians
Driver
crossingpermission
driverinformation
hri control data
hri advisories
trackstatus
hri operationalstatus
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Highway Railroad Intersection System (Existing and Planned) • Signal Priority/Pre-emption Equipment • Train Detectors
Advanced Railroad Grade Crossing (ATMS14)
This market package manages highway traffic at highway-rail intersections (HRIs) where operational requirements demand advanced features (e.g., where rail operational speeds are greater than 80 miles per hour). This market package includes all capabilities from the Standard Railroad Grade Crossing Market Package and augments these with additional safety features to mitigate the risks associated with higher rail speeds. The active warning systems supported by this market package include positive barrier systems that preclude entrance into the intersection when the barriers are activated. Like the Standard Package, the HRI equipment is activated on notification by wayside interface equipment that detects, or communicates with the approaching train. In this market package, additional information about the arriving train is also provided by the wayside interface equipment so that the train's direction of travel, its estimated time of arrival, and the estimated duration of closure may be derived. This enhanced information may be conveyed to the driver prior to, or in context with, warning system activation. This market package also includes additional detection capabilities that enable it to detect an entrapped or
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
25 / 64 June 24, 2003
otherwise immobilized vehicle within the HRI and provide an immediate notification to highway and railroad officials.
ATMS14 - Advanced Railroad Grade Crossing
TrafficManagement
HRI TrafficManagement
RailOperations
WaysideEquipment
hri status
trackstatus
Traffic
trafficcharacteristics
hri request
Pedestrians
Driver
crossingpermission
driverinformation
hri operational
statusintersection blockage
notification Roadway
AdvancedRail Crossing
arriving traininformation
intersectionblockage
notification
hri control data
hri advisories
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Highway Railroad Intersection System (Existing and Planned) • Train Detectors
Parking Facility Management (ATMS16)
This market package provides enhanced monitoring and management of parking facilities. The included equipment assists in the management of parking operations, coordinates with transportation authorities, and supports electronic collection of parking fees. This is performed by sensing and collecting current parking facilities status, sharing the data with information service providers and traffic operations, and automatic fee collection using short range communications with the same in-vehicle equipment utilized for electronic toll collection.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
26 / 64 June 24, 2003
ATMS16 - Parking Facility Management
Parking Management
Parking
ManagementVehicle
Vehicle Toll/Parking Interface
FinancialInstitution
PaymentInstrument
InformationService
Provider
tag update
tag data
transactionstatus
paymentrequest
EnforcementAgency
violationnotification
parkinginformation
request tag data
paymentrequest
forpayment
parking lot reservation confirmationParking Electronic
Payment
Parking Surveillance
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • APIS • Minneapolis Parking Management System
Reversible Lane Management (ATMS17)
This market package provides for the management of reversible lane facilities. In addition to standard surveillance capabilities, this market package includes sensory functions that detect wrong-way vehicles and other special surveillance capabilities that mitigate safety hazards associated with reversible lanes. The package includes the field equipment, physical lane access controls, and associated control electronics that manage and control these special lanes. This market package also includes the equipment used to electronically reconfigure intersections and manage right-of-way to address dynamic demand changes and special events.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
27 / 64 June 24, 2003
ATMS17 - Reversible Lane Management
Traffic
Management
TMC ReversibleLane Management
TrafficOperationsPersonnel
Roadway
Roadway ReversibleLanes
traffic flow
incident data
freeway control data
freeway control status
signal control status
signal control data
trafficoperator
inputs
trafficoperator
data
reversible lane status
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • HOV Lane Gate System • HOV Lane Open/Closed Sign System
Road Weather Information System (ATMS18)
This market package monitors current and forecast road and weather conditions using a combination of weather service information and data collected from environmental sensors deployed on and about the roadway. The collected road weather information is monitored and analyzed to detect and forecast environmental hazards such as icy road conditions, dense fog, and approaching severe weather fronts. This information can be used to more effectively deploy road maintenance resources, issue general traveler advisories, and support location specific warnings to drivers using the Traffic Information Dissemination Market Package.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
28 / 64 June 24, 2003
ATMS18 - Road Weather Information System
WeatherService
TrafficManagement
TMC Road WeatherMonitoring
Roadway
Roadway EnvironmentalMonitoring
Construction &Maintenance
RoadwayEnvironment
TrafficOperationsPersonnel
weatherinformation
maintenance resource request
maintenanceresourceresponse weather
conditions
environmental conditions
trafficoperator
inputs
trafficoperator
data
closurecoordination
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Mn/DOT Statewide RWIS System • AWOS • CARS and MDARS
Regional Parking Management (ATMS19)
This market package supports coordination between parking facilities to enable regional parking management strategies.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
29 / 64 June 24, 2003
ATMS19 - Regional Parking Management
ParkingManagement
Parking Management
Parking Coordination
TransitManagement
parkingavailability
transit parking lot response
transit parkingcoordination
parking demand management request
TrafficManagement
OtherParking
parking coordination
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • APIS • Minneapolis Parking Management System
Fleet Administration (CVO01)
This market package keeps track of vehicle location, itineraries, and fuel usage at the Fleet and Freight Management Subsystem using a cell based or satellite data link and the pre-existing wireless infrastructure. The vehicle has a processor to interface to its sensor (e.g., fuel gauge) and to the cellular data link. The Fleet and Freight Management Subsystem can provide the vehicle with dispatch instructions, and can process and respond to requests for assistance and general information from the vehicle via the cellular data link. The market package also provides the Fleet Manager with connectivity to intermodal transportation providers using the existing wireline infrastructure.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
30 / 64 June 24, 2003
CVO01 - Fleet Administration
Fleet and FreightManagement
Fleet Administration
CommercialVehicle
On-board Trip Monitoring
fleet to driver update
driver and vehicle information
CommercialVehicle Driver
CVO driverinitialization
Fleet Maintenance Management
alerts,messages
route plan
route request
InformationService Provider
vehiclelocation
Vehicle
Vehicle Location Determination
CommercialVehicle Manager
fleet status fleet managerinquiry
log information
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • CVISN • SAIL Maintenance AVL System (Existing and future planned expansion) • IVI Systems (TH 7, TH 19, TH 101, etc)
Emergency Response (EM1)
This market package provides the computer-aided dispatch systems, emergency vehicle equipment, and wireless communications that enable safe and rapid deployment of appropriate resources to an emergency. Coordination between Emergency Management Subsystems supports emergency notification and coordinated response between agencies. Existing wide area wireless communications would be utilized between the Emergency Management Subsystem and an Emergency Vehicle to enable an incident command system to be established and supported at the emergency location. The Emergency Management Subsystem would include hardware and software for tracking the emergency vehicles. Public safety, traffic management, and many other allied agencies may each participate in the coordinated response managed by this package.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
31 / 64 June 24, 2003
EM1 - Emergency Response
EmergencyManagement
Emergency Call-Tracking
EmergencyVehicle
On-board EV Incident Management
Communication
incident status
Emergency Response Management
emergency dispatch requests
Other EMincidentreport
TrafficManagement
resource request +remote surveillance control
current network conditions +resource deployment status
WeatherServices weather
information
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • CAD 911 / State Patrol AVL System • Highway Helper AVL System • Mayday System
Emergency Routing (EM2)
This market package supports dynamic routing of emergency vehicles and coordination with the Traffic Management Subsystem for special priority on the selected route(s). The Information Service Provider Subsystem supports routing for the emergency fleet based on real-time traffic conditions and the emergency routes assigned to other responding vehicles. In this market package, the Information Service Provider Subsystem would typically be integrated with the Emergency Management Subsystem in a public safety communications center. The Emergency Vehicle would also optionally be equipped with dedicated short range communications for local signal preemption.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
32 / 64 June 24, 2003
EM2 - Emergency Routing
EmergencyManagement
EmergencyVehicle
emergency vehicletracking data
emergency trafficcontrol request
TrafficManagement
signal control data
On-Board EVEn Route Supportsuggested route
local signalpreemption request
Roadway
Roadside Signal Priority
Emergency Dispatch
request for right-of-way
current network conditions +emergency traffic control response
Vehicle Location Determination
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • Signal Priority/Pre-emption Equipment
Mayday Support (EM3)
This package allows the user (driver or non-driver) to initiate a request for emergency assistance and enables the Emergency Management Subsystem to locate the user and determine the appropriate response. The Emergency Management Subsystem may be operated by the public sector or by a private sector provider. The request from the traveler needing assistance may be manually initiated or automated and linked to vehicle sensors. The data is sent to the Emergency Management subsystem using wide area wireless communications with voice as an option. Providing user location implies either a location technology within the user device or location determination within the communications infrastructure.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
33 / 64 June 24, 2003
EM3 - Mayday Support
EmergencyManagement
Mayday Support
Vehicle
Vehicle Mayday I/F
Personal Inform.Access
Personal Mayday I/F
Remote TravelerSupport
Remote Mayday I/F
Other EM
emergency notification
emergency acknowledge
emergency acknowledge
emergency notification
emergency notification
emergency acknowledge
incidentreport
Vehicle Location Determination
Personal Location Determination
Vehicle Safety Monitoring System
The above diagram is a generic representation of the implementation of this Market Package from The National ITS Architecture, CD ROM, Version 3.0. The diagram shows key Market Package elements. Some elements are omitted for clarity and not every organization will implement this market package as shown in the diagram. List of Systems Under this Market Package: • CAD 911 / State Patrol AVL • Mayday System
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
34 / 64 June 24, 2003
CHAPTER 4 – SYSTEM DESCRIPTIONS AND CONTACT RESOURCE LISTING
As noted previously in this report, there are a number of existing or planned “ITS Systems” that have been identified as being part of the overall Minnesota Guidestar ITS testing and deployment efforts. Some of these systems are solely under the management of Mn/DOT. Some involve partnerships with other public agencies or private vendors, while others are largely being managed by a non-Mn/DOT agency (i.e. local transit operators).
The following table (Table 4.1) has been prepared so that readers of this report may have a basic understanding of the nature of each ITS System listed and discussed throughout this report. Further, the table provides a reference source from which more detailed system or program information can be obtained.
Notes:
1. The Minnesota ITS Standards Migration Matrix presented in Section 5 shows the potentially applicable standards for each existing ITS System. However, these standards are only applicable in case the referenced system is updated (Major re-writes of software would then be necessary). The table below indicates any exceptions to this general note.
2. Video transmission standards are not considered in the matrix because the ITS Standards do not address them. Instead transmission standards established by the video industry must be used. ITS Standards only address and standardize on the command set to control the Pan, Tilt, and Zoom functionalities.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
35 / 64 June 24, 2003
Table 4.1 – System Description and Contact Resource Information
System Name Description Contact
Data Archive
TMC 30 second
Detector
Volume/Occupancy
A key data set maintained as part of the operation of the METRO RTMC. Custom written and allows access to detector data archives for study and planning purposes. Data is acquired from field detectors throughout freeway management system via the RTMC communications system.
This is a Transport Communication Protocol/ Internet Protocol (TCP/IP) over Ethernet connection.
The following system diagram shows which aspect this ITS System addresses (highlighted arrow):
Mn/DOT Metro District Traffic Management Center (TMC)
(612) 341-7500
www.dot.state.mn.us/tmc
Maureen Jensen
(651) 582-1341
TMC Incident Log Archive
A custom written archive of incident records maintained as part of the operation of the METRO area TMC.
This is part of the Traffic Incident Computer (TIC) and the data is saved in the ‘International Traveler
Mn/DOT Metro District Traffic Management Center (TMC)
(612) 341-7500
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
36 / 64 June 24, 2003
System Name Description Contact
Information Interchange Standard (ITIS)’ data format.
The following system diagram shows which aspect this ITS System addresses (highlighted arrow):
1HWZRUN6HUYHU
$ UFKLYH
&RPP� 6HUYHU�,5,�VHUYHU�
,5,6� * 8,�,QWHUIDF�WR
&RPP�6HUYHU�
&RQWUROOHU
5DPS�0 HWHUV
'HWHFWRU�6 WDWLRQVDQG�5 DPS�0 HWHUV
/DQH�&RQWURO6LJQDOV
' 0 6 �1 7&,3 �
) LEHURSWLFVWRFDELQHWPXOWLGURS
����9RO�2 FF�5DPS�$UFKLYH�
7&3�,3FRQQHFWLRQ
'DWD�' LVWULEXWLRQ6HUYHU�' ' 6�
570&�&RQWURO5RRP�0 DS
0HWUR�7UDIILF�0 JPW�: HESDJHV
7UDIILF�,QFLGHQW&RPSXWHU�7,&�
0 DQXDOO\HQWHUHG,QFLGHQW
' DWD�,7,6�
,QFLGHQW�$UFKLYH
7KH�7,&�FRPSRQHQW�FRXOG�EHUHSODFHG�E\ � RU�LQWHJUDWHG�LQWR�WKH&$56� V\ VWHP�LQ�WKH�IXWXUH
0 DS�&OLHQW
: HEVHUYHU
&RQWUROOHU
&RQWUROOHU
&RQWUROOHU ' 0 6 �1 7&,3 �
&RQWUROOHU
www.dot.state.mn.us/tmc
Maureen Jensen
(651) 582-1341
Automatic Traffic Recorder (ATR) System
Data collected and stored by a system of commercially supplied devices deployed at selected locations throughout the state to measure traffic volumes, occupancy, vehicle weight, speed, and vehicle classification for planning and reporting purposes.
Data is typically acquired automatically from field devices over phone lines and stored in a central computer.
The Mn/DOT Office of Transportation Data Analysis (OTDA) collects traffic data, namely: volume, occupancy, vehicle weight, speed, and vehicle classification. The Office also analyzes the data for quality before making it available to end-users. The data from some of the TMC detector locations and other sources are used by the office to extract Peak hour volumes, Average Daily Traffic (ADT), and Annual Average Daily Traffic (AADT).
The OTDA also has another new project that seeks to implement a location data server, which is intended to utilize a stable linear datum to replace the route naming and numbering methods used today. It will include ramps, loops, collectors, distributors, and other transportation segments that currently are not part of the
Mn/DOT Office of Transportation Data & Analysis
Jonnette Kriedeweis
(651) 215-1854
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
37 / 64 June 24, 2003
System Name Description Contact
routes in today's applications. The new location data server will also add both history capability and the ability to store proposed routes.
The ATR data is compiled from several sources. The University of Minnesota Duluth has provided integration of the several sources into a single accessible database. The database is not directly shared electronically, in general, but rather ODTA uses the database to answer data requests and provide reports to others.
The following diagram shows these relationships:
Transit Management:
Transit Scheduling System (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink Transit, Metro Mobility, Dakota Area Resources and Transportation for Seniors [DARTS] etc.)
computerized or manual scheduling systems (typically proprietary) for both scheduled transit operators and demand responsive transit systems.
Metro Transit – uses TRAPEZE DOS version, but this will be replaced, possibly by HASTUS software or newer version of Trapeze. It includes a garage operations component assigning a bus to a driver and interface to Siemens’ Automatic Vehicle Location/Computer-Aided Dispatching (AVL/CAD) system. A request for proposals (RFP) to upgrade the software contains some high-level TCIP requirements.
Duluth Transit Authority – uses TrapLite from Trapeze for paratransit (currently experiencing problems with the software). Uses HASTUS software (GIRO Inc) for fixed route (software works very well). It allows users to configure driver hours and assignments.
Others transit properties use either some form of Trapeze software or perform the scheduling manually by hand.
System specific information on ITS applications may be obtained by contacting the individual system operators, or the
Mn/DOT - Michelle Gutzmann (651) 282-9950 [email protected]
Metro Transit- Gary Nyberg (612) 349-7303
www.metrocouncil.org/transit/index.htm
Southwest Transit - John Krangness (952) 974-3107
www.swtransit.org
Mn Valley Transit: (952) 882-6000
www.metrocouncil.org/transit
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
38 / 64 June 24, 2003
System Name Description Contact
Plymouth Metrolink: Paul Buharin (612) 378-7833
Www2.ci.plymouth.mn.us/
Metro Mobility: (651) 602-1111
www.metrocouncil.org/transit
DARTS: (651) 455-1560
www.darts1.org.
Information for selected systems (i.e. DARTS) involved with testing ITS elements can also be found under “ITS Projects” at www.dot.state.mn.us/guidestar/
Transit Driver Assignment (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink Transit, Metro Mobility, DARTS etc.)
Computerized or manual driver assignment systems that typically come as proprietary packages depending on the type and size of a bus transit operation (i.e. Metro w/ 950 buses or DART w/ 25 vehicles).
Metro Transit – currently uses software by Siemens, however, this may change to HASTUS software later.
Duluth Transit – uses HASTUS software.
Other transit properties – assignments done manually
See contact information in box above.
Transit Dispatch (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink Transit, Metro Mobility, DARTS, etc.)
Computerized or manual systems to assist transit dispatch operators. These systems typically come as proprietary packages depending on the type and size of a bus transit operation.
Metro Transit – uses Siemens TransitMaster software
Other transit properties – do not use computerized dispatching at this time.
See contact information in box above.
Transit Automatic Vehicle Location (AVL) System (Metro Transit, DARTS [planned], Duluth Transit [planned], etc.)
AVL systems, typically using GPS technology, specifically designed for tracking the location of buses. Systems are typically purchased as proprietary packages.
Metro Transit – uses Siemens TransitMaster software. Also uses GPS over four analog channels of an 800 MHz radio system.
Duluth Transit – uses Siemens TransitMaster software
Other transit properties – do not use AVL
Contact information.
Duluth Transit
Dennis Jensen (218) 722-4426
Transit Passenger Counters
On-board transit vehicle technology used for route planning that automatically records the entries and exits at each bus stop.
Metro Transit – uses RedPine devices for passenger counting
Duluth Transit – uses RedPine devices for passenger counting
For Metro Transit information see the Metropolitan Council web site at www.metrocouncil.org/transit/index.htm
Gary Nyberg (612) 349-7303
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
39 / 64 June 24, 2003
System Name Description Contact
Other transit properties – use either manual counting and/or estimate passenger counts based upon trip manifests or trips scheduled in Trapeze software
Transit Vehicle Video Cameras
On-board video cameras that provide security for the driver and passengers.
Metro Transit – currently uses analog video cameras, but is investigating a move to digital with wireless transmission.
Duluth Transit – uses analog cameras on board which record images that are later retrieved.
Other transit properties – currently do not deploy this technology.
For Metro Transit information see the Metropolitan Council web site at
www.metrocouncil.org/transit/index.htm
Gary Nyberg (612) 349-7303
Video Surveillance:
Metro Park and Ride Surveillance Cameras
This project utilizes new web-based and video technologies for surveillance at park and ride lots. Autoscope cameras will be utilized for the surveillance and the video will be brought to a central location via wireless, satellite, or fiber optic communications media.
Mn/DOT OTSO
Ben Osemenam (651) 297-5651
Metro Transit
Fritz Coulter (612) 349-7251
George Serumgard (612) 349-7697
Freeway and
Arterial Video Surveillance System (St. Paul, MPLS, Hennepin County, TH 55, ICTM, etc.)
Freeway and arterial deployments of Closed Circuit Television (CCTV) cameras typically viewed and operated from a TMC.
The center to field connection for Camera control is via RS-232 through a communications system (currently this communications system is a Sonet fiber system). In addition, there is a keyboard and a switcher controller (server) that has a RS-232 connection to a Video switcher.
City of Minneapolis DPW-Traffic Div
Scott Tachney (612) 673-2646 [email protected]
www.ci.minneapolis.mn.us/
City of St. Paul
John Maczko (651) 266-6137
www.ci.stpaul.mn.us
Hennepin County DOT
Jerry Smrcha (763) 673-7740
www.co.hennepin.mn.us
Mn/DOT Metro TMC
Nick Thompson (651) 634-7269
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
40 / 64 June 24, 2003
System Name Description Contact
www.dot.state.mn.us/tmc/
RWIS Video Surveillance System
The video part of a system of weather and pavement condition sensors strategically located throughout the state to collect and automatically report weather and pavement condition information in support of maintenance services. A University researcher in Duluth is perfecting use of this video to quantify visibility conditions. RWIS field sites are now also known as Environmental Sensor Systems (ESS).
Mn/DOT- Duluth District Office (218) 723-4960
AXIS Server – Snapshot
Collects Video snapshots from the freeway surveillance cameras and sends them to Metro Traffic Web Pages system.
Assumption: The digital camera system operates over a wireline TCP/IP network. TCP/IP network.
Mn/DOT OTSO
Nick Thompson (651) 634-7269
www.dot.state.mn.us
Portable Traffic Management System (PTMS) Video Surveillance Component
The video surveillance component of Portable Traffic Management Systems that can also employ detectors, processors, signs, etc. PTMS’s are typically used in work zones.
The digital camera system operates over a wireless TCP/IP network.
Mn/DOT Metro Traffic
Nick Thompson (651) 634-7269
www.dot.state.mn.us/tmc/
Signal Priority
Transit Bus Priority system (Metro Transit, St. Cloud, etc.)
Systems (typically proprietary) with a combination of on-board bus and on-street signal controller add-ons that allow buses to get preferential green time, but not pre-emption as for fire and police.
If preemption/priority systems are used, they deploy the data-less 3M Opticom system (contact closure activation based on receiving stroboscope light at intersection – line of sight necessary).
See box above for Mn/DOT and Metro Transit contact information.
Mn/DOT Thomas Dumont
(320) 654-5105
For St. Cloud Transit information
St. Cloud MTC
Tom Cruishank
(320) 539-4483
www.stcloudmtc.com
Traffic Signal Priority/Pre-Emption
Systems (typically proprietary) with a combination of on-board equipment in police or fire vehicles as well as on-street signal system detector and controller apparatus that allow these vehicles to always get a green signal display.
If preemption/priority systems are used, they deploy the data-less 3M Opticom system (contact closure activation based on receiving stroboscope light at intersection – line of sight necessary). Some intersections use a sonic-based system (SonicEVP).
For local units of government, contact the Traffic Engineering unit of jurisdictions employing this technology.
For the Mn/DOT Central Office, contact:
Mn/DOT Office of Traffic Engineering, Security and Operations
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
41 / 64 June 24, 2003
System Name Description Contact
(651) 284-3500
Traveler Information
TMC Data Distribution Server
The DDS is a Mn/DOT custom designed real time data distribution system used at the Metro TMC and from which data is shared with others.
The following system diagram shows which aspect this ITS System addresses (highlighted box):
See Mn/DOT Metro District T
Nick Thompson (651) 634-7269
KBEM A Twin Cities FM station broadcasting at 88.5 MHZ owned by others (Minneapolis Public Schools) but which carries regular traffic reports originating from the MNDOT Metro TMC daily.
Mn/DOT Metro District Traffic Management Center (TMC)
(612) 341-7500
www.dot.state.mn.us/tmc/
Maureen Jensen
(651) 582-1341
Metro Transit Telephony System
Provides personalized trip planning phone assistance to Metro Transit customers.
Metro Transit – uses schedule information provided by the Trapeze software. Addition of other real-time information is currently being investigated.
For Metro Transit information see the Metropolitan Council web site at www.metrocouncil.org/transit/index.htm
Gary Nyberg (612) 349-7303
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
42 / 64 June 24, 2003
System Name Description Contact
Other transit properties – currently do not deploy this technology Other transit properties – currently do not deploy this technology
Scenic Byways Kiosk System A test project that allows travelers stopping at a rest area to use a live computer based kiosk to access
traveler and tourist information via phone and satellite communications.
Mn/DOT Office of Traffic, Security and Operations
Ben Osemenam (651) 297-5651 [email protected]
Rob Williams
(651) 282-2169
511 This is MNDOT’s multi-faceted and multi-phased implementation of the FCC’s July 2000 designation of the national “511” calling number for Traveler Information.
The 511 system receives/obtains XML data from the CARS system and provides VOICE XML data to the BeVocal application.
The following system diagram shows the logical system diagram for this ITS System as well as the applicable component (highlighted):
Mn/DOT Office of Traffic Engineering, Security and Operations
Ginny Crowson
MNDOT Guidestar Program Manager
(651) 284-3454
Also see “ITS Projects” at
www.dot.state.mn.us/guidestar/
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
43 / 64 June 24, 2003
System Name Description Contact
&$56 VHUYHU+RVWHG�E\ � &DVWOH�5RFN�& RQVXOWDQWV�DW�%HOO6RXWK�IDFLOLW\ � LQ�$OWDQWD�
* $
&$56 8VHU�' DWD�����R�XVHUV
70&�' ' 6/RRS�GHWHFWRU�GDWD�Z�* HRORFDWLRQ
SURYLGHG�E\ � 70 &
FRQQHFWHGYLD,QWH
UQHW
; 0 /
0 ' $ 5 6 VHUYHU+RVWHG�E\ � & DVWOH�5RFN�&RQVXOWDQWV�RSHUDWLRQDO�WHVW
0 ' $ 5 6 8VHU�' DWD����YHK�RSHUDWRU�XVHUV
1RWH�& $56�SHUIRUPVPDSSLQJ� RI�/ DW�/ RQJ � LQIRWR�0 LOHSRVW�GDWD
+RVWHG�E\ � &DVWOH�5RFN�&RQVXOWDQWV�DW�%H9RFDO�IDFLOLW\ � LQ6XQQ\YDOH�&$
0HGLGLDQ( QYLURQPHQWDO
: HDWKHU
3URYLGHV�ZHDWKHUIRUHFDVWV�XVLQJ�5: ,6 �12$$�HWF�GDWD
&DEOH�$FFHVV 7HUPLQDWHG�LQ�) HE
7ULS86$�RUJ &DVWOH�5RFN�V\ VWHP
0DS�&OLHQW+RVWHG�DW�12 &RQ�: LQ�VHUYHU
/RDG%DODQFHU
���RUJEDVHG�RQ�& DVWOH�5RFNV7ULS86$�VRIWZDUH
) LOH&KHFNHU�DQG: HDWKHU&KHFNHU
+RVWHG�DW�,QWHUWHFK�RQ�8QL[6HUYHU
) LOH&KHFNHU�DQG: HDWKHU&KHFNHU
+RVWHG�DW�,QWHUWHFK�RQ�8QL[6HUYHU
8 5 / � WR�&RQJHVWLRQ0DS�LQ�70 &
1: 6� : HDWKHU
&RQQHFWHGYLD�,QWHUQHW�7H[W 1RWH�VHULHV�RI�* ,) � LP DJHV
Orion Parking Garage Monitors
The Orion project was a multi-year, multi-faceted, ITS technical and institutional integration project for the Twin Cities area. Parking Garage Monitors were a planned component to provide freeway traffic information to travelers returning to their cars.
The system also uses fixed CCTV in the garages.
This is a TCP/IP connection using an early version of DATEX as the application profile protocol.
Upgrades are planned for this ITS System including the utilization of data provided by the CARS system to develop customized webpages (high level traveler information).
Mn/DOT Office of Traffic Engineering, Security and Operations Ray Starr (651) 284-3434 [email protected]
Also see “ITS Projects” at
www.dot.state.mn.us/guidestar
Transit Schedule Web Pages
Trip planning schedule information posted on the Metro Web site.
Metro Transit – uses Trapeze software
Duluth Transit – will be implementing Siemens Webwatch system in Summer 2003
Other transit properties – currently do not deploy this technology
For Metro Transit information see the Metropolitan Council web site at www.metrocouncil.org/transit/index.htm
(612) 349-7400
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
44 / 64 June 24, 2003
System Name Description Contact
Transit Trip Planner
A web based system that allows potential riders to self plan transit trips. This system is currently only applicable to fixed route trip planning.
Metro Transit – uses ManTech (now Trapeze) software
Other transit properties – currently do not deploy this technology
For Metro Transit information see the Metropolitan Council web site at www.metrocouncil.org/transit/index.htm
(612) 349-7400
Metro Traffic Management Web Pages
A web based system run by Mn/DOT out of the Metro TMC that shares with the public, in real time, traffic and travel condition information, including a real time traffic flow map.
It also provides camera snapshots .
The following system diagram shows which aspect this ITS System addresses (highlighted arrow):
For Metro Transit information see the Metropolitan Council web site at
www.dot.state.mn.us/tmc/trafficinfo/map/refreshmap.html
Contact: Nick Thompson
(612) 341-7269
nick. [email protected]
511 Web Pages This is one aspect of Mn/DOT’s multi-faceted and multi-phased implementation of the FCC’s July 2000 designation of the national “511” calling number for Traveler Information.
This system generates traveler information to web pages using data provided by the CARS system.
The following system diagram shows the logical 511 system diagram for this ITS System as well as the applicable component (highlighted):
Mn/DOT Office of Traffic Engineering, Security and Operations
Ginny Crowson (651) 284-3454
Also see “ITS Projects” at
www.dot.state.mn.us/guidestar/
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
45 / 64 June 24, 2003
System Name Description Contact
&$56 VHUYHU+RVWHG�E\ � &DVWOH�5RFN�&RQVXOWDQWV�DW�%HOO6RXWK�IDFLOLW\ � LQ�$OWDQWD�
* $
&$56 8VHU�' DWD�����R�XVHUV
5 7 0 & �' ' 6/RRS�GHWHFWRU�GDWD�Z�* HRORFDWLRQ�
&RQJHVWLRQ�,QFLGHQW�GDWD
FRQQHFWHGYLD,QWHUQH
W
; 0 /
0 ' $ 5 6 VHUYHU+RVWHG�E\ � &DVWOH�5RFN�&RQVXOWDQWV�RSHUDWLRQDO�WHVW
0 ' $ 5 6 8VHU�' DWD����YHK�RSHUDWRU�XVHUV
1RWH�&$56�SHUIRUP VPDSSLQJ�RI�/ DW�/ RQJ�LQIRWR�0LOHSRVW�GDWD
+RVWHG�E\ � &DVWOH�5RFN�&RQVXOWDQWV�DW�%H9RFDO�IDFLOLW\ � LQ6XQQ\YDOH�&$
0HGLGLDQ(QYLURQPHQWDO
: HDWKHU
3URYLGHV�ZHDWKHUIRUHFDVWV�XVLQJ�5: ,6�12$$�HWF�GDWD
&DEOH�$ FFHVV 7HUPLQDWHG�LQ�) HE
7 ULS86$� RUJ &DVWOH�5RFN�V\ VWHP
0DS�&OLHQW+RVWHG�DW�12&RQ�: LQ�VHUYHU
/RDG%DODQFHU
���RUJEDVHG�RQ�&DVWOH�5RFNV7ULS86$�VRIWZDUH
) LOH&KHFNHU�DQG: HDWKHU&KHFNHU
+RVWHG�DW�,QWHUWHFK�RQ�8QL[6HUYHU
) LOH&KHFNHU�DQG: HDWKHU&KHFNHU
+RVWHG�DW�,QWHUWHFK�RQ�8QL[6HUYHU
8 5 / � WR�&RQJHVWLRQ0 DS�LQ�70 &
1 : 6�: HDWKHU
&RQQHFWHGYLD�,QWHUQHW�7H[W 1RWH�VHULHV�RI�* ,) � LPDJ HV
St. Paul Advance Parking Information System (APIS)
An ITS Operational Field Test Project that was continued by the City of St. Paul that provides garage specific parking availability info in the CBD.
Information is displayed via a sign.
Center-to-center communications between the garages and the central office uses leased phone lines (T1-lines). Center-to-field communication to the signs now uses agency -owned twisted pair cabling.
The system does not archive any data.
Mn/DOT Office of Traffic, Security, and Operations
Ben Osemenam (651) 297-5651
Also see “ITS Projects” at
www.dot.state.mn.us/guidestar/
City of St. Paul
Bob Hamilton (651) 266-6208
Minneapolis Parking Management System
Management system for occupancy, usage and revenue control of City owned ramp and surface parking spaces in CBD.
DMS are controlled locally from the parking garage. Security CCTV with Pan, Tilt, and Zoom (PTZ) are controlled and images are transmitted to the central location.
City of Minneapolis DPW-Traffic Div
(612) 637-2411
www.ci.minneapolis.mn.us
Scott Wellan (612) 637-2411
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
46 / 64 June 24, 2003
System Name Description Contact
CVISN
Commercial Vehicle Information Systems and Networks (CVISN)
Mn/DOT initiatives as part of national CVISN program to improve trucking efficiency and safety through the use of standardized electronic communications.
MNDOT
Pierre Carpenter (651) 4052-6195
Pierre. [email protected]
Also see “ITS Projects” at www.dot.state.mn.us/guidestar/
Traffic Signals
Closed Loop Signal Controllers & Detectors
Closed Loop Systems employee an On-Street Master Controller that typically communicates full time by wire line using FSK to a string of local intersection controllers and then communicate by dial-up phone lines to a TMC or other location on an as needed basis only. Controllers are mostly ECONOLITE and TRACONET.
City of St. Paul uses the DMJM (company now part of Econolite Products) TCS2 central system with time-based coordination and Model 170 controllers.
For local units of government, contact the Traffic Engineering unit of jurisdictions employing this technology.
For Mn/DOT Metro Office
Steve Misgen (651) 634-2130
Mn/DOT Office of Traffic, Security, and Operations
Ray Starr (651) 284-3434
Centralized Traffic Signal Systems & Detectors (St. Paul, MPLS, & Icons)
Traffic signals that are coordinated and managed from one or more computers located at a central city location.
A central signal control system (Icons) controls several intersection controllers (Econolite).
City of Minneapolis uses FORTRAN T2000C and a SCOOT back -end. Minneapolis uses NEMA controllers (Eagle).
St. Paul is 2/3rds under central control (Econolite-DMJM software called TCS 2, which is no longer supported and will ultimately be replaced. The other 1/3rd is controlled by closed loop systems. St. Paul uses 170 controllers,
The Icons system, City of Minneapolis, and City of St. Paul use RS232 with modem or FSK for center to field communications.
City of Minneapolis DPW-Traffic Div
Scott Tacheny (612) 673-2646
www.ci.minneapolis.mn.us
City of St. Paul
Bob Hamilton (651) 266-6176
www.ci.stpaul.mn.us/
For the ICTM project contact:
Mn/DOT Metro TMC
Linda Taylor (612) 634-2126
www.dot.state.mn.us/tmc/
Isolated Signal Controllers & Detectors
Stand-alone intersection signal controller and detector installations.
For local units of government, contact the Traffic Engineering unit of jurisdictions employing this technology.
Also
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
47 / 64 June 24, 2003
System Name Description Contact
Mn/DOT Office of Traffic, Security and Operations
Ray Star (651) 284-3434
Lane Control Signals
Signal indications having a down arrow or X, mounted over specific freeway lanes to indicate whether the lane is open or closed.
Center to Field communication is via RS-232 or FSK modem.
Mn/DOT Metro District Traffic Management Center (TMC)
(612) 341-7500
www.dot.state.mn.us/tmc/
Maureen Jensen (651) 582-1341
Ramp Metering
Ramp Meters and Detector Stations
Controllers and associated equipment, very similar to signal system equipment controller HW & SW but in this use located on freeway entrance ramps in congested urban areas.
Mn/DOT Metro District Traffic Management Center (TMC)
(612) 341-7500
www.dot.state.mn.us/tmc/
Maureen Jensen (651) 582-1341
Data Collection and Monitoring
TH 55 Automatic Vehicle Identification (AVI) System (License plate readers)
This ITS System utilizes infrared video cameras that read and encode license plate numbers and match them at multiple locations along highway 55 to measure travel time. This system is currently not active and will likely not be expanded to other sites.
Both Center to Center and Center to Field communications is over a TCP/IP network.
Mn/DOT Office of Traffic Engineering, Security and Operations
Ray Starr (651) 284-3434
Mn/DOT Metro Traffic
Steve Misgen (651) 634-2130
Condition Acquisition and Reporting System (CARS) and Maintenance Driver Automated Recording System (MDARS)
MN/CARS is the Minnesota-specific implementation of a multi-state developed system for acquiring real time roadway info through an This ITS system provides for the data entry point of the Mn/DOT traveler information system. This system allows remote data entry from within vehicles using web-enabled cellular phones.
The following system diagram shows the logical CARS system diagram for this ITS System as well as the
Mn/DOT Office of Traffic, Security and Operations
Ginny Crowson (651) 284-3454
Mn/DOT Metro District Traff ic Management Center (TMC)
(612) 341-7500
www.dot.state.mn.us/tmc/
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
48 / 64 June 24, 2003
System Name Description Contact
applicable component (highlighted):
Traffic Management
Virtual Transportation Operation Center (VTOC) Software
Software that monitors and controls video cameras and variable message signs over a wireless and/or wireline TCP/IP network. It is being deployed in selected TOCC’s.
Operation between centers is not true center-to-center communication, but clients connecting into a remote system. However, an interface into the CARS system might be added in the future.
VTOC cameras are made by PELCO,
Currently non-NTCIP compatible VMS (by ADCO) are controlled by the VTOC software, but it can also control NTCIP-compatible signs (such as LedStar signs).
Other devices include Autoscope cameras.
Non-intrusive infrared Ice Detection systems, the I-90 Gate Control system, Overheight Detection systems, and Flood Detection and Warning systems may be integrated in the future.
Mn/DOT Office of Traffic, Security and Operations Tom Peters (651) 282-2469 [email protected]
Also see “ITS Projects” at
www.dot.state.mn.us/guidestar/
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
49 / 64 June 24, 2003
System Name Description Contact
Integrated Corridor Traffic Management (ICTM)
A field test project on I-494 and adjacent arterials near Mall of America that has continued to operate. This system involves the integration of freeway and arterial traffic control/ITS applications from a number of agencies and vendor partners. It helps divert traffic around freeway incidents onto arterial streets and back onto the freeway in an organized fashion using controlled signal timing and a motorist information system. The ICTM uses signal controllers and ramp meters (both SCATS controlled. Note: ICTM is being reduced in scope. Additionally, the SCATS system is currently being replaced with an Econolite Closed Loop System), CCTV cameras for surveillance, and older versions of DMS.
This is a simple shared system rather than multiple systems with center-to-center connection.
It has a center-to-field connection and uses RS-232/FSK.
The scope of this project is being reduced.
Mn/DOT - Metro Division, Waters Edge Linda K. Taylor (651) 582-1461 [email protected]
High Occupancy Vehicle (HOV) Lane Gate System
A locally, manually operated system for controlling the gates on the Metro area I-394 reversible HOV lane deployment that uses traffic detectors and controllers.
There is another ramp meter HOV bypass located at Snelling Ave/I-94 that uses a ramp metering controller.
Mn/DOT Metro District Traffic Management Center (TMC)
(612) 341-7500
www.dot.state.mn.us/tmc/
Maureen Jensen (651) 582-1341
HOV Lane Open/Closed Sign System
A semi-automated system for controlling the open/closed signs on the Metro area I-394 reversible HOV lane deployment. Currently locally, manually operated.
Mn/DOT Metro District Traffic Management Center (TMC)
(612) 341-7500
www.dot.state.mn.us/tmc/
Maureen Jensen (651) 582-1341
Dynamic Message Signs
PTMS Dynamic Message Sign Component
The sign component of Portable Traffic Management Systems that can also employ video surveillance, detectors, etc.
PTMS’s are typically used in work zones.
This is an ADCO system that uses wireless TCP/IP.
For Twin Cities applications see Mn/DOT METRO TMC contact information in box above.
For greater Minnesota applications contact applicable Mn/DOT District Traffic Engineering office.
Freeway and Arterial Dynamic Message Signs
Variable Message Signs controlled from the Metro TMC or from a TOCC.
ORION (TH55) and TOCCs center-to-field communication is TCP/IP.
For Freeway DMS, center-to-field communication is RS -232 or FSK modem with no routing capability.
See contact for VTOC as well as for the TMC.
Incident Management
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
50 / 64 June 24, 2003
System Name Description Contact
CAD 911 / State Patrol AVL
A computer assisted State Patrol system for handling cellular 911 calls and for determining the position of State Police vehicles.
Minnesota State Patrol
Captain Craig Hendrickson (651) 215-1768
www.dps.state.mn.us/patrol/
Minnesota -State Patrol
Captain Craig Hendrickson (651) 215-1768
www.dps.state.mn.us/patrol/
Highway Helper AVL System
An Automatic Vehicle Location System installed on MNDOT’s Metro area Highway Helper Service Patrol vehicle fleet to facilitate Highway Helpers’ operations.
Currently, a Ball system is used, but will be replaced by a Siemens’ TransitMaster (CAD/AVL) software.
Mn/DOT Metro Traffic
Nick Thompson (651) 634-7269
www.dot.state.mn.us/tmc/
Maureen Jensen (651) 582-1341
I-90 Gate Control System (Existing and planned)
A system using permanently installed mainline and on-ramp gates to manually and remotely shut off access to Interstate segments during severe weather events or major incidents.
Developed by ThomTech. Software control by Saturn Systems.
900 MHz spread spectrum communications to the gates.
Not currently part of the VTOC software.
Uses Autoscope CCTV to detect violators and can bring back slow scan camera images.
Mn/DOT Office of Traffic, Security, and Operations
Farideh Amiri (651) 296-8602
Also see “ITS Projects” at
www.dot.state.mn.us/guidestar/
HRI
Highway Railroad Intersection System (Existing and Planned)
In cooperation with private partners and a RR in West Central MN, Mn/DOT has a multi-phase test project underway to deploy low cost, dynamic RR Xing displays using GPS train location and wireless communications.
Mn/DOT Office of Traffic Engineering, Security and Operations Daryl Taavola (651) 282-2115 [email protected]
Train Detectors Various detection technologies (i.e. Radar) preferably deployed separate from the train and track infrastructures. MNDOT has a test project called the “Moorhead Area Integrated Train Detection and Traffic Control System”.
Mn/DOT Office of Traffic Engineering, Security and Operations
Farideh Amiri (651) 296-8602
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
51 / 64 June 24, 2003
System Name Description Contact
Environmental Monitoring
Mn/DOT Statewide Road Weather Information System (RWIS)
A system of weather and pavement condition sensors strategically located throughout the state to collect and report weather and pavement condition information in support of maintenance services.
This system already implements ITS Standards and has been tested by the FHWA’s Testing Team (Battelle).
Mn/DOT- Duluth District Office Curt Pape (218) 723-4960 Ext. 3540 [email protected]
Automatic Weather Observing Systems (AWOS)
This is a system of 50+ automated weather-reporting stations deployed by the Mn/DOT Office of Aeronautics. Stations are accessible by aircraft radio or phone.
Mn/DOT Office of Aeronautics
Robert Milton (651) 296-1600
www.dot.state.mn.us/aero
SAIL
Safety Automatic Intelligent Locator (SAIL) Maintenance AVL System (Existing and future planned expansion)
This system is a multi-phase test deployment of AVL on a wide array of Metro District vehicles to determine the benefits of AVL in the conduct of maintenance and data collection activities.
Mn/DOT Office of Traffic Engineering, Security, and Operations
John Scharffbillig (651) 215-0402
Also see “ITS Projects” at www.dot.state.mn.us/guidestar/
Vehicle Sensor
Intelligent
Initiative (IVI)
(TH 7, TH 19,
A multi-phase, multi-corridor test deployment of snowplows, ambulances and State Patrol cars equipped with a variety of enhanced ITS collision avoidance and guidance technologies
Mn/DOT Office of Traffic Engineering and ITS
Brad Estochen (651) 296-2984
John Scharffbillig (651) 215-0402
Also see “ITS Projects” at www.dot.state.mn.us/guidestar/
Mayday/Site Surveillance
Mayday System This system is a multi-phased vehicle test deployment in southeastern Minnesota in cooperation with the Mayo Clinic and others to determine the costs, benefits, role of standards, etc. in the automatic reporting of crashes, their location, severity, etc.
Mn/DOT Office of Traffic Engineering, Security and Operations
Brad Estochen (651) 296-2984
Also see “ITS Projects” at www.dot.state.mn.us/guidestar/
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
52 / 64 June 24, 2003
CHAPTER 5 – MINNESOTA ITS STANDARD MIGRATION MATRIX
A very important and illustrative element of this ITS Candidate Systems, Standards and Products Report is the establishment of a relationship between the applicable national ITS Standards and the many ITS Systems implemented or planned in Minnesota. This relationship is shown in form of a matrix. The cells of the matrix shows different designations indicating whether and in what form a particular standard is applicable to a particular Minnesota ITS System. These designations are:
M = Must have. This standard must be implemented if the ITS System is intended to be compliant with ITS Standards.
Cx = Choice of Must Haves. For the indicated ITS System to be compliant, the system must utilize one of the standards.
P = Possible. This standard may or may not be appropriate depending upon how the system is implemented.
Blank = Not applicable for the indicated ITS System.
Also indicated is the “Minnesota Current Approach” (i.e. a Custom application, a Proprietary application, etc.).
The status ITS Standards (i.e., Under Development, in Ballot Stage, a Published Standard, etc.) may be found on the FHWA webpage at
<http://www.its-standards.net>
For this ITS Candidate Systems, Standards and Products Report, the ITS Standard Migration Matrix is being presented as a separate Excel file. The status of a particular standard may be one of the following:
Published standard - Standard which has been published and is available for purchase.
Approved standard - Standard has been approved, and is in the publishing process
Standard in ballot - The draft standard is in the approval process of the sponsoring Standards Development Organizations.
Standards under development - Standards are in the development phase under the direction of a technical working group.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
53 / 64 June 24, 2003
CHAPTER 6 –PRODUCT AVAILABILITY FOR MINNESOTA ITS SYSTEMS
This Chapter identifies the availability of products that conform to published ITS Standards, which are applicable to the various Minnesota ITS Systems. The level of conformance of products claiming conformance to particular ITS Standards were not investigated or verified. Table 6.1 is based on information provided by manufacturers and vendors via direct inquiries as part of this project, and the authors’ awareness of the availability of certain products. The purpose of this table is to help identify where the opportunity to migrate to ITS standards may exist or may evolve in the near future. The “Product Search Priority” rankings and “Comments” were developed by Mn/DOT and project stakeholders to help focus the research effort on product availability and do not infer any ranking of ITS Systems in Minnesota. Products that use particular ITS standards may be hardware or software products.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
54 / 64 June 24, 2003
Table 6.1 – Product Availability
System Name: Product Search Priority:
Comments: Product Availability
Data Archive:
TMC 30 second Detector Volume/ Occupancy Archive
L - Custom Written As of June 2003, no products conforming with applicable standards are available.
TMC Incident Log Archive
L - Custom Written
- Log of information coming out of the TIC
As of June 2003, no products conforming with applicable standards are available.
Automatic Traffic Recorder (ATR) System M - Commercial Off The Shelf Software (COTS)
- Maybe custom
- Not shared in real time
Checked with 2 vendors (Peek Global and IRD) but no products available since ‘Data Collection and Monitoring’ standard is not finalized.
Transit Management:
Transit Scheduling (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink Transit, Metro Mobility, Dakota Area Resources and Transportation for Seniors [DARTS] etc.)
M/H Lots of data sharing between the Transit systems required
- Maybe not able to upgrade soon
- Not likely to be available products?
- Talk with Metro Transit
Checked with FTA, APTA, and manufacturers (during March 2003 TCIP workshop) – no known products available . However, certain TCIP data elements are currently being implemented. Minneapolis Metro Transit and Columbus Transportation Authority (COTA) will be pilot projects for TCIP II pilot project implementations.
Transit Driver Assignment (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink Transit, Metro Mobility, DARTS etc.)
M/H - Lots of data sharing between the Transit systems required
- Maybe not able to upgrade soon
- Not likely to be available products?
- Talk with Metro Transit
Checked with FTA, APTA, and manufacturers (during March 2003 TCIP workshop) – no known products available . However, certain TCIP data elements are currently being implemented. Minneapolis Metro Transit and Columbus Transportation Authority (COTA) will be pilot projects for TCIP II pilot project implementations.
Transit Dispatch (Metro Transit, Southwest Transit, MN Valley Transit, Plymouth Metrolink Transit, Metro Mobility, DARTS etc.)
M/H - Lots of data sharing between the Transit systems required
- Maybe not able to upgrade soon (brand new system existing at Metro Transit)
- Not likely to be available products?
- Talk with Metro Transit
Checked with FTA, APTA, and manufacturers (during March 2003 TCIP workshop) – no known products available . However, certain TCIP data elements are currently being implemented. Minneapolis Metro Transit and Columbus Transportation Authority (COTA) will be pilot projects for TCIP II pilot project implementations.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
55 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
Transit Automatic Vehicle Location (AVL) System (Metro Transit, DARTS [planned], Duluth Transit [planned], etc.)
M/H - Lots of data sharing between the Transit systems required
- Maybe not able to upgrade soon (brand new system existing at Metro Transit)
- Not likely to be available products?
- Talk with Metro Transit
Checked with FTA, APTA, and manufacturers (during March 2003 TCIP workshop) – no known products available . However, certain TCIP data elements are currently being implemented. Minneapolis Metro Transit and Columbus Transportation Authority (COTA) will be pilot projects for TCIP II pilot project implementations.
Transit Passenger Counters L - Not much impacted by standards
- Data not widely shared
Checked with FTA, APTA, and manufacturers (during March 2003 TCIP workshop) – no known products available . However, certain TCIP data elements are currently being implemented. Minneapolis Metro Transit and Columbus Transportation Authority (COTA) will be pilot projects for TCIP II pilot project implementations.
Transit Vehicle Video Cameras
L - Not much impacted by standards
- Data not widely shared
As of June 2003, no products conforming with applicable standards are available.
Video Surveillance:
Metro Park & Ride Surveillance Cameras L - Likelihood of implementation unknown
- Not much impacted by standards
- Standards maturity questionable
Cohu and Vicon have presented CCTV controls claiming conformance to NTCIP 1205 at the 2003 ITS America Annual meeting. Both companies deployed the services of another company to develop a ‘translator’ inside a blackbox device that is installed in the field. It translates the vendors proprietary protocol into NTCIP PTZ commands.
Freeway and Arterial Video Surveillance Systems (St. Paul, MPLS, Hennepin County, TH 55, ICTM, etc.)
M - Standards maturity questionable Cohu and Vicon have presented CCTV controls claiming conformance to NTCIP 1205 at the 2003 ITS America Annual meeting. Both companies deployed the services of another company to develop a ‘translator’ inside a blackbox device that is installed in the field. It translates the vendors proprietary protocol into NTCIP PTZ commands.
RWIS Video Surveillance System L Not much impacted by standards since no camera control involved
Cohu and Vicon have presented CCTV controls claiming conformance to NTCIP 1205 at the 2003 ITS America Annual meeting. Both companies deployed the services of another company to develop a ‘translator’ inside a blackbox device that is installed in the field. It translates the vendors proprietary protocol into NTCIP PTZ commands.
AXIS Server - Snapshot L - Not much impacted by standards since no camera control involved
- IT video standards (digital) based; mature, but not addressed by ITS Standards
No ITS Standards are available for use with this system.
Portable Traffic Management (PTMS) Video Surveillance Component
M - Standards maturity questionable Cohu and Vicon have presented CCTV controls claiming conformance to NTCIP 1205 at the 2003 ITS America Annual meeting. Both companies deployed the services of another company to develop a ‘translator’ inside a blackbox device that is installed in the field. It translates the vendors proprietary protocol into NTCIP PTZ commands.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
56 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
Signal Priority
Transit Bus Priority System (Metro Transit, St. Cloud, etc.)
L - Likelihood of wide implementation questionable
- Currently use optical rather than approach indicated by draft standard
- Standard not available, but under development
As of June 2003, no products conforming to applicable standards are available.
Traffic Signal Priority/Pre-Emption L - Currently use optical rather than approach indicated by draft standard
- Standard not available, but under development
As of June 2003, no products conforming to applicable standards are available.
Traveler Information
TMC Data Distribution Server (DDS) L - Very important system, as source of all real time freeway data
- Standards maturity questionable
- Likely to be custom developed in-house
As of June 2003, no products conforming to applicable standards are available. This is mainly because this system uses custom developed software. It already uses IT(S) standards for communicating data across the network. However, replacing the DDS with Commercial Off The Shelf software is not feasible at this point, since the DDS is connected to many legacy systems.
KBEM L - Not much impacted by standards No ITS Standards are applicable to this system; thus, no products were researched.
Metro Transit Telephony System M - Lots of data sharing between the Transit systems required
- Maybe not able to upgrade soon
- Not likely to be available products?
- Talk with Metro Transit
Checked with FTA, APTA, and manufacturers (during March 2003 TCIP workshop) – no known products available . However, certain TCIP data elements are currently being implemented. Minneapolis Metro Transit and Columbus Transportation Authority (COTA) will be pilot projects for TCIP II implementations, whose output would be the input to an ATIS telephony system.
Scenic Byways Kiosk System M - Standards maturity questionable
- Utilizes standard Mn/CARS info
As of June 2003, no products conforming to applicable standards are available.
511 M -Need to understand 511 boundary as related to Mn/CARS, weather, transit, etc. to determine if 511 per se involves ITS standards
- Not Likely to be available products.
As of June 2003, no products conforming to applicable standards are available. However, the CARS/511-utilized XML software can be considered COTS.
Orion Parking Garage Monitors L - Likelihood of implementation unknown
- Not likely to be available products
As of June 2003, no products conforming to applicable standards are available. However, there is a DATEX development software used within the TransMIT and TXDOT implementations that conformed to a previous version of the DATEX standard. However, consistent use of the data element standards is questionable.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
57 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
Transit Schedule Web Pages L - Not likely to be available products Checked with FTA, APTA, and manufacturers (during March 2003 TCIP workshop) – no known products available . However, certain TCIP data elements are currently being implemented. Minneapolis Metro Transit and Columbus Transportation Authority (COTA) will be pilot projects for TCIP II implementations, whose output would be the input to an ATIS webpage system.
Transit Trip Planner L - System not likely to be updated soon
- Not likely to be available products
Checked with FTA, APTA, and manufacturers (during March 2003 TCIP workshop) – no known products available . However, certain TCIP data elements are currently being implemented. Minneapolis Metro Transit and Columbus Transportation Authority (COTA) will be pilot projects for TCIP II implementations, whose output would be the input to an ATIS trip planning system.
Metro Traffic Management Web Pages L - Custom developed in-house
- Standards maturity questionable
As of June 2003, no products conforming to applicable standards are available. However, the CARS/511-utilized XML software can be considered COTS.
511 Web Pages L - Custom developed in-house
- Standards maturity questionable
As of June 2003, no products conforming to applicable standards are available. However, the CARS/511-utilized XML software can be considered COTS.
St. Paul Advance Parking Information System (APIS)
M - Likelihood of wide implementation unknown As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
The Center-to-Field component is a DMS, for which now virtually all DMS vendors offer conformant products in various sizes, technologies, and configurations. Vendors claiming conformance to the applicable ITS DMS Standards include: 3M DMS, Adaptive Micro Systems, ADDCO, AmSig, National Signs, FDS, Dambach, Mark IV, Skyline, Daktronics, Skyline, LedStar, Display Solutions, and Vultron. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, DMJM-Harris, Kimley Horn, PB Farradyne, Siemens ITS.
Minneapolis Parking Management System L - Not much impacted by standards As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
The Center-to-Field components include DMS and CCTV. For both of these components, there are at least 2 vendors that over products conformant with the applicable NTCIP standards. DMS: now virtually all DMS vendors offer compliant products in various sizes, technologies, and configurations. Vendors claiming conformance to the applicable ITS DMS Standards include: 3M DMS, Adaptive Micro Systems, ADDCO, AmSig, National Signs, FDS, Dambach, Mark IV, Skyline, Daktronics, Skyline, LedStar, Display Solutions, and Vultron. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, DMJM-Harris, Kimley Horn, PB Farradyne, Siemens ITS.
CCTV conforming to the applicable ITS Standards is currently offered by COHU and Vicon.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
58 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
CVISN
Commercial Vehicle Information Systems and Networks (CVISN)
L - Being handled through other efforts No ITS Standards are applicable to this system; thus, no products were researched.
Traffic Signals
Closed Loop Signal Controllers & Detectors H - Master to local communications standards are relatively mature
- Central to master standards not available
- In terms of hardware, the Houston (TX) area agencies as well as Caltrans issued RFPs asking for ATC-compliant cabinets and controllers (which were based on 2070 controllers). Several companies including McCain, Safetran, Eagle, Peek and Econolite provided products to this effort.
Center to Field components conforming to the applicable ITS Standards are currently being offered by the following companies: Eagle, Econolite, Peek, McCain, NazTec, Bitran (now part of McCain)
Centralized Traffic Signal Systems & Detectors (St. Paul, MPLS, & Icons)
M - Not likely to replace current systems As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
Center to Field components conforming to the applicable ITS Standards are currently being offered by the following companies: Siemens Gardner (now Siemens ITS), NazTec, Eagle (now Siemens ITS), Peek, McCain, Bitran (now part of McCain), Econolite. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, Fortran, DMJM-Harris, Kimley Horn, and PB Farradyne.
Isolated Signal Controllers & Detectors L - This is covered in the closed loop signal controllers & detectors system, since this is a subset of those standards
Center to Field components conforming to the applicable ITS Standards are currently being offered by the following companies: Siemens Gardner (now Siemens ITS), NazTec, Eagle (now Siemens ITS), Peek, McCain, BiTrans (now part of McCain), Econolite. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, Fortran, DMJM-Harris, Kimley Horn, and PB Farradyne.
Lane Control Signals L - Not a wide deployment of these systems
- The controller portion is covered in the closed loop signal controllers & detectors
As of June 2003, there are no dedicated ITS Standards addressing this particular ITS System. However, the DMS-applicable standards could be used for this purpose using vendor-specific and/or agency-specific data elements.
Ramp Metering
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
59 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
Ramp Meters and Detector Stations H for controller &
cabinet
L for system software
- Custom software developed in -house
- Sufficiency of the NTCIP RMC 1207 standard is in question
- In terms of hardware, the Houston (TX) area agencies as well as Caltrans issued RFPs asking for ATC-compliant cabinets and controllers (which were based on 2070 controllers). Several companies including McCain, Safetran, Eagle, Peek and Econolite provided products to this effort.
As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
As of June 2003, only one installation using ITS Standards for Center to Field communications is known. This installation was done by Siemens ITS in Utah.
Data Collection and Monitoring
TH 55 Automatic Vehicle Identification (AVI) System (License plate readers)
L - Likelihood of continued implementation in question
- Products not likely available
As of June 2003, no products conforming with applicable standards for either the Center-to-Center or the Center to Field aspect are available.
Condition Acquisition and Report ing System (CARS) and the Maintenance Driver Automated Recording System [MDARS]
M - Very important system, as the main source of data for other systems
- Already uses ITS standards
- Custom developed
As of June 2003, no products conforming to applicable standards are available. However, the CARS/511-utilized XML software can be considered COTS.
Traffic Management
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
60 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
Virtual Transportation Operation Center (VTOC) Software
M/H - It is known already that standard compliant DMSs exist.
- Maturity of CCTV standards is in question
- It is valuable to determine if there are additional integrated standards compliant systems
- Talk to TOCC manager
As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
The Center-to-Field components include DMS and CCTV. For both of these components, there are at least 2 vendors that offer products conformant with the applicable NTCIP standards. DMS: Now virtually all DMS vendors offer compliant products in various sizes, technologies, and configurations. Vendors claiming conformance to the applicable ITS DMS Standards include: 3M DMS, Adaptive Micro Systems, ADDCO, AmSig, National Signs, FDS, Dambach, Mark IV, Skyline, Daktronics, Skyline, LedStar, Display Solutions, and Vultron. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, DMJM-Harris, Kimley Horn, PB Farradyne, Siemens ITS.
CCTV conforming to the applicable ITS Standards is currently offered by COHU and Vicon.
For other Center to Field components, there are no products claiming conformance with applicable standards available.
Integrated Corridor Traffic Management (ICTM)
L - Recently upgraded
- The controller portions is covered under closed loop signal controllers & detectors
- Likelihood of continued implementation in question
As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
The Center-to-Field components include DMS, CCTV, Ramp Meters, and Signal Controllers.
DMS: Now virtually all DMS vendors offer compliant products in various sizes, technologies, and configurations. Vendors claiming conformance to the applicable ITS DMS Standards include: 3M DMS, Adaptive Micro Systems, ADDCO, AmSig, National Signs, FDS, Dambach, Mark IV, Skyline, Daktronics, Skyline, LedStar, Display Solutions, and Vultron. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, DMJM-Harris, Kimley Horn, PB Farradyne, Siemens ITS.
CCTV conforming to the applicable ITS Standards is currently offered by COHU and Vicon.
As of June 2003, only one installation using ITS Standards for Center to Field communications is known. This installation was done by Siemens ITS in Utah.
Signal Controllers conforming to the applicable ITS Standards are currently being offered by the following companies: Siemens Gardner (now Siemens ITS), NazTec, Eagle (now Siemens ITS), Peek, McCain, BiTrans (now part of McCain), and Econolite. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, Fortran, DMJM-Harris, Kimley Horn, and PB Farradyne.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
61 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
High Occupancy Vehicle (HOV) Lane Gate System
L - Controller portion covered under closed loop signal controllers & detectors
As of June 2003, no products conforming with applicable standards for either the Center-to-Center or the Center to Field aspect are available.
HOV Lane Open/Closed Sign System
L - Not a wide deployment of these systems
- Custom developed in-house
- Controller portion covered under closed loop signal controllers & detectors
As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
The Center-to-Field component is a DMS, for which now virtually all DMS vendors offer conformant products in various sizes, technologies, and configurations. Vendors claiming conformance to the applicable ITS DMS Standards include: 3M DMS, Adaptive Micro Systems, ADDCO, AmSig, National Signs, FDS, Dambach, Mark IV, Skyline, Daktronics, Skyline, LedStar, Display Solutions, and Vultron. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, DMJM-Harris, Kimley Horn, PB Farradyne, Siemens ITS.
Dynamic Message Signs
PTMS Dynamic Message Sign Component M - Likelihood of wide implementation in question
- Valuable to determine the availability of wireless products
As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
The Center-to-Field component is a DMS, for which now virtually all DMS vendors offer conformant products in various sizes, technologies, and configurations. Vendors claiming conformance to the applicable ITS DMS Standards include: 3M DMS, Adaptive Micro Systems, ADDCO, AmSig, National Signs, FDS, Dambach, Mark IV, Skyline, Daktronics, Skyline, LedStar, Display Solutions, and Vultron. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, DMJM-Harris, Kimley Horn, PB Farradyne, Siemens ITS.
Freeway and Arterial Dynamic Message Signs
L - Products are known to exist
- Standards are currently in use for some of these systems
As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
The Center-to-Field component is a DMS, for which now virtually all DMS vendors offer conformant products in various sizes, technologies, and configurations. Vendors claiming conformance to the applicable ITS DMS Standards include: 3M DMS, Adaptive Micro Systems, ADDCO, AmSig, National Signs, FDS, Dambach, Mark IV, Skyline, Daktronics, Skyline, LedStar, Display Solutions, and Vultron. Additionally, Central System Vendors offering systems that conform to the applicable ITS Standards include E&K, DMJM-Harris, Kimley Horn, PB Farradyne, Siemens ITS.
Incident Management
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
62 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
CAD 911 / State Patrol AVL M - Not likely to be replaced soon
- Interfaces important for homeland security
As of June 2003, no products conforming with applicable standards for either the Center-to-Center or the Center to Field aspect are available.
Highway Helper AVL System (Current Ball system and planned Intergraph system)
M/H - Intended to be replaced soon As of June 2003, no products conforming with applicable standards for either the Center-to-Center or the Center to Field aspect are available.
I-90 Gate Control System (Existing and Planned)
L - Likelihood of wide implementation in question
- Not likely to be products available
As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
As for Center to Field components claiming conformance to ITS Standards, the following vendors offer CCTV them: COHU and Vicon.
For other Center to Field components, there are no products claiming conformance with applicable standards available.
HRI
Highway Railroad Intersection System (Existing and Planned)
M - Proprietary system currently being developed.
- Likely to have other products.
As of June 2003, no products conforming with applicable standards for either the Center-to-Center or the Center to Field aspect are available.
Train Detectors L - Not much impacted by standards
- Not in public sector's control
As of June 2003, no products conforming with applicable standards for either the Center-to-Center or the Center to Field aspect are available.
Environmental Monitoring
Mn/DOT Statewide Road Weather Information System (RWIS)
L - Already implements standards
As of June 2003, no products conforming to applicable standards for the Center-to-Center aspect are available.
As for Center to Field components claiming conformance to ITS Standards, the following vendors offer them: McQ-SII, Qualmetrics, SSI.
Automatic Weather Observing System (AWOS)
L - Not likely to be products available.
- Currently using FAA standard.
As of June 2003, no products conforming to applicable standards are available. But SSI developed a center-to-center interface into this system (which does not conform to potentially applicable ITS Standards).
SAIL
Safety Automatic Intelligent Locator (SAIL) Maintenance AVL System (Existing and future planned expansion)
L - Maintenance Market Package recently added to ITS Architecture, not likely to have products.
As of June 2003, no products conforming to applicable standards are available.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
63 / 64 June 24, 2003
System Name: Product Search Priority:
Comments: Product Availability
Vehicle Sensor
Intelligent Vehicle Initiative (IVI) Systems (TH7, TH 19, TH 101, etc)
M - Need more information
As of June 2003, no products conforming to applicable standards are available.
Mayday/Site Surveillance
Mayday System H - Potential Homeland security issue
- Potentially expanding area, National Mayday Readiness Initiative (NMRI)
As of June 2003, no products conforming to applicable standards are available.
Mn/DOT – ITS Candidate Systems, Standards, and Products Final Report
64 / 64 June 24, 2003
CHAPTER 7 - SUMMARY
Migration to the routine use of standards by Mn/DOT and others is going to be an incremental process involving a number of steps over a period of years. Using the base line information contained in this report on Minnesota ITS Systems, related standards, the status of standards and the status of related products, the next phase will consist of developing a Minnesota specific “ITS STANDARDS RECOMMENDATIONS REPORT”. That report will be based on the status of the standards development process at the time the effort is completed in mid 2003. That report, as with this report, will reflect not only the views of national experts involved with the development and application of standards but also the views of Minnesota stakeholders.