Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS...

44
Minnesota Statewide Regional ITS Architecture Version 2009 March 2009 Prepared for: Prepared by: Volume 4: Advanced Public Transportation Systems Market Package Bundle

Transcript of Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS...

Page 1: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide RegionalITS ArchitectureVersion 2009

March 2009

Prepared for:

Prepared by:

Volume 4: Advanced Public Transportation Systems Market Package Bundle

Page 2: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS ArchitectureVersion 2009

Volume 4: Advanced Public Transportation SystemsMarket Package Bundle

Prepared by

URS Corporation

In association with

TranSmart Technologies, Inc.

March 2009

Page 3: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

i

TABLE OF CONTENTS

1. Overview ........................................................................................................................... 1

1.1 ITS Planning and Regional Architecture Update ....................................................... 1

1.2 Volume 4 – Advanced Public Transportation Systems.............................................. 2

2. Identification of Existing APTS ....................................................................................... 3

3. Development Objectives.................................................................................................. 4

4. Needs and Services ......................................................................................................... 5

5. Detail of APTS Needs and Services ................................................................................ 7

6. APTS Research and Development Needs....................................................................... 7

Appendix A: Existing/Planned APTS Elements ..................................................................... 9

Appendix B: MN ITS Development Objectives..................................................................... 14

Appendix C: Needs and Services Detail............................................................................... 18

Appendix D: APTS Market Packages and Descriptions ...................................................... 38

Page 4: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

ii

ACRONYMS

AD Archived Data ManagementADA Americans with Disabilities ActAPTS Advanced Public Transportation SystemATIS Advanced Traveler Information SystemATMS Advanced Traffic Management SystemAVL Automatic Vehicle LocationAVSS Advanced Vehicle Safety SystemCAD Computer Aided DispatchCAT Cities Area Transit (East Grand Forks)CCTV Closed Circuit TelevisionCVO Commercial Vehicle OperationsDARTS Dakota Area Resources and Transportation for SeniorsDOT Department of TransportationDTA Duluth Transit AuthorityEM Emergency ManagementEVP Emergency Vehicle PreemptionGIS Geographic Information SystemGPS Global Positioning SystemHOV High-Occupancy VehicleITS Intelligent Transportation SystemsIVR Interactive Voice ResponseMAT Metro Area Transit (Moorhead)MCM Maintenance and Construction ManagementMDT Mobile Data TerminalMn/DOT Minnesota Department of TransportationMTC Metropolitan Transit Commission (St. Cloud)PDA Personal Digital AssistantRTMC Regional Transportation Management CenterTSP Transit Signal Priority

Page 5: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems

1

1. Overview 1.1 ITS Planning and Regional Architecture Update The Minnesota Statewide Regional ITS Architecture represents a shared vision of how each agency’s systems work together by sharing information and resources to enhance transportation safety, efficiency, capacity, mobility and security. The information exchange among the many transportation stakeholders helps illustrate various integration options, gain consensus on cost-effective ITS technologies and systems to be considered prior to investing in design, development and deployment of ITS. The Regional ITS Architecture is a living document and will evolve as needs, technology, stakeholders and funding change. The National ITS Architecture is a resource to the Minnesota Statewide Regional Architecture providing framework for planning, defining and integrating ITS. The Minnesota Statewide Regional ITS Architecture is organized as follows:

Volume 1 – Overview: Volume 1 identifies the purpose/need, a general description of the region, development objectives, and performance measures for the Minnesota Statewide Regional ITS Architecture.

Volumes 2 thru 7 – Development and Documentation of Market Package Bundles:

Each volume will be specific to the corresponding Market Package Bundle and include: a description of the Market Package Bundle, ITS development objectives, a summary of needs and services, and a detailed description of needs and services (consisting of the operational concept, inventory, specific market packages to address needs and services, interconnects and architecture flows, and functional requirements).

Volume 8 – Regional ITS Architecture: Volume 8 consists of the hard copies of the

Turbo Architecture outputs and the corresponding electronic files.

Volume 9 – Regional ITS Architecture Implementation Projects: This volume describes processes for developing an ITS program and projects and identifies an implementation project summary and corresponding project detail for each project. The project detail will include a project description, dependencies, time frame, project champion and any agency agreements required.

The purpose for developing Volumes 2 through 7 was to identify and prioritize stakeholder needs; gather information on existing infrastructure, components and technology; and define stakeholder roles and responsibilities in planning, deploying, operating and maintaining existing and future ITS systems. Data collection activities were conducted early in the study process and focused on two primary tasks:

1. The assemblage of an inventory of existing and planned transportation infrastructure and, facilities and services.

2. The assessment of statewide needs and opportunities for further deployment of ITS needs.

Page 6: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

2

Previously published transportation plans were the main source of data about characteristics ofthe existing transportation system, planned improvements, transportation system needs andgoals. Strategic and long-range planning studies, ITS deployment and safety plans, transitstudies and transportation planning and policy documents were reviewed.

1.2 Volume 4 – Advanced Public Transportation Systems

Advanced Public Transportation Systems (APTS) are intended to enhance public transportationchoices, safety and efficiency with a goal towards increased transit ridership.

Development of Volume 4 entailed the Project Consultant to work closely with Mn/DOT andstakeholders to identify and prioritize stakeholder needs; gather information on existing andfuture ITS infrastructure, components and technology; and define the stakeholders’ roles andresponsibilities in planning, deploying, operating and maintaining existing and future ITSsystems.

Volume 4 summarizes the findings of data collection and analysis activities conducted tosupport development of the APTS Market Package Bundle. Volume 4 is organized with thefollowing sections:

Section 1: Overview provides a brief project overview and the purpose of thisdocument.Section 2: Identification of Existing APTS provides a brief overview of statewideAPTS deployments with a detailed listing of existing/planned systems in Appendix A.Section 3: Development Objectives provides an overview of the Minnesota ITSDevelopment Objectives specific to APTS. This section summarizes the results of anAPTS stakeholder workshop conducted in 2006 to obtain feedback on the MinnesotaITS Deployment Objectives. These objectives are used to identify needs and gaps,which will then be used to identify services to address those needs.Section 4: Identification of Needs and Services. Based on the ITS DevelopmentObjectives, needs were identified and prioritized by the stakeholders. Services wereidentified to address those prioritized needs.Section 5: Detail of APTS Needs and Services describes, for each identifiedNeed/Service, the following information:

o Operational Concept - who is currently using the service and how they areusing it. Users include both managers and operators of a system and otherusers, like the traveling public, who use an end service.

o Existing Capabilities - what systems are currently in place that are used toprovide this service and who operates these services.

o Gaps and Planned Enhancements - enhancements that can be made to betterprovide the service and address needs, who will use these enhancements, andwhat they will be used for. These enhancements can include expanding systemsto geographic areas that currently do not have access to the service, enhancingan existing service to provide greater functionality or use by more groups, orimplementing a new system to address a gap.

o Roles and Responsibilities - what roles stakeholders need to fulfill to make theservice operate successfully throughout a system’s lifecycle (planning, design,implementation, operations, and maintenance).

o Interconnects - the communications linkages between subsystems orstakeholders to provide the service.

Page 7: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

3

o Archive Needs - what data is generated for the service that should be archived,who is responsible for archiving, and any special needs or requirements for sucharchiving.

o Associated Market Packages - other Market Packages that the service fallsunder. This includes both Market Packages within the APTS Market PackageBundle and those in other Market Package Bundles.

Section 6: APTS Research and Development Needs describes general research thatcan be performed to help implement the identified services.

2. Identification of Existing APTS

APTS systems are utilized throughout Minnesota to assist in transit operations and enhanceservices to transit users. Using those systems has improved schedule adherence, transitsecurity, backroom operations, and availability of information about modal choices.

APTS can be used to assist in the operations, security, and fleet management, of a transitsystem as well as coordinate services provided by different transit providers. Transit users canaccess schedule information through telephone systems, Internet sites or electronic displays,quickly pay with electronic payment cards, and easily transfer to another transit vehicle or modeof travel. APTS also allow transit vehicles to operate more efficiently and stay on schedulethrough implementations such as scheduling software, bus signal priority, computer-aideddispatch (CAD), automated vehicle location (AVL), and mobile data terminals (MDT).Operations managers can use services such as automated passenger counting, vehicletracking, fare management, and dispatch and response logs to enhance operational planningand make back-office activities more efficient. Security enhancements such as transit platformmonitoring, in-vehicle surveillance and driver alert systems are used to improve the safety ofpassengers as well as vehicle operators.

An inventory of existing and planned APTS ITS systems (e.g. control centers, vehicles, devicesand infrastructure) in Minnesota is described in Appendix A. This inventory summarizes a list ofexisting and programmed ITS systems in the state, their general description, associatedstakeholder that are involved with their operations and management, and their currentdeployment. The systems described in Appendix A are Minnesota-specific implementations ofsubsystems described in the National ITS Architecture.

Page 8: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

4

3. Development Objectives

Transportation needs identify the transportation problems that can be solved by ITS services.They also represent a link to transportation planning efforts that define the strategies used todefine problems. These strategies involve capital improvements as well as operationalimprovements. APTS solutions involve services that improve the schedule adherence, safety,and operations of the transit system as well as the safety and experience of the transit user.

APTS are intended to enhance public transportation choices, safety and efficiency with a goaltowards increased transit ridership. The vision for APTS is that it will enable travelers inMinnesota to have reliable public transportation choices for a safe, efficient and satisfying trip.The following Minnesota ITS Development Objectives, specific to APTS, are steps to determineand/or measure whether or not APTS goals are being achieved. A complete list of MinnesotaITS Development Objectives is included in Appendix B.

A. Improve the Safety of the State’s Transportation SystemA-1. Reduce crash frequency (ATMS, ATIS, APTS, CVO, EM, MCM & AVSS)

O-7 Reduce lane departure crashesO-12 Reduce crashes due to driver errors and limitationsO-13 Reduce crashes involving pedestrians or non-motorized vehicles

A-3. Safeguard the motoring public from homeland security and/or Hazmat incidents(ALL)O-19 Reduce security risks to transit passengers and transit vehicle operatorsO-21 Reduce security risks to transportation infrastructure

B. Increase Operational Efficiency and Capacity of the Transportation SystemB-2. Increase average vehicle occupancy and facility throughput (ATMS & APTS)

O-28 Increase transit ridershipO-29 Enhance transit operations efficiency

B-4. Reduce traffic delays during evacuation from homeland security and Hazmatincidents (ALL)

O-24 Reduce congestion and delay

C. Enhance Mobility, Security, Convenience, and Comfort for the TransportationSystem UserC-1. Reduce congestion and incident-related delay for travelers (ATMS, ATIS & APTS)

O-24 Reduce congestion and delayO-26 Maintain smooth traffic flowO-34 Enhance parking facility services and management

C-3. Increase choice of travel modes (APTS & ATMS)O-35 Inform travelers of travel mode options

C-4. Enhance traveler security (ATMS & EM)O-19 Reduce security risks to transit passengers and transit vehicle operatorsO-21 Reduce security risks to transportation infrastructure

C-5. Reduce stress caused by transportation (ATMS, ATIS, APTS, EM & MCM)O-24 Reduce congestion and delayO-29 Enhance transit operations efficiencyO-34 Enhance parking facility services and managementO-35 Inform traveler of travel mode options

Page 9: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

5

D. Enhance the Present and Future Economic Productivity of Individuals,Organizations and the Economy as a WholeD-1. Reduce travel time for freight, transit and businesses (ATMS, ATIS, APTS & CVO)

O-24 Reduce congestion and delayO-26 Maintain smooth traffic flowO-29 Enhance transit operations efficiency

D-3. Improve travel time reliability for freight, transit and businesses (ATMS, APTS &CVO)O-26 Maintain smooth traffic flowO-29 Enhance transit operations efficiency

D-4. Increase agency efficiency (ATMS, APTS, AD, CVO, EM & MCM)O-29 Enhance transit operations efficiencyO-39 Enhance garage operations efficiencyO-36 Enhance asset and resource management

D-6. Aid in transportation infrastructure and operations planning (ALL)O-36 Enhance asset and resource managementO-41 Enhance planning with better dataO-42 Enhance investment decision making

D-7. Reduce vehicle operating costs (ATMS, APTS, CVO & AVSS)O-24 Reduce congestion and delayO-26 Maintain smooth traffic flow

E. Reduce Energy Consumption, Environmental Impacts and Costs of TransportationE-3. Reduce negative impacts of the transportation system on communities (APTS,

ATMS, EM & MCM)O-28 Increase transit ridership

4. Needs and Services

An APTS stakeholder workshop was conducted on June 8, 2006 to obtain feedback on theMinnesota ITS Development Objectives and determine the APTS needs and services for thestate. Based on the Objectives, the facilitators of the workshop provided functional andinformational needs to the APTS stakeholder group to review and further develop into an APTSITS Needs and Service list. The group was then asked to prioritize the identified needs andservices.

Table 1 displays the Specific Functional/Informational Needs/Services as potential solutions andenhancements. Priority is indicated in the Priority Points column, with each point representingone vote from each attendee at the APTS workshop. Due to time constraints, some functionaland information needs were identified but did not get voted on by the stakeholder group.Additionally, other needs were introduced after the voting occurred. These needs and servicesare designated with an “n/a” in the Points column. Table 1 also provides the APTSDevelopment Objectives and ITS Architecture Market Packages with the correspondingpotential solutions. The potential solutions and enhancements identified in Table 1 will providethe required service(s) to fill the gaps summarized in Appendix C. This appendix will take theAPTS Needs and associated APTS Solutions and define what and how the system will be used,who will use it and who is responsible for planning, design, implementation, operation andmaintenance of the system.

Page 10: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

6

Table 1. APTS Needs and Potential Solutions

* Discussions on needs/solutions fall under other market package bundles can be found incorresponding Market Package Bundle documents.

ID Need/Potential Solution PriorityPoint

APTSDevelopment

Objective

National ITSArchitectureReference

TR01 Provide transit route, schedule, and fareinformation

9 O-28, O-35 APTS08

TR02 Provide real-time transit vehiclearrival/departure information

8 O-28, O-35 APTS01,APTS08,ATMS06

TR03 Provide simple fare payment systems 6 O-29 APTS04TR04 Coordinate timed transfers between

route segments, providers & modes5 O-24, O-28 APTS07

TR05 Manage transit fleet and personneloperations

5 O-19, O-29, O-36 APTS01

TR06 Provide surveillance and enforcement ontransit vehicles and transit facilities

5 O-19, O-21 APTS05

TR07 Provide electronic fare payment card 3 O-24, O-29 APTS04TR08 Support vehicle diagnostics and

maintenance3 O-36, O-39 APTS06

TR09 Measure historical transit routeperformance

2 O-29, O-36, O-41, O-42

APTS01, AD1

TR10 Provide on-board automated enunciators 2 O-35 APTS08TR11 Provide information to the ADA

community2 O-28 APTS08

TR12 Optimize garage operations 2 O-39 APTS06TR13 Provide collision avoidance assistance

for transit vehicles1 O-7, O-12 AVSS03,

AVSS04TR14 Provide security at park and ride lots 1 O-19, O-34 APTS05TR15 Optimize schedule efficiency 1 O-29, O-36 APTS02TR16 Provide information on ridesharing

opportunitiesn/a O-30 APTS08,

ATIS08TR17 Coordinate transit vehicle movements

with traffic control devicesn/a O-24, O-26, O-

28, O-29APTS09

TR18 Install pedestrian detection/warningsystem to reduce incidents

n/a O-12, O-13 AVSS03

TR19 Provide queue jumping n/a O-24 APTS09TR20 Provide real-time transfer information to

travelers en routen/a O-35 APTS08

TR21 Provide on-line reservation system fordemand-responsive transit

n/a O-28, O-29, O-35 APTS03,ATIS02

TI19 Provide different alternatives to travelersfor the most appropriate route/mode/timeof travel

n/a O-24, O-26, O-35 ATIS01, ATIS05,APTS08

Page 11: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

7

5. Detail of APTS Needs and Services

A detailed description of each APTS Needs and Services for Minnesota is found in Appendix C.Appendix C contains a table, listing the services sorted by Market Package and details for theservice. The details described in the table include:

Operational Concept: Describes who is currently using the service and how theyare using it. Users of the service include both managers and operators of a systemand other users who may be impacted and/or benefit from such a service, such asother agencies and the traveling public.Existing Capabilities: Describes what systems are currently in place that are usedto provide this service and who operates these systems and provides such services.Gaps and Planned Enhancements: Summarizes enhancements that can be madeto better provide the service and address needs, who will use these enhancements,and what they will be used for. These enhancements include expanding currentsystems to geographic areas that presently do not have access to the service,enhancing an existing service to fill identified gaps or use by more groups, orimplementing a new system to address a need.Roles and Responsibilities: Describes the roles and responsibility of involvingstakeholders to make the service operate successfully throughout a system’slifecycle (planning, design, implementation, operations, and maintenance).Interconnects: Presents the communications linkages between subsystems orstakeholders to provide the service.Archive Needs: Summarizes what data is generated for the service that should bearchived, who is responsible for archiving, and any special needs or requirements forsuch archiving.Associated Market Packages: Describes other Market Package(s) required todeliver the desired service. This includes both Market Packages within the APTSMarket Package Bundle and those in other Market Package Bundles.

6. APTS Research and Development Needs

In order to fill gaps in APTS services, some research must be performed to test solutions andgain a greater understanding of what can effectively address identified needs. Research andTechnology development needs and opportunities for APTS are summarized in the following:

Communications Analyze technologies and policies to transmit and record real-time operations data

Data Enhance route performance analysis tools Enhance archived data search tools Refine/enhance transit scheduling software Test coordination of different agency scheduling software for mixed mode/provider

schedule coordination Test use of transit vehicles as traffic probes

Operations Test transit signal priority technologies and systems Develop bus stop occupancy alert system for drivers

Page 12: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

8

Test smart/electronic fare cards Enhance carpool rideshare finding systems

Maintenance Enhance vehicle performance monitoring/diagnostic equipment Test in-garage transit vehicle bus finder system

Transit Information Test traveler information distribution methods for ADA and elderly communities Test transit information distribution to PDAs/handheld wireless devices Enhance trip planning systems Develop/enhance on-line transit reservation systems Enhance interactive transit information systems Test bus arrival announcement systems at bus stops Develop and test next bus arrival time systems

Safety Test pedestrian warning systems Test collision avoidance systems Test lane departure warning/shoulder driving assistance systems

Security Enhance automated surveillance monitoring/alert systems

Page 13: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

9

Appendix A: Existing/Planned APTS Elements

Element MarketPackage Description Stakeholder Status

Commuter RailOperationsCenter

APTS02,APTS04,APTS07

This element represents the NorthstarCommuter Rail operations center that willoperate and maintain commuter rail vehiclesbetween downtown Minneapolis and BigLake beginning in 2009. Commuter railvehicle maintenance facility will be located inBig Lake. Stations are planned inMinneapolis, Fridley, Coon Rapids, Anoka,Elk River, and Big Lake. Future plans are toexpand the commuter rail line northwest todowntown Saint Cloud and the VA MedicalCenter.

NorthstarCorridorDevelopmentAuthority

Planned

DynamicMessage SignRoadsideEquipment

APTS08,ATMS06

Real-time information on transit travel timesas compared passenger-vehicle travel timeswill be displayed to passengers via dynamicmessage signs prior to arriving at selectedpark-and-ride locations in the Twin Citiesmetro area.

Mn/DOT,Metro Transit Planned

Intercity TransitManagementCenters

APTS02,APTS04

This element represents transit managementcenters that operate intercity fixed routestraveling long distances. These centersinclude the Northstar Commuter Coachtraveling between Elk River and Minneapolisand Greyhound and Jefferson Lines busestraveling throughout the state.

IntercityTransitProviders

Existing

Light RailOperationsCenter

APTS02,APTS06,APTS09

This element represents the Metro TransitHiawatha light rail transit managementcenter. This center dispatches and maintainsall light rail transit vehicles running betweendowntown Minneapolis and the Mall ofAmerica in Bloomington. It is planned toexpand light rail operations along UniversityAvenue between Minneapolis and Saint Paulby 2014. Other light rail transit linesconnecting suburbs with Minneapolis andSaint Paul are in early planning stages.

Metro Transit Existing

Page 14: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

10

Element MarketPackage Description Stakeholder Status

Local TransitManagementCenters

APTS01,APTS02,APTS03,APTS04,APTS05,APTS06,APTS08,APTS09,APTS10

This element represents local transitmanagement centers operating outside of theTwin Cities metropolitan area that operatefixed route and demand responsive publictransit services. These centers include theSt. Cloud Metropolitan Transit Commission(MTC), Duluth Transit Authority (DTA), City ofRochester Public Transit, Metro Area Transit(MAT -- serving Moorhead), Cities AreaTransit (CAT -- serving East Grand Forks),and various county and city-level transitmanagement centers. St. Cloud MTC usesITS applications such as transit signal priority(TSP), electronic fare collection, on-boardsurveillance systems, and automated transitfleet management system. DTAdisseminates real-time bus arrival informationat bus stops, via the internet, and via on-board enunciators. DTA manages electronicfare collection with smart “touch” cards thatare integrated with U of M student ID cards.DTA also operates surveillance systems on-board all buses and at transit centers/garages. City of Rochester manageselectronic fare collection and plans to operateTSP at all signalized intersections that serveemergency vehicles with traffic signalpreemption within the City. MAT currentlyoperates electronic fare collection and plansto operate TSP at intersections where trafficsignals are operated by Mn/DOT. CATcurrently operates TSP at intersectionswhere traffic signals are operated byMn/DOT. Various other counties and citiesthroughout the state are in the process ofdeploying AVL equipment.

Local TransitProviders Existing

Page 15: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

11

Element MarketPackage Description Stakeholder Status

Metro AreaTransitManagementCenters

APTS01,APTS02,APTS03,APTS04,APTS05,APTS06,APTS07,APTS08,APTS09,APTS10

This element represents transit managementcenters operating within the Twin Citiesmetropolitan area that operate fixed routeand demand responsive public transitservices. This includes the Metro TransitControl Center and Suburban TransitProvider Operations Centers, independent ofMetro Transit, that connect outer-ring metro-area suburbs with Minneapolis and St. Paulmetro areas. Metro Transit Control Centerutilizes Global Position System (GPS)technology to identify the location of all transitvehicles and also uses an 800-megahertzregional radio system, which allows MetroTransit to interact with police and firedepartments and emergency responseteams. Metro Transit also utilizes anautomated transit fleet maintenance system(TxBase). Within the metro area, door-to-door demand response transit service isprovided by Metro Mobility (servingMinneapolis, St. Paul and many surroundingsuburbs), Anoka County Traveler (servingAnoka County), DARTS (serving DakotaCounty), Scott County (Scott County) andH.S.I. (serving Washington County). Transitfare coordination exists between MetroTransit and all Suburban Transit Providers.As a suburban transit provider, MinnesotaValley Transit Authority plans to implementBus Rapid Transit components, such astransit signal priority and transit kiosks attransit stations along the Cedar Avenue / I-35W Corridor. Other Suburban TransitProviders include Maple Grove Transit,Southwest Metro Transit Commission, PriorLake Laker Lines, Plymouth Transit, andScott County Transit.

Metro AreaTransitProviders

Existing

Park-and-RideParkingInformationSystemRoadsideEquipment

APTS08,ATMS16

Real-time information on availability ofparking spaces at transit park-and-ridefacilities will be displayed to drivers viaelectronic message signs at selected park-and-ride locations in the Twin Cities metroarea.

Metro Transit Planned

Real-Time BusArrival TimeDisplayRoadsideEquipment

APTS08

Real-time information on bus and light railarrival/departure times will be displayed topassengers via electronic message signs atbus stops and light rail stations in the TwinCities metro area. Signs will also be installedat key decision points for drivers alongarterial roads and freeways prior to entrancesto park-and-ride facilities. Commuter railarrival/departure times could also bedisplayed to travelers in the future.

Metro Transit Planned

Page 16: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

12

Element MarketPackage Description Stakeholder Status

Traffic SignalRoadsideEquipment

APTS09

This element represents traffic signals on allMinnesota roads and highways that arecontrolled by Traffic Signal Central Controland monitored by Traffic Signal CentralMonitoring. Transit Signal Priority (TSP)capability has been implemented in the SaintCloud metro area. A TSP system will beimplemented in the Twin Cities metro area forMetro Transit by the end of 2009.

Mn/DOT,LocalAgencies

Existing

Transit Centerand StationSurveillanceSystemRoadsideEquipment

APTS05

These systems represent surveillance andsecurity monitoring at transit centers,garages, stations, and park and ride lots. Thesystems have been implemented at centersand garages for the Saint Cloud MetropolitanTransit Commission, Duluth Transit Authority,and Metro Transit. Park and ride surveillancesystem and light rail boarding areasurveillance systems are deployed by MetroTransit.

Metro AreaTransitProviders,Local TransitProviders

Existing

TransitInformationWebsites

APTS08,ATIS01,ATIS07,ATIS08

This element represents websites thatprovide general route and scheduleinformation to travelers. Metro Transit,Duluth Transit Authority, and Cities AreaTransit websites support transit trip plannerfunctions. Metro Transit website alsoprovides real-time bus arrival information andsupports trip planning and dynamicridesharing functions. DARTS is consideringan on-line ride reservation system.

Metro AreaTransitProviders,Local TransitProviders

Existing

Transit Kiosks APTS04,APTS08

This element represents transit kiosks thatmanage electronic fare payment and providereal-time stop arrival notifications. Kiosks arecurrently in operation along the Metro TransitHiawatha Light Rail line. Kiosks are plannedas part of the Minnesota Valley TransitAuthority Bus Rapid Transit project alongCedar Avenue and I-35W.

Metro AreaTransitProviders

Existing

Page 17: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

13

Element MarketPackage Description Stakeholder Status

Transit VehicleEquipment

APTS01,APTS02,APTS03,APTS04,APTS05,APTS06,APTS08,APTS09,APTS10,AVSS03,AVSS04,AVSS09

This element represents transit vehicles andon-board ITS equipment operated by transitservice providers. On-board ITS equipmentmay include AVL, MDT, radiocommunications, TSP, passenger counter,electronic fare collection equipment,surveillance and security monitoring devices,and traveler information annunciation. TSPexists on vehicles serving St. Cloud and EastGrand Forks. TSP is planned for vehiclesserving Minneapolis, Rochester, Duluth, andMoorhead. Transit vehicles for Metro Transit,MTC, and DTA are equipped with on-boardsurveillance cameras. Transit vehicles forMetro Transit, MTC, and DTA haveAutomated Vehicle Location (AVL) devicesinstalled. Transit vehicles for Metro Transit,MTC, DTA, MAT, CAT, and Rochestersupport electronic fare collection devices.Transit vehicles for Metro Transit and DTAsupport automated passenger counting.Light Rail transit vehicles support automatednext stop annunciation. MVTA and MetroTransit plan to deploy transit vehicle lateraland longitudinal vehicle safety warningsystems as well as advanced vehicle lateralcontrol for shoulder-running buses to improvetransit travel safety.

Metro AreaTransitProviders,Local TransitProviders,IntercityTransitProviders,NCDA

Existing

TransitLinePhone System APTS08

This system allows users to utilize atouchtone phone to access transit scheduleinformation. TransitLine also gives othertransit related information such as State Fairtransit information, and Snow Rerouteinformation when applicable. TransitLineprovides visually impaired customers withequal access to schedules. It is planned toupgrade the system with limited voiceresponse technology and real-time busarrival and departure information.

Metro Transit Existing

Page 18: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

14

Appendix B: MN ITS Development ObjectivesGeneral Purpose: Create a system that enhances transportation through the safe and efficientmovement of people, goods, and information, with greater mobility and fuel efficiency, lesspollution, and increased operating efficiency in Minnesota.

A. Improve the Safety of the State’s Transportation SystemA-1. Reduce crash frequency (ATMS, ATIS, APTS, CVO, EM, MCM & AVSS)

O-1 Reduce crashes due to road weather conditionsO-2 Reduce crashes due to unexpected congestionO-3 Reduce secondary crashesO-4 Reduce incident clearance timeO-5 Reduce crashes due to red-light runningO-6 Reduce crashes due to unsafe drivers, vehicles and cargo on the

transportation systemO-7 Reduce lane departure crashesO-8 Reduce crashes due to roadway/geometric restrictionsO-9 Reduce crashes at railroad crossingsO-10 Reduce crashes at intersectionsO-11 Reduce speed differentialO-12 Reduce crashes due to driver errors and limitationsO-13 Reduce crashes involving pedestrians or non-motorized vehiclesO-14 Reduce violation of traffic laws

A-2. Reduce fatalities and life changing injuries (ATMS, ATIS, CVO, EM, MCM & AVSS)O-5 Reduce crashes due to red-light runningO-9 Reduce crashes at railroad crossingsO-10 Reduce crashes at intersectionsO-11 Reduce speed differentialO-15 Reduce emergency/incident response timeO-16 Enhance emergency/incident response effectivenessO-17 Safeguard public safety personnel while they are at roadway incidents and

emergenciesO-18 Reduce speed violations

A-3. Safeguard the motoring public from homeland security and/or Hazmat incidents (ALL)O-15 Reduce emergency/incident response timeO-19 Reduce security risks to transit passengers and transit vehicle operatorsO-20 Reduce security risks to motorists and travelersO-21 Reduce security risks to transportation infrastructureO-22 Reduce exposure due to Hazmat & homeland security incidentsO-23 Enhance tracking and monitoring of sensitive Hazmat shipments

A-4. Reduce crashes in work zones (ATMS, ATIS, EM & MCM)O-4 Reduce incident clearance timeO-11 Reduce speed differentialO-24 Reduce congestion and delayO-25 Enhance safety of workers

B. Increase Operational Efficiency and Capacity of the Transportation SystemB-1. Reduce overall delay associated with congestion (ATMS, ATIS & MCM)

O-4 Reduce incident clearance timeO-15 Reduce emergency/incident response timeO-16 Enhance emergency/incident response effectiveness

Page 19: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

15

O-24 Reduce congestion and delayO-26 Maintain smooth traffic flowO-27 Reduce incident detection and verification time

B-2. Increase average vehicle occupancy and facility throughput (ATMS & APTS)O-28 Increase transit ridershipO-29 Enhance transit operations efficiencyO-30 Increase carpoolersO-31 Increase throughput of roadways

B-3. Reduce delays due to work zones (ATMS, ATIS, EM & MCM)O-4 Reduce incident clearance timeO-24 Reduce congestion and delayO-26 Maintain smooth traffic flow

B-4. Reduce traffic delays during evacuation from homeland security and Hazmat incidents(ALL)O-24 Reduce congestion and delay

B-5. Enhance efficiency at borders (ATMS, CVO, EM & AVSS)O-32 Reduce delays at border crossingsO-33 Keep travelers informed of travel conditions

C. Enhance Mobility, Security, Convenience, and Comfort for the Transportation SystemUserC-1. Reduce congestion and incident-related delay for travelers (ATMS, ATIS & APTS)

O-4 Reduce incident clearance timeO-15 Reduce emergency/incident response timeO-16 Enhance emergency/incident response effectivenessO-24 Reduce congestion and delayO-26 Maintain smooth traffic flowO-27 Reduce incident detection and verification timeO-34 Enhance parking facility services and management

C-2. Improve travel time reliability (ATMS)O-24 Reduce congestion and delayO-26 Maintain smooth traffic flow

C-3. Increase choice of travel modes (APTS & ATMS)O-33 Keep travelers informed of travel conditionsO-35 Inform travelers of travel mode options

C-4. Enhance traveler security (APTS & EM)O-19 Reduce security risks to transit passengers and transit vehicle operatorsO-20 Reduce security risks to motorists and travelersO-21 Reduce security risks to transportation infrastructure

C-5. Reduce stress caused by transportation (ATMS, ATIS, APTS, EM & MCM)O-3 Reduce secondary crashesO-11 Reduce speed differentialO-14 Reduce violation of traffic lawsO-18 Reduce speed violationsO-24 Reduce congestion and delayO-29 Enhance transit operations efficiencyO-33 Keep travelers informed of travel conditionsO-34 Enhance parking facility services and managementO-35 Inform traveler of travel mode options

Page 20: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

16

D. Enhance the Present and Future Economic Productivity of Individuals, Organizationsand the Economy as a WholeD-1. Reduce travel time for freight, transit and businesses (ATMS, ATIS, APTS & CVO)

O-24 Reduce congestion and delayO-26 Maintain smooth traffic flowO-29 Enhance transit operations efficiencyO-33 Keep travelers informed of travel conditions

D-2. Improve the efficiency of freight movement, permitting and credentials process (ATIS &CVO)O-33 Keep travelers informed of travel conditionsO-36 Enhance asset and resource managementO-37 Enhance credential process automationO-38 Reduce freight movement delays due to inspection

D-3. Improve travel time reliability for freight, transit and businesses (ATMS, APTS & CVO)O-26 Maintain smooth traffic flowO-29 Enhance transit operations efficiencyO-33 Keep travelers informed of travel conditionsO-38 Reduce freight movement delays due to inspection

D-4. Increase agency efficiency (ATMS, APTS, AD, CVO, EM & MCM)O-29 Enhance transit operations efficiencyO-36 Enhance asset and resource managementO-39 Enhance garage operations efficiency

D-5. Safeguard existing infrastructure (CVO, EM & MCM)O-21 Reduce security risks to transportation infrastructureO-36 Enhance asset and resource managementO-40 Reduce commercial vehicle size and weight violations

D-6. Aid in transportation infrastructure and operations planning (ALL)O-36 Enhance asset and resource managementO-41 Enhance planning with better dataO-42 Enhance investment decision making

D-7. Reduce vehicle operating costs (ATMS, APTS, CVO & AVSS)O-24 Reduce congestion and delayO-26 Maintain smooth traffic flow

E. Reduce Energy Consumption, Environmental Impacts and Costs of TransportationE-1. Reduce emissions/energy impacts and use associated with congestion (ATMS, ATIS &

CVO)O-24 Reduce congestion and delayO-33 Keep travelers informed of travel conditionsO-43 Enhance compliance of air quality standards

E-2. Reduce need for new facilities (ATMS,CVO & MCM)O-31 Increase throughput of roadwaysO-36 Enhance asset and resource managementO-37 Enhance credential process automation

E-3. Reduce negative impacts of the transportation system on communities (APTS, ATMS,EM & MCM)O-14 Reduce violation of traffic lawsO-28 Increase transit ridershipO-30 Increase carpoolersO-44 Reduce environmental impacts of de-icing material use

Page 21: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

17

AD: Archived Data Management AVSS: Advanced Vehicle Safety SystemsAPTS: Advanced Public Transportation Systems CVO: Commercial Vehicle OperationsATIS: Advanced Traveler Information Systems EM: Emergency ManagementATMS: Advanced Traffic Management Systems MCM: Maintenance and Construction Management

Page 22: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

18

Appendix C: Needs and Services Detail

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS01- Transit Vehicle Tracking

TR02 Provide real-time transitvehicle arrival/departureinformation

Transit agenciesprovide real-timevehicle arrival/departureinformation tocustomers viatravel informationsystems to assistwith their traveldecisions. Customers usereal-time arrival/departureinformation tomake mode androute choices.

Metro Transit hasreal-time next busarrival signs at 3locations. Metro Transit hasa web-based real-time bus scheduleinformationsystem (NexTrip). Metro Transit istesting bus arrivalinformation on itsTransitLine phoneinformationsystem to providereal-time andscheduled busarrival/departuretimes. Duluth TransitAuthority (DTA)currently providesreal-time arrivalinformation at 7locations withdynamic messagesigns. DTA willadd 14 locationsin the comingyear.

Complete the testand roll outTransitLine toprovide real-timebus scheduleinformation. Expand real-timetransit arrival timeand transit travel-time information. Integrate MetroTransit CAD/AVLsystem andRTMC togenerate andprovide real-timetransitinformation. Provide real-timetransit informationvia mobiledevices. Make informationsystems moreinteractive andcustomer-driven. Display real-timeinformationconsistentlybetween agenciesand systems toavoid confusion. Integrate real-time

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirinformationsystems.

Real-timevehicle arrivalsystems includeinterconnectsbetween in-vehicle GPS/AVL equipmentand transitmanagementcenters. Interconnectsbetween transitmanagementcenters andtravelerinformationsystems.

Vehicle traveltime andscheduleadherencedata shouldbe archivedforperformanceevaluationand analysis.

APTS08 ATMS06

Page 23: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

19

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

Packagetransit informationinto a Transit TripPlanning System. Display real-timetransit arrival/departureinformation viaDMS and webservice. Provide real-timetransit transferconnectioninformation onboard of transitvehicles.

TR05 Manage transitfleet andpersonneloperations

Transit agenciesmonitor vehiclelocations tomanageoperations andscheduleadherence and tooptimize futureoperations.

Most transitagencies useautomated vehiclelocation (AVL)systems on transitfleet vehicles andcomputer aideddispatch (CAD) tomanageresources.

Expand AVLdeployments. Integrate transitresources and/orinformationbetweenagencies.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirAVL systems.

AVL systemsincludeinterconnectsbetween in-vehicleequipment,transitoperationaldevices, andtransitmanagementcenters.

AVL data isarchived forfutureanalysis toimproveoperations.

Page 24: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

20

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR09 Measure

historicaltransit routeperformance

Transit agenciesmeasure andanalyze routeperformance toidentify areas toenhance serviceand improveoperations.

Many metro areaand local transitagencies alreadytrack routeperformance anduse in analysis oftransit operations.

Refine dataanalysis tools toevaluate routeperformancebased onarchived data. Refine tools tomanage archivedtransitperformance data.

Transit agenciesare responsibleto gather,manage,archive, andanalyze routeperformance fortheir system.

This serviceincludesinterconnectsbetween in-vehicleequipment andtransitmanagementcenters. Interconnectsbetween transitmanagementcenters andtransit dataarchives.

Keymeasures ofrouteperformancehave alreadybeen archivedfor futureanalysis andcomparison.

AD1

Page 25: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

21

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS02- Transit Fixed-Route Operations

TR15 Optimizescheduleefficiency

Transit agenciestrack routeperformance andanalyze scheduleefficiency. Transit agenciesuse performanceanalysis resultsand schedulingsoftware toimprove scheduleefficiency toprovide betterservice at a lowercost.

Many agenciesalready useschedulingsoftware toimproveoperationsefficiency. Other servicesthat supportscheduleadherence alsohave a secondaryaffect ofimprovingscheduleefficiency.

Enhanceschedulingsoftware. Coordinateimplementation ofrelated servicessuch as TR02 –provide real-timetransit vehiclearrival/departureinformation, TR04– coordinate timetransfer, TR10 –measure historicalrouteperformance, andTR18 - coordinatetransit vehiclemovements withtraffic controldevices.

Transit agenciesare responsibleto plan, design,construct,integrate,operate andmaintain theirsystems tooptimizeschedules.

Schedulingoptimizationsystemsincludesinterconnectsbetween historicroute databasesand schedulingsoftwaresystems.

None. Thisservice useskey historictravelinformationalreadyarchived.

Page 26: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

22

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS03- Demand Response Transit Operations

TR21 Provide on-linereservationsystem fordemand-responsivetransit

Demand-responsive transitagencies provideon-line services toallow customersto schedule pick-up and drop-off. Demand-response transitriders use on-lineservices toschedule pick-upsand drop-offs.

Many demand-responsive transitagenciesschedule servicesvia phone andweb.

Implement on-linereservationsystems onagency web-sitesand integratethem with fleetschedulingsystems. Dakota AreaResources andTransportation forSeniors (DARTS)plans toimplement an on-line reservationsystem. Integrate withfixed route tripplanning system.

Demand-responsivetransit agenciesare responsibleto plan, design,construct,integrate,operate andmaintain on-linereservationsystems.

Interconnectsbetween on-linereservation websites andschedulingsystems.

Servicerequests willbe archivedfor scheduleanalysis andrequesttracking.

Page 27: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

23

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS04- Transit Fare Collection Management

TR03 Provide simplefare paymentsystems

Transit agenciesuse simpleelectronic farepayment systemsto make it easierfor customers topay. Transit agenciesin the sameregion integratetheir fare paymentsystems to allowcustomers to usea single fare cardto ride on transitservices providedby differentagencies. Transit customerspay fare usingelectronic farecards.

Metro Transit iscoordinating farepayment betweenbus and railservices and withSuburban TransitProviders. U of M, MetroTransit, andDuluth TransitAuthority (DTA)have integratedtransit smartcards and StudentID cards for U ofM students andfaculty. St. Cloud MTC isexamining usingthe smart cardcapability. Businesses andMetro Transithave integratedtransit smart cardand MetroPass.

Coordinatepaymentintegrationbetween transitsystems. Allow credit cardpayment tosimplify paymentsystem and easilyallow charges foradditionalservices. Implement GoToCard customercheck balanceand add valuecapability to farepayment systems

Transit agenciesare responsibleto plan, design,construct,integrate,operate andmaintain theirpaymentsystems.

This serviceincludesinterconnectsbetween transittraveler cardsand in-vehicleelectronic fareboxes. Interconnectsbetween in-vehicleelectronic fareboxes andtransitoperationscenters. Interconnectsbetween farepayment systemand credit cardprocessingcenter. Interconnectsbetween farepayment systemand IVR phonesystem.

Transitcustomeraccounttransactionsshould bearchived forback-officeaccountmanagement.

Page 28: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

24

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR07 Provide

electronic farepayment card

Transit agenciesprovide electronicfare card tosimplify farecollection andreduce boardingtime. Customers useelectronic faresystem to quicklypay and boardvehicle. Transit agenciesuse electronicfare card asemployee securitycards / timecards.

Metro Transit hasimplemented Go-To Card forelectronic farepayment. St. Cloud MTC isexamining usingthe smart cardcapability. Metro Transit andDuluth TransitAuthority (DTA)uses transit smartcard for employeesecurity and dooraccess in additionto transit usage.

DTA is planningto use transitsmart card foremployee timeclockmanagement. Regional transitproviders plan touse electronicfare cards insame capacity asMetro Transit. Investigate theuse of electronicfare card to payfor parking Investigate theuse of electronicfare card forparatransit.

Transit agenciesare responsibleto plan, design,construct,integrate,operate andmaintain theirfare paymentsystem.

This serviceincludesinterconnectsbetween transittraveler cardsand in-vehicleelectronic fareboxes. Interconnectsbetween in-vehicleelectronic fareboxes andtransitoperationscenters.

Transitcustomeraccounttransactionsshould bearchived forback-officeaccountmanagement. Archiveelectronic farecard usageand bad listdata. Need centraldatabase toallow faremanagementacrossregionalproviders.

Page 29: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

25

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS05- Transit Security

TR06 Providesurveillanceandenforcementon transitvehicles andtransit facilities

Transit agenciesuse surveillanceto monitor and/ordetect suspiciousactivities, threatsor incidents ontransit vehicles,outside transitvehicles, and inand around transitfacilities. Transit agenciesshare surveillanceand information ofsuspiciousactivities, threats,and incidents withenforcementagencies.

St. Cloud MTC,Metro Transit, andDTA have videosurveillance ontheir buses. St. Cloud MTC isplanning anoperational test toenhance itssecurity features. Metro Transit hassurveillancesystems installedat transit centersand garages. DTA operatessurveillancesystems at transitcenters andgarages. Silent, driveractivated securityalert buttons invehicles.

Enhanceautomatedsurveillancemonitoring withalarms. Install secure,high capacity,wirelesscommunicationsbetweensurveillanceequipment andoperationscenters (videodownload togarage, center,and supervisorpersonnel Multi-agencyintegration ofsurveillance video(police, DOT,etc.). Upgrade analogcameras to digitalcameras.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirsurveillancesystems.

This serviceincludesinterconnectsbetween in-vehiclesurveillanceequipment/roadsidesurveillanceequipment andtransitmanagementcenter/enforcementagency (DOT,other transitagencies). Interconnectsbetween transitmanagementcenter andenforcementagency (DOT,other transitagencies).

Live videoshould be"buffered" fora period oftime to allowsaving videoof interestafter the fact. Video ofinterestshould bepermanentlysaved andcataloged fortraining, postincidentbriefing, andtort cases.

Page 30: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

26

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR14 Provide

security at parkand ride lots

Transit agenciesuse surveillanceto monitor andrecord suspiciousactivity at park-and-ride lots toimprove thesafety andsecurity ofcustomers andvehicle operators.

Some transitagencies alreadyuse cameras forsurveillance atpark-and-ride lots. Panic buttons andemergencyphones also existat select park-and-ride facilities.

Deploysurveillancecameras at morepark-and-ride lots. Integratemonitoring alertsystems withsurveillancesystems toautomatically alertagencies ofsuspiciousactivities. Upgrade analogcameras to digitalcameras.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirsurveillancesystems.

This serviceincludesinterconnectsbetweenroadsidesurveillanceequipment andtransitmanagementcenters.

Live videoshould be"buffered" fora period oftime to allowsaving videoof interestafter the fact. Video ofinterestshould bepermanentlysaved andcataloged fortraining, postincidentbriefing, andtort cases.

Page 31: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

27

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS06- Transit Fleet Management

TR08 Support vehiclediagnosticsandmaintenance

Transit agenciesuse sensors tomonitor vehicleusage andconditions andtransmit data tofleet managementsystems to issuediagnostic reportsand maintenancerequests. Fleetmanagementsystems processdata andschedulepreventative andcorrectivemaintenance. The systems alsoprovide personnelwith vehiclediagnostic andhistoricalmaintenance datafor use duringpreventativemaintenance andfor roadsideassistance calls.

Metro Transituses TxBaseinterface togenerate workorders whensome error codesare received. It isplanning a test ofwirelessdiagnostic datatransmission. St. Cloud entersall diagnostic datainto its fleetmanagementsystem. Duluth TransitAuthority (DTA)uses AVL systemfor diagnosticdata reporting andon-board sensorsfor preventativemaintenance. Transit agencieshave integratedvehicle monitoringequipment withautomateddiagnosticsystems.

Expandimplementation offleet managementsystems withautomateddiagnostic andschedulingcapabilities toother transitagencies.

Transit agenciesare responsibleto plan, design,construct,integrate,operate andmaintain theirvehiclemonitoring anddiagnosticsystems.

This serviceincludesinterconnectsbetween in-vehiclemonitoringequipment andfleetmanagement/diagnosticsystems.

Diagnosticandmaintenancehistory will bearchived foruse in futurevehiclemaintenanceand fleetmaintenanceanalysis.

Page 32: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

28

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR12 Optimize

garageoperations

Transit agenciesuse fleet/garagemanagementsystems toimprove efficiencyin vehicle storage,finding, andmaintenance.

Metro Transitemployeesperform bus“markup” bywalking the aislesin bus garagesand recording theposition of eachbus in the garagearea. Duluth TransitAuthority (DTA)staff assignstransit vehicles todrivers. Metro Transit isinstalling a garagebus locatorsystem to locatebuses while theyare parked ingarages.

Some transitagencies plan todeploy a garagebus locatorsystem to locatebuses primarilywhile they areparked on transitagency property.

Transit agenciesare responsibleto plan, design,deploy,integrate,operate andmaintain theirfleet/garagemanagementsystems.

The fleetmanagementsystems andgarage buslocator systemsincludeinterconnectsbetween in-vehiclesequipment andgarageoperationscenters Interconnectsbetween garageoperationscenters andtransitmanagementcenters.

None.

Page 33: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

29

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS07- Multi-modal Coordination

TR04 Coordinatetimed transfersbetween routesegments,providers &modes

Transit agenciesshare andcoordinate vehicleroutes andschedules tominimize waittimes and missedtransfers attransfer points. Transit agenciescoordinate withproviders of othermodes to improveservicecoordination andoperatingefficiency.

Metro Transituses software toprovide internaltimed transfers. Three transitagencies arecoordinatingservices incommon regionalcenters insouthwest andwest centralMinnesota Duluth TransitAuthority (DTA)uses AVL systemto coordinatetransfers betweenDTA routes. DTA uses GoogleTransit TripPlanning. MetroTransit andRegional TransitProviders will alsouse Google inSept. 2008.

Improveautomatedcoordinationamong transitproviders toexpand serviceand preventduplicating trips Alert transitdrivers/dispatcherswhetherpassengers arewaiting at a busstop. Reduceduplication ofroutes betweenfixed route anddemand-response Deploy GPS/AVLtechnology fortransit agencies ingreater MNtransit.

Transit agenciesare responsibleto communicateand coordinatewith each otherto improveservicecoordination. Coordinationbetweenregional transitproviders,county, andtransit planningstakeholders forgreater MN.

This serviceincludesinterconnectsbetween transitvehicles, transitmanagementcenters, andagencies. Interconnectsbetweendifferent transitmanagementcenters.

Historic routeperformanceand scheduleadherencedata shouldbe archived toassist inanalyzingvehiclesarrive/departtimes attransfer pointsand trippatterns/trends.

Page 34: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

30

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS08- Transit Traveler Information

TR01 Provide transitroute andscheduleinformation

Transit agenciesuse various travelinformationsystems toprovide route,schedule, andfare information tothe public. Transit customersuse route,schedule, andfare information tomaketime/route/modetravel decisions.

Many transitagencies provideroute, scheduleand fareinformation viawebsites or phonesystems as wellas printedschedules atstops. Metro Transitprovides a tripplanner serviceon its website. Duluth TransitAuthority (DTA)uses WebWatchsoftware thatinformscustomers via theInternet of theplanned transitdepartures frombus stops.

Enhance voicerecognition forautomated tripplanning. Implement routeplanning systemsfor agencies thatdo not have them(regional transitand countyproviders). Provide WiFiInternet accesspoints on trains. Install kiosks atkey transitstops/centers toprovideinformation andfor trip planning.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirtravelinformationsystems.

Transit travelerinformationsystems includeinterconnectsbetween transitschedulingsystems andwebsites, phonesystems, kiosksand otherinformationdistributionequipment.

Service usageshould betracked andarchived.

TR02 Provide real-time transitvehicle arrival/departureinformation

See information under APTS01

Page 35: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

31

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR10 Provide on-

boardautomatedenunciators

Transit agenciesuse on-boardenunciators toautomaticallyannounce stopsbased on vehiclelocations. Customer useenunciators todetermine whatstop the vehicle isat and whetherthey should getoff.

Metro Transit’slight rail systemuses on-boardautomatedenunciators toannounce nextstops/routes andsafety messages.Enunciators atLRT stations alsoprovide safetymessages. Duluth TransitAuthority (DTA)utilizes on-boardenunciators toannounce nextstops/routes andsafety messageson the interior andexterior of transitvehicles. Driverscan also activatea set of pre-defined messagesto address transitcustomers.

Deploy on-boardenunciators /visual displaysystems andintegrate themwith AVLsystems.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirautomatedenunciatorsystems / visualdisplay systems.

Enunciatorsystems includeinterconnectsbetween invehicleenunciators andin-vehicle AVLequipment.

None.

Page 36: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

32

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR11 Provide

information tothe ADAcommunity

Transit agenciesuse websites,telephoneservices, printedmaterials, media,and other meansto provide transitservice and fareinformation toADAcommunities. The travelerinformationsystems providedby transitagencies shallmeet Section 508of the U.S.Rehabilitation Actof 1973. ADA communitiesobtain informationon transitavailability,routes, schedule,fare, vehicletypes, andaccessibilityoptions.

Transit agenciescurrently providevehiclewheelchairaccessibilityinformation viapublic websitesand brochures. Provision of on-board enunciatorsby Metro Transitand DTA provideautomatedinformation toADA community.

Develop/updatetransit agencywebsites to meetaccessibilityrequirements asrequired bySection 508. Coordinate withsolutions toaddressneeds/services ofTR01 – providetransit route,schedule and fareinformation andTR11 – provideon-boardautomatedenunciators.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirtravelinformationsystems.

Transit travelinformationsystems includeinterconnectsbetween transitmanagementcenters andwebsites, phonesystems, kiosksand otherinformationdistributionequipment.

None.

Page 37: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

33

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR16 Provide

information onridesharingopportunities

Transit agenciesprovide transitand ridesharinginformation tocustomers toassist them withtravel decisionsand interagencytrip coordination. Customers usethis information toobtain rideshareinformation andform carpools.

Agencies provideinformation ontransit andcarpoolingopportunities ontheir websites orphone informationsystems. Metro Transitprovidesrideshareinformation on itsweb site and hason-line carpooland vanpoolmatchingcapabilities.

Enhance carpooland vanpoolridematchingsystem. Opportunities forcoordination ofexisting transitservice in greaterMN with city,county, andregional transitproviders.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theircarpool/vanpoolridematchingsystems.

None. None. ATIS08

Page 38: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

34

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR20 Provide real-

time transferinformation totravelers enroute

Transit agenciesprovide real-timetransferinformation tocustomers “enroute” to assistwith their traveldecisions,regardless oftravel mode. Customers usereal-time arrivalinformation tomake transferdecisions.

Metro Transit hasreal-time next busarrival signs at 3locations. Duluth TransitAuthority (DTA)currently providesreal-time arrivalinformation at 7locations withdynamic messagesigns. DTA willadd 14 locationsin the comingyear. Beta testing ofNexTrip on MetroTransit website,phone, and PDA.

Integrate MetroTransit CAD/AVLsystem withRTMC togenerate real-timeinformation. Provide real-timenext bus arrivaland transferinformation attransit centersand transferpoints. Provide next busarrival time atdecision points onfreeways andmajor arterials. Provide real-timeinformation tocustomers enroute. Add rail modeinformation toNexTrip. Integrate St.Cloud transitinformation intoNexTrip.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirAVL and real-time informationsystems.

Transferinformationsystems includeinterconnectsbetween in-vehicle AVLsystems andtransitmanagementcenters. Interconnectsbetweenoperationscenters androadside andportable travelerinformationequipment.

None. Transitarrival archivedata isarchived aspart of theCAD/AVLservice.

Page 39: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

35

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package APTS09- Transit Signal Priority

TR17 Coordinatetransit vehiclemovementswith trafficcontrol devices

Transit agencieswill use transitsignal priority(TSP) to increasescheduleadherence andimprove transitspeed and triptime reliability forcustomers.

Many signalizedintersections inmany cities areequipped withemergencyvehiclepreemption (EVP) St. Cloud MTCcurrently operatesTSP at selectintersections.

Deploy TSP alongtwo north-southarterial corridorsand near park-and-ride locationsalong I-35Wcorridor as pilotproject. If successful,deploy TSP alongother key transitcorridors.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirTSP systems. Local trafficcontrol agenciesare responsibleto operate andmaintain trafficsignals. Transit agenciesare responsibleto coordinatewith local trafficcontrol and lawenforcementagencies.

TSP systemsincludesinterconnectsbetween transitvehicles,roadside signalcontrolequipment, anda transitmanagementcenter.

Vehicle traveltime andscheduleadherencedata shouldbe archivedas part ofCAD/AVLservice forperformanceevaluationand analysis.

TR19 Provide queuejumping

Transit agenciesuse queuejumping to allowtransit vehiclespreferred accessto reduce traveltime and enhancescheduleadherence.

Buses currentlyhave access toHOV bypasslanes at someramp locations inthe metro areaand have anexception for turnlanes.

Test andimplement queuejump systems atselected bottlenecked areas. Implement queuejumps along withTSP to improveoperationsefficiency.

Transit agenciesare responsibleto coordinatewith Mn/DOTand localagencies toplan, design,construct,operate andmaintain theirqueue jumpsystems.

None. None.

Market Package APTS10- Transit Passenger CountingMany transit agencies have automated passenger counters installed in their transit vehicles. No additional needs or services in this area were identified bystakeholders.

Page 40: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

36

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageMarket Package AVSS03- Longitudinal Safety Warning1

TR13 Providecollisionavoidanceassistance fortransit vehicles

Transit vehicledrivers usecollisionavoidancesystems tomonitor the areasaround thevehicles, detectpotential hazards,and receivewarnings whenhazardousconditions arepresent. Transit driversuse on-boardsafety sensorsand collisionsensors tomonitor the areasto the sides ofvehicles as busesare merging intoand out ofshoulder lanesand bus stops. Warnings aboutpotential hazardsare presented totransit drivers.

Vehicle collisionwarning systemshave been testedin several states,includingMinnesota.

Test and deployGPS system forbus-only shoulderlane use driverassistance. Test and deploylateral safetydetection andwarning systemsto improve safetyof buses merging. Test and deploycollision warning/avoidancesystems onbuses.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theircollisionwarning/avoidancesystems on theirfleet vehicles. Transit agenciesare responsibleto plan, design,construct,operate andmaintain theirlateral safetydetection andwarning systemson their fleetvehicles.

Lateral safetydetection andwarning systemsas well ascollisionwarning/avoidancesystems includeinterconnectsbetween in-vehicle safetyand collisiondetectionequipment andin-vehiclewarningequipment. Interconnectsbetween in-vehicle detectionequipment andin-vehicle driverfeedbackequipment.

None. AVSS04

1 Description of AVSS03 – Longitudinal Safety Warning: This market package allows for longitudinal warning. It utilizes safety sensors and collision sensors.It requires on-board sensors to monitor the areas in front of and behind the vehicle and present warnings to the driver about potential hazards.

Page 41: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

37

ID Need/Service OperationalConcept

ExistingCapability

Gap/PlannedEnhancement

Role/Responsibility Interconnect Archive Need

AssociatedMarket

PackageTR18 Install

pedestriandetection/warningsystem toreduceincidents

The detection andwarning systemdetectspedestrians inobstructed viewarea. Transit driversreceive alerts ofpedestrians inobstructed viewareas.

Some garage andtransit stationentry/exit wayshave static anddynamicpedestrianwarning systems. No currentsystems providein-vehiclewarnings todrivers.

Test and deployon-boardpedestriandetection/warningsystems. Test and deployroadsidepedestrianwarning systemsat areas with highpedestrianaccident rates.

Transit agenciesare responsibleto plan, design,construct,operate andmaintain theiron-boardpedestriandetection andwarningsystems. Local trafficagencies areresponsible toplan, design,construct,operate andmaintainroadsidesignage.

Pedestriandetection andwarning systemsincludeinterconnectsbetween in-vehicle detectionequipment andin-vehiclewarningequipment. Interconnectsbetweenroadsidedetection andwarningequipment andin-vehiclewarningequipment.

Warningsactivationdata will bearchived forfuture systemanalysis andtort claims.

Market Package AVSS04- Lateral Safety Warning2

TR13 Providecollisionavoidanceassistance fortransit vehicles

See information under AVSS03

2 Description of AVSS04 – Lateral Safety Warning: This market package allows for lateral warning. It utilizes safety sensors and collision sensors. It requireson-board sensors to monitor the areas to the sides of the vehicle and present warnings to the driver about potential hazards.

Page 42: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

38

Appendix D: APTS Market Packages and DescriptionsThe descriptions of APTS market packages are taken directly from the National ITS Architectureversion 6.0.

APTS01-Transit Vehicle TrackingThis market package monitors current transit vehicle location using an Automated VehicleLocation System. The location data may be used to determine real time schedule adherenceand update the transit system’s schedule in real-time. Vehicle position may be determined eitherby the vehicle (e.g., through GPS) and relayed to the infrastructure or may be determineddirectly by the communications infrastructure. A two-way wireless communication link with theTransit Management Subsystem is used for relaying vehicle position and control measures.Fixed route transit systems may also employ beacons along the route to enable positiondetermination and facilitate communications with each vehicle at fixed intervals. The TransitManagement Subsystem processes this information, updates the transit schedule and makesreal-time schedule information available to the Information Service Provider.

APTS02-Transit Fixed-Route OperationsThis market package performs automated dispatch and system monitoring for fixed-route andflexible-route transit services. This service performs scheduling activities including the creationof schedules, blocks and runs, as well as operator assignment. This service determines thetransit vehicle trip performance against the schedule using AVL data and provides informationdisplays at the Transit Management Subsystem. Static and real time transit data is exchangedwith Information Service Providers where it is integrated with that from other transportationmodes (e.g. rail, ferry, air) to provide the public with integrated and personalized dynamicschedules.

APTS03-Demand Response Transit OperationsThis market package performs automated dispatch and system monitoring for demandresponsive transit services. This service performs scheduling activities as well as operatorassignment. In addition, this market package performs similar functions to support dynamicfeatures of flexible-route transit services. This package monitors the current status of the transitfleet and supports allocation of these fleet resources to service incoming requests for transitservice while also considering traffic conditions. The Transit Management Subsystem providesthe necessary data processing and information display to assist the transit operator in makingoptimal use of the transit fleet. This service includes the capability for a traveler request forpersonalized transit services to be made through the Information Service Provider (ISP)Subsystem. The ISP may either be operated by a transit management center or beindependently owned and operated by a separate service provider. In the first scenario, thetraveler makes a direct request to a specific paratransit service. In the second scenario, a thirdparty service provider determines that the paratransit service is a viable means of satisfying atraveler request and makes a reservation for the traveler.

APTS04-Transit Fare Collection ManagementThis market package manages transit fare collection on-board transit vehicles and at transitstops using electronic means. It allows transit users to use a traveler card or other electronicpayment device. Readers located either in the infrastructure or on-board the transit vehiclesallow electronic fare payment. Data is processed, stored, and displayed on the transit vehicleand communicated as needed to the Transit Management Subsystem. Two other marketpackages, ATMS10: Electronic Toll Collection and ATMS16: Parking Facility Management also

Page 43: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

39

provides electronic payment services. These three market packages in combination provide anintegrated electronic payment system for transportation services.

APTS05-Transit SecurityThis market package provides for the physical security of transit passengers and transit vehicleoperators. On-board equipment is deployed to perform surveillance and sensor monitoring inorder to warn of potentially hazardous situations. The surveillance equipment includes video(e.g., CCTV cameras), audio systems and/or event recorder systems. The sensor equipmentincludes threat sensors (e.g., chemical agent, toxic industrial chemical, biological, explosives,and radiological sensors) and object detection sensors (e.g., metal detectors). Transit user ortransit vehicle operator activated alarms are provided on-board. Public areas (e.g., transit stops,park and ride lots, stations) are also monitored with similar surveillance and sensor equipmentand provided with transit user activated alarms. In addition this market package providessurveillance and sensor monitoring of non-public areas of transit facilities (e.g., transit yards)and transit infrastructure such as bridges, tunnels, and transit railways or bus rapid transit (BRT)guideways. The surveillance equipment includes video and/or audio systems. The sensorequipment includes threat sensors and object detection sensors as described above as well as,intrusion or motion detection sensors and infrastructure integrity monitoring (e.g., rail trackcontinuity checking or bridge structural integrity monitoring).

The surveillance and sensor information is transmitted to the Emergency ManagementSubsystem, as are transit user activated alarms in public secure areas. On-board alarms,activated by transit users or transit vehicle operators are transmitted to both the EmergencyManagement Subsystem and the Transit Management Subsystem, indicating two possibleapproaches to implementing this market package.

In addition the market package supports remote transit vehicle disabling by the TransitManagement Subsystem and transit vehicle operator authentication.

APTS06-Transit Fleet ManagementThis market package supports automatic transit maintenance scheduling and monitoring. On-board condition sensors monitor system status and transmit critical status information to theTransit Management Subsystem. Hardware and software in the Transit ManagementSubsystem processes this data and schedules preventative and corrective maintenance. Themarket package also supports the day to day management of the transit fleet inventory,including the assignment of specific transit vehicles to blocks.

APTS07-Multi-modal CoordinationThis market package establishes two way communications between multiple transit and trafficagencies to improve service coordination. Multimodal coordination between transit agencies canincrease traveler convenience at transit transfer points and clusters (a collection of stops,stations, or terminals where transfers can be made conveniently) and also improve operatingefficiency. Transit transfer information is shared between Multimodal Transportation ServiceProviders and Transit Agencies.

APTS08-Transit Traveler InformationThis market package provides transit users at transit stops and on-board transit vehicles withready access to transit information. The information services include transit stop annunciation,imminent arrival signs, and real-time transit schedule displays that are of general interest totransit users. Systems that provide custom transit trip itineraries and other tailored transitinformation services are also represented by this market package.

Page 44: Minnesota Statewide Regional ITS Architecture · 2011-01-10 · Minnesota Statewide Regional ITS Architecture Version 2009 Volume 4: Advanced Public Transportation Systems 2 Previously

Minnesota Statewide Regional ITS Architecture Version 2009Volume 4: Advanced Public Transportation Systems

40

APTS09-Transit Signal PriorityThis market package determines the need for transit priority on routes and at certainintersections and requests transit vehicle priority at these locations. The signal priority mayresult from limited local coordination between the transit vehicle and the individual intersectionfor signal priority or may result from coordination between transit management and trafficmanagement centers. Coordination between traffic and transit management is intended toimprove on-time performance of the transit system to the extent that this can be accommodatedwithout degrading overall performance of the traffic network.

APTS10-Transit Passenger CountingThis market package counts the number of passengers entering and exiting a transit vehicleusing sensors mounted on the vehicle and communicates the collected passenger data back tothe management center. The collected data can be used to calculate reliable ridership figuresand measure passenger load information at particular stops.