ITS Architecture Main Document - Indianapolis Metropolitan ...

Indianapolis Metropolitan Planning Area Regional
Intelligent Transportation System (ITS) Architecture
FINAL REPORT
Version 3.0
February 1, 2012
Originally Prepared By
Updated by Justin Stuehrenberg
for
Indianapolis Metropolitan Planning Organization

Regional ITS
Architecture
Issue No.
Regional ITS
Architecture
Issue Date
Document Revision History
National ITS
Architecture
Version
Turbo
Architecture®
Software
Version
Comment
1.0 July 20, 2005 5.0 3.0 Initial release
1.1 July 20, 2007 5.1 3.1
National Architecture/
Turbo Architecture®
update
2.0 January 3, 2008 5.1 3.1
2.1
3.0
February 6,
2008
February 1,
2012
6.0 4.0
6.1 5.0
First regular architecture
update
National Architecture/
Turbo Architecture®
update
Second regular
architecture update
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
i

Table of Contents
1.0 Introduction ........................................................................................................................ 1
1.1 Geographic Area ............................................................................................................ 1
1.2 Timeframe ...................................................................................................................... 1
1.3 Service Scope ................................................................................................................. 1
1.4 Stakeholders ................................................................................................................... 1
2.0 Inventory ............................................................................................................................ 4
2.1 Systems .......................................................................................................................... 5
2.2 Needs and Services ...................................................................................................... 16
3.0 Concept of Operations ...................................................................................................... 28
3.1 Vision Statement .......................................................................................................... 28
3.2 Role and Responsibility Areas ..................................................................................... 28
4.0 Functional Requirements .................................................................................................. 40
5.0 Interfaces and Information Flows ..................................................................................... 50
6.0 Project Sequencing ........................................................................................................... 52
7.0 Agreements ....................................................................................................................... 54
8.0 Standards .......................................................................................................................... 58
9.0 Use of the Architecture ..................................................................................................... 62
9.1 Planning ....................................................................................................................... 62
9.2 Project Development and Implementation ................................................................... 62
10.0 Architecture Maintenance Plan ........................................................................................ 64
10.1 Who Will Maintain the Architecture? .......................................................................... 64
10.2 What Will Be Maintained? .......................................................................................... 65
10.3 How Will It Be Maintained? ........................................................................................ 65
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
ii

List of Tables
Table 1 Architecture Requirements Reference .............................................................................. ix
Table 2 Architecture Stakeholder List ............................................................................................ 3
Table 3 Indianapolis ITS Systems Inventory ................................................................................. 6
Table 4 Indianapolis Market Packages (Transportation Services) Inventory ............................... 17
Table 5 Archived Data Management Roles and Responsibilities ................................................ 29
Table 6 Emergency Management Roles and Responsibilities ...................................................... 30
Table 7 Emissions Management Roles and Responsibilities ....................................................... 32
Table 8 Freeway Management Roles and Responsibilities .......................................................... 32
Table 9 HAZMAT Response Roles and Responsibilities ............................................................ 32
Table 10 Incident Management Roles and Responsibilities ......................................................... 34
Table 11 Maintenance and Construction Roles and Responsibilities ........................................... 35
Table 12 Parking Management Roles and Responsibilities ......................................................... 36
Table 13 Surface Street Management Roles and Responsibilities ............................................... 37
Table 14 Transit Services Roles and Responsibilities .................................................................. 38
Table 15 Transportation Security Roles and Responsibilities ...................................................... 38
Table 16 Traveler Information Roles and Responsibilities .......................................................... 39
Table 17 Indianapolis Equipment Packages (Functional Areas) Inventory ................................. 40
Table 18 Indianapolis ITS Projects Inventory .............................................................................. 52
Table 19 Indianapolis ITS Agreements Inventory ....................................................................... 55
Table 20 Indianapolis ITS Standards Inventory ........................................................................... 59
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
iii

List of Figures
Figure 1 Architecture Development Process Diagram ................................................................... x
Figure 2 Indianapolis Metropolitan Planning Area ........................................................................ 2
Figure 3 Indianapolis Subsystem Interconnect Diagram ................................................................ 5
Figure 4 Network Surveillance Market Package Diagram ........................................................... 17
Figure 5 Indianapolis Subsystem Interconnect Diagram .............................................................. 50
Figure 6 Indianapolis Subsystem Interconnect Diagram .............................................................. 51
Figure 7 Standard Systems Engineering Diagram ........................................................................ 63
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
iv

List of Appendices
A
B
C
D
E
F
G
H
I
Inventory of Existing Documentation
Project Outreach Summary
Stakeholder List
Stakeholder Survey Template
Telephone Interview Template
Stakeholder Workshop Notes
Interconnect Diagrams
Detailed Regional ITS Project List
Submitted Change Request Forms
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
v

List of Terms
AASHTO
ASTM
AVL
CCTV
CMAQ
CTASC
DMS
DPW
EDP
EMS
EPA
EV
FAA
FHWA
FSP
FTA
GIS
HAR
HAZMAT
HRI
IAA
IDI
IEEE
IFD
IMS
INDOT
IPD
IPS
IPTC
IRTC
IRTIP
ISP
ITE
ITS
ITSSP
UIPUI
MACC
MCM
MCO
MCS
MCV
MECA
MOU
MPA
IMPO
NEMA
NTCIP
RFP
CIRTA
American Association of State Highway and Transportation Officials
American Society for Testing and Materials
Automatic Vehicle Locationing
Closed Circuit Television
Congestion Mitigation and Air Quality
Indiana Counterterrorism and Security Council
Dynamic Message Signs
Department of Public Works
Early Deployment Plan
Emergency Medical Services
Environmental Protection Agency
Emergency Vehicle
Federal Aviation Administration
Federal Highway Administration
Freeway Service Patrol
Federal Transit Authority
Geographic Information Systems
Highway Advisory Radio
Hazardous Materials
Highway Rail Intersection
Indianapolis Airport Authority
Indianapolis Downtown, Inc.
Institute of Electrical and Electronics Engineers
Indianapolis Fire Department
Indianapolis Motor Speedway
Indiana Department of Transportation
Indianapolis Police Department
Indianapolis Public Schools
Indianapolis Public Transportation Corporation
Indianapolis Regional Transportation Council
Indianapolis Regional Transportation Improvement Program
Indiana State Police/Information Service Provider
Institute of Transportation Engineers
Intelligent Transportation Systems
Indiana Department of Transportation ITS Strategic Plan
Indiana University/Purdue University at Indianapolis
Multi-Agency Command Center
Maintenance and Construction Management
Maintenance and Construction
Marion County Sheriff
Maintenance and Construction Vehicle
Metropolitan Emergency Communications Agency
Memorandum of Understanding
Metropolitan Planning Area
Indianapolis Metropolitan Planning Organization
National Electrical Manufacturer’s Association
National Transportation Communications for ITS Protocol
Request for Proposals
Central Indiana Regional Transportation Authority
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
vi

LRTP
RWIS
SAE
Safetea-LU
SDO
INSTIP
STP
TEA-21
TCIP
TIP
TMC
TSA
USDOT
Indianapolis Long-Range Transportation Plan
Road Weather Information Systems
Society of Automotive Engineers
Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for users
Standards Development Organization
Indiana Statewide Transportation Improvement Program
Surface Transportation Program
Transportation Equity Act for the 21 st Century
Transit Communications Interface Profile
Transportation Improvement Program
Traffic Management Center
Transportation Safety Administration
United States Department of Transportation
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
vii

Foreword
Intelligent transportation systems (ITS) are the integrated application of various technologies and
management strategies to provide traveler information to increase the safety and efficiency of the
surface transportation system. This ITS architecture document represents the next in a series of
steps intended to chart a course for ITS in the greater Indianapolis area.
A regional ITS architecture is a framework for describing, planning, and implementing intelligent
transportation systems. It is intended to promote integration between stakeholders by providing a
common framework under which stakeholders in a region can build intelligent transportation
systems. Once implemented, these systems can combine to increase the safety and efficiency of
the surface transportation system.
As a further incentive for the development of regional ITS architectures, the
Federal Highway Administration (FHWA) developed a Rule and the Federal
Transit Authority (FTA) developed a parallel Policy to enact Section 5206(e) of the
Transportation Equity Act for the 21 st Century (TEA-21) in April of 2001. This
Rule/Policy states that, in order to receive funding through the Highway Trust
Fund, any region in the United States that has deployed or will soon deploy ITS
projects must have developed a regional ITS architecture by April 8, 2005. With the
significant number of ITS projects at various stages of implementation, Indianapolis
certainly falls within this category.
Table 1 provides a reference for each of the FHWA/FTA Rule/Policy requirements, and the
manner in which they are addressed in this Architecture Document.
The FHWA has provided a number of resources to assist architecture developers around the
country with their task. First, the FHWA created the National ITS Architecture as a guide for the
development of regional ITS architectures (www.iteris.com/itsarch/). Now in its sixth version,
the National ITS Architecture provides architecture developers with a common vocabulary,
promoting the integration and interoperability of ITS systems. The FHWA’s “Regional ITS
Architecture Guidance Document” (Oct. 12, 2001) elaborates on the Rule/Policy, providing
recommendations for each stage of architecture development (see Figure 1). In addition, the
FHWA developed Turbo Architecture® software as a tool for assembling, organizing, and
displaying the information necessary to create and use an ITS architecture.
As the architecture “champions,” the Indianapolis Metropolitan Planning Organization (MPO)
and INDOT have led the effort to bring stakeholders together to create this Indianapolis Regional
ITS Architecture, and will be responsible for the ongoing use and maintenance of this
architecture. This work has been performed in close coordination with INDOT’s concurrent
development of the Indiana Statewide ITS Architecture, which serves as a link between the
thirteen regional ITS architectures across Indiana.
Overall, this Indianapolis Regional ITS Architecture is intended to promote continued
improvements in the movement of goods and people throughout the region through the
implementation of ITS strategies, technologies, and projects. Most importantly, the deployment
of these ITS strategies, technologies, and infrastructure will help to make the metropolitan
Indianapolis transportation system safer, better coordinated, and more efficient. In addition, by
taking a cooperative multi-agency approach, the MPO and partner agencies will be able to better
integrate ITS related efforts beyond their boundaries, pool funds, and deploy ITS technologies
and projects that benefit not only the Indianapolis region, but the entire State of Indiana.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
viii

Table 1 Architecture Requirements Reference
ITS Architecture Requirement
Architecture Scope and Region Description
Stakeholder Identification
System Inventory
Needs and Services
Operational Concept
Functional Requirements
Interfaces/Information Flows
Project Sequencing
Agreements
Standards Identification
Using the Regional ITS Architecture
Maintenance Plan
Report Section Addressing Requirement
The geographic area, timeframe, and service
scope of the Indianapolis Architecture are
provided in Sections 1.1 - 1.3 of this document.
A listing of stakeholders can be found in
Section 2.1 and Appendix C of this document.
Section 2.1 contains a complete systems
inventory (subsystems and terminators).
Section 2.2 identifies those needs identified by
the stakeholders, as well as a listing of existing
and planned services (market packages).
The operational concept for Indianapolis is
defined in Section 3.0 of this document.
The functional requirements of the Indianapolis
Architecture are listed in Section 4.0 of this
document.
Interfaces and information flows are described
in Section 5.0 of this document. Individual
interconnect diagrams are contained in
Appendix G.
A listing of ITS projects and their anticipated
sequence are addressed in Section 6.0 of this
document.
A listing of existing and planned agreements is
included in Section 7.0 of this document.
Applicable ITS Standards are included in
Section 8.0 of this document.
Section 9.0 describes the manner in which the
Indianapolis ITS Architecture can be used to
plan, design, and deploy ITS projects in the
region.
Section 10.0 outlines the tasks associated with
maintaining the architecture.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
ix

Figure 1 Architecture Development Process Diagram
Indianapolis Regional Intelligent Transportation System (ITS) Architecture
FINAL REPORT, Version 3.0
x

1.0 Introduction
Before creating an ITS architecture, it is necessary to define the general parameters of the
architecture. These parameters include the geographic area, timeframe, service scope, and
involved stakeholders of the architecture. Setting these architecture boundaries leads to the tasks
in subsequent steps.
1.1 Geographic Area
The Indianapolis metropolitan planning area (MPA) also serves as the geographic region for the
Indianapolis regional ITS architecture. This area, depicted in Figure 2, includes all of Marion
County and portions of Hamilton, Boone, Hendricks, Johnson, Hancock, and Shelby counties.
The Indianapolis MPA borders the Madison County MPA, located to the northeast of
Indianapolis.
The Indianapolis MPA was chosen to define the ITS architecture boundary for several reasons.
First, the Indianapolis MPO staff focuses on this area for overall transportation planning
processes, of which ITS is a subset. This will allow ITS planning to mirror the larger
transportation planning effort. Also, the MPA is a good starting point for future expansion as the
Indianapolis metropolitan area grows and ITS projects are planned and deployed outside of its
current boundaries. In addition, it is important to note that, with the recent designation of
Indianapolis as a non-attainment area by the Environmental Protection Agency (EPA), the
Indianapolis ITS Architecture must remain cognizant of air quality boundaries and adapt to
address the geographic nature of these boundaries.
1.2 Timeframe
For the purposes of this architecture, the timeframe has been set at ten (10) years from the date of
this document, or 2021. Defining an architecture timeframe provides a basis for determining the
status of ITS systems, services, and interconnections, as identified in later steps.
1.3 Service Scope
Before delving into the particular ITS services that are found in the greater Indianapolis area
(described in detail in Section 2.0), it should be noted that several statewide ITS services have
been excluded from this regional architecture and are instead contained within the Statewide
Indiana ITS Architecture. These include commercial vehicle services (beyond hazardous material
response), and other ITS services that are administered from a single statewide agency, such as
the Department of Motor Vehicles, the Department of Natural Resources, and the Department of
Revenue.
1.4 Stakeholders
From the onset of architecture development, every effort was made to include as many ITS
stakeholders as possible (see Appendix B). This outreach process resulted in a stakeholder group
comprised of a comprehensive list of surface transportation agencies and organizations. Below in
Table 2 is a listing of these stakeholders with descriptions as designated in the Turbo
Architecture® database.
As shown in Table 2, some stakeholders are explicitly identified in the architecture (e.g.,
‘Indianapolis Department of Public Works’), while others are combined within a general
stakeholder designation (e.g., ‘Suburban Municipalities’). This was done to include as many ITS
stakeholders as possible while keeping the architecture to a manageable size.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 1
FINAL REPORT, Version 3.0

Figure 2 Indianapolis Metropolitan Planning Area
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 2
FINAL REPORT, Version 3.0

Stakeholder Name
Ambulance/Emergency
Services
Central Indiana Regional
Transportation Authority
City of Beech Grove
City of Lawrence
City of Southport
Event Promoters/Special
Events
IIFC Executive Committee
Indiana Department of
Transportation
Indiana Department of
Transportation District Level
Indiana State Police
Indianapolis Airport
Authority
Major Sporting Event Venues
Indianapolis Department of
Public Works
Indianapolis Downtown, Inc.
Indianapolis Emergency
Management Agency
Indianapolis Fire Department
Indianapolis Metropolitan
Police Department
Table 2 Architecture Stakeholder List
Stakeholder Description
Rural/Metro Ambulance, Wishard Ambulance
Planning and implementation of mass transit services
Adjoining municipality (excluded from Unigov)
Adjoining municipality (excluded from Unigov)
Adjoining municipality (excluded from Unigov)
Includes: Indiana Black Expo, Indiana Sports Corporation, Indianapolis
Convention and Visitors Association, Indianapolis 500 Festival, NCAA
Headquarters, O’Reilly Raceway Park
Indiana Intelligence Fusion Center (IIFC) Executive Committee, provides
policy development, administrative guidance, and oversight to the IIFC, a
division of the Indiana Department of Homeland Security
State agency responsible for statewide road network including ITS
functions
Represents portions of INDOT's Greenfield, Crawfordsville, and Seymour
Districts, including all of the Indianapolis Subdistrict.
ISP Districts 51, 52, 53, Capitol Police
Provides incoming and outgoing air flights to Indianapolis
Indianapolis Capital Improvements Board (owner of the new Lucas Oil
Stadium) and Pacers Sports and & Entertainment (owner of the Conseco
Fieldhouse)
Maintains public infrastructure (including streets, sewers, bridges, and
traffic systems) and manages municipal solid waste collection and
disposal. DPW also ensures a healthy, safe, and natural environment (air,
land, and water). Includes six divisions: Policy and Planning,
Engineering, Operations, Solid Waste Management Section, Maintenance
Operations Section, and Storm/Wastewater Management Section.
Not-for-profit organization formed to develop, manage and market
Downtown Indianapolis.
Emergency Management is responsible for planning for all hazards that
threaten the community, whether natural, or man-made
Indianapolis Fire Department, includes Washington and Warren Township
Fire Departments
Indianapolis Metropolitan Police Department (includes the former
Indianapolis Police Department and the former Marion County Sheriff
Department)
Indianapolis Motor Speedway Host of major racing events including the Indy 500
Indianapolis MPO
Indianapolis Public
Transportation
Corporation/IndyGo
Indianapolis Schools
Major Employers
MECA
Indianapolis Metropolitan Planning Organization, part of the Department
of Metropolitan Development, Metropolitan Planning Organization
Division. Includes the IRTC.
The public transportation agency for the City of Indianapolis
Includes Indianapolis Public Schools (IPS), the state’s largest school
district, serving more than 39,000 students in 79 schools. Also includes 8
township school districts and private schools.
Eli Lilly & Co.
Metropolitan Emergency Communications Agency - governing body of
the Consolidated City of Indianapolis and Marion County public safety
communications systems and computer facilities district
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 3
FINAL REPORT, Version 3.0

Stakeholder Name
Stakeholder Description
Represents the government agencies in Marion County and surrounding
MECA System Users*
counties and suburban municipalities that utilize the MECA radio system
Media Services
Includes television, radio, and print media
Provider of highly customized, site-specific weather forecasting and
Meridian Environmental
analysis services to people anywhere, anytime, via state of the art Internet,
Technology
wireless, and cellular technologies
National Weather Service US agency responsible for national and local weather forecasting
Private Maintenance Private maintenance contractors who perform maintenance on regional
Companies
signal systems, HAR, DMS, lighting systems, and pumping stations
Railroad Agencies
Passenger and freight rail organizations
Clarian Health Partners (Methodist Hospital, Indiana University Hospital,
Regional Hospitals
and the Riley Hospital for Children), Health and Hospital Corporation of
Marion County, St. Francis, Community Hospital, St. Vincent
INDOT and the Indianapolis DPW co-own RWIS stations in the
RWIS Users*
Indianapolis region.
Street departments/public works, police, fire, and emergency
communications for the following suburban municipalities: Town of
Avon, City of Carmel, City of Greenwood, Town of Plainfield, Town of
Suburban Municipalities
Cumberland, Town of Brownsburg, Town of Zionville, Town of New
Whiteland, Town of Fishers, Town of Whiteland, City of Franklin, City of
Noblesville, City of Westfield
Represents highway, sheriffs, fire departments, emergency management,
and 911 centers in counties within the metropolitan planning area
Surrounding Counties
surrounding Marion County, including Boone, Hamilton, Hancock,
Hendricks, Johnson, Morgan, and Shelby Counties
Includes over 45 private taxicab companies serving the Indianapolis
Taxi Companies
region.
Towing Operators
Represents private towing companies operating in the region
Town of Speedway
Adjoining municipality (excluded from Unigov)
Traffic Data Archive Users
Stakeholders with a need to access proposed online Traffic Data Archive.
Group*
Traveling Motorists
Represents the motoring public
Indiana University/Purdue University at Indianapolis (IUPUI), Purdue
Universities
University, Butler University, University of Indianapolis, Ivy Tech and
other major institutions in the region
Local utility providers, including IPL, Citizens Gas and Indianapolis
Utility Companies
Water Company
* Turbo Architecture “stakeholder group”
Appendix C provides a comprehensive listing of all of the project stakeholders and primary
contacts for each agency/organization.
Due to its recent formation, following is a brief description of the Central Indiana Regional
Transportation Authority:
The Indianapolis City-Marion County Council has recently created
the Central Indiana Regional Transportation Authority (CIRTA) to
oversee the planning and implementation of transit services in the
region. Initially, the RTA will focus on the development of rapid
transit, particularly the Northeast Corridor from Noblesville to downtown Indianapolis.
2.0 Inventory
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 4
FINAL REPORT, Version 3.0

Intelligent transportation systems have been employed in the Indianapolis region for a number of
years. To build a foundation for the Indianapolis ITS Architecture, a research effort was
undertaken to collect and analyze the numerous ITS-related documents that have been created todate.
Summarized in Appendix A, these documents record the progress of ITS planning and
deployment in the region.
These documents, along with the results of the stakeholder outreach process, provide the ITS
inventory that serves as the starting point for this ITS architecture.
2.1 Systems
A ‘system’ can be defined as:
A collection of hardware, software, data, processes, and people that work together to
achieve a common goal.
In the realm of ITS, a system corresponds to the resources of a surface transportation agency. In
general, these resources can be categorized as either centers (e.g., Traffic Management Center),
field elements (e.g., freeway surveillance devices), vehicles (e.g., transit vehicles), or devices that
interact with travelers (e.g., traveler information website). The National ITS Architecture
includes entities (‘subsystems’ and ‘terminators’) that correspond to the real-world examples
previously given. Figure 3 displays the National ITS Architecture Subsystem Interconnect
Diagram, which shows these subsystems and the potential links between them, including the type
of communications media that each link would use.
Figure 3 Indianapolis Subsystem Interconnect Diagram
Table 3 provides a listing of the systems identified in the Indianapolis region, along with the
associated stakeholder, National ITS Architecture entity, status, and a brief description.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 5
FINAL REPORT, Version 3.0

Table 3 Indianapolis ITS Systems Inventory
System
511 Traveler
Information
Ambulance
Dispatch
Ambulance
Vehicles
Avon CSX Rail
Yard
Beech Grove
Public Safety
Beech Grove
Public Works
Beech Grove
Vehicles
Beech Grove
Roadside
Equipment
CICS Website
Associated
Stakeholder
Indiana
Department of
Transportation
Ambulance/
Emergency
Services
Ambulance/
Emergency
Services
Railroad
Agencies
City of Beech
Grove
City of Beech
Grove
City of Beech
Grove
City of Beech
Grove
Indianapolis
Public
Transportation
Corporation/Indy
Go
Architecture
Entity
Information
Service Provider
Emergency
Management
Emergency
Vehicle
Subsystem
Element
Status
Existing
Existing
Existing
Element Description
The national traveler information
number, both via telephone and
through the Internet.
Emergency vehicles include ITS
equipment that provides the
sensory, processing, storage, and
communications functions
necessary to support safe and
efficient emergency response.
Rail Operations Existing CSX rail yard.
Emergency
Management
Traffic
Management,
Maintenance and
Construction
Management
Emergency
Vehicle
Subsystem,
Maintenance and
Construction
Vehicle
Roadway
Subsystem
Information
Service Provider
Existing
Existing
Existing
Existing
Existing
Police, Fire, and EMS dispatching
for the City of Beech Grove,
including the Beech Grove
Communications Center.
The DPW maintains all roads within
the city limits.
Beech Grove police, fire, EMS,
MCO vehicles
Beech Grove arterial traffic
management roadside equipment
includes any and all equipment
distributed on and along the
roadway which monitors and
controls traffic, including traffic
signals and vehicle detection
devices, including MCO equipment.
Central Indiana Commuter Services
is a new IndyGo service federally
funded to reduce air pollution and
traffic congestion. CICS offers
commuting solutions to area
employers and employees in Boone,
Hamilton, Hancock, Hendricks,
Johnson, Madison, Marion, Morgan
and Shelby counties. These
commuting solutions are
alternatives to driving alone, such as
carpooling, vanpooling, riding
transit, biking or walking.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 6
FINAL REPORT, Version 3.0

System
Clarian People
Mover
Convention
Center Kiosks
Downtown
Event Promoter
Emergency
Operations
Center
Event Promoters
IMS Command
Center
Indiana
Intelligence
Fusion Center
Associated
Stakeholder
Regional
Hospitals
Major Sporting
Event Venues
Indianapolis
Downtown, Inc.
Indianapolis
Emergency
Management
Agency
Event
Promoters/
Special Events
Indianapolis
Motor Speedway
IIFC Executive
Committee
Architecture
Entity
Multimodal
Transportation
Service Provider
Remote Traveler
Support
Archived Data
Management
Subsystem,
Information
Service Provider,
Parking
Management
Emergency
Management
Information
Service Provider
Emergency
Management,
Parking
Management,
Traffic
Management
Emergency
Management
Element
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Element Description
Elevated, driverless rail system that
runs between Methodist Hospital,
Indiana University Hospital, and the
Riley Hospital for Children.
Kiosks are public informational
displays supporting various levels
of interaction and information
access.
Downtown Indianapolis event
promoter (www.indydt.com).
Command center for major
emergencies in Indianapolis
(located in the MECA building)
Includes: Indiana Black Expo,
Indiana Sports Corporation,
Indianapolis Capital Improvements
Board (Colts), Indianapolis
Convention and Visitors
Association, Indianapolis 500
Festival, Indianapolis Downtown,
Indianapolis Motor Speedway,
NCAA Headquarters, Pacers Sports
& Entertainment
During race events, the IMS
Command Center hosts various
other agencies to form a MACC
(Multi-Agency Command Center).
These agencies include local
police/fire (on MECA System),
IndyGo, INDOT, the Federal
Aviation Administration (FAA), the
Transportation Safety
Administration (TSA), and local
hospitals (utilize their own
communications, but operate in the
MACC using face-to-face
communications with other
agencies). MECA also provides
equipment and one operator in the
MACC. Indiana State Police (250
personnel) are based in the infield,
and receive a MECA radio to
communicate with MECA and the
MACC.
Brings together public safety and
transportation agencies to collect
and distribute information.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 7
FINAL REPORT, Version 3.0

System
Indianapolis
Airport
Emergency
Vehicles
Indianapolis
Airport Field
Devices
Indianapolis
Airport
Maintenance
Vehicles
Indianapolis
Airport
Management
Systems
Indianapolis
Airport Parking
Systems
Indianapolis
DPW Operations
Center
Indianapolis
DPW Vehicles
Associated
Stakeholder
Indianapolis
Airport
Authority
Indianapolis
Airport
Authority
Indianapolis
Airport
Authority
Indianapolis
Airport
Authority
Indianapolis
Airport
Authority
Indianapolis
Department of
Public Works
Indianapolis
Department of
Public Works
Architecture
Entity
Emergency
Vehicle
Subsystem
Roadway
Subsystem,
Alerting and
Advisory
Systems,
Security
Monitoring
Subsystem
Maintenance and
Construction
Vehicle
Emergency
Management,
Traffic
Management,
Multimodal
Transportation
Service Provider,
Maintenance and
Construction
Management
Information
Service Provider,
Parking
Management
Emergency
Management,
Emissions
Management,
Traffic
Management,
Maintenance and
Construction
Management
Maintenance and
Construction
Vehicle
Element
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Element Description
18 squad cars, fire vehicles (aerial
truck, mini-pumper, 4 special crash
trucks, rescue, others), containment
vehicle (for bomb detonations),
decontamination unit (for airport
and county use, bought by county
emergency management), mass
casualty vehicle
CCTV cameras, portable and
permanent DMS, gate operations,
weather sensors, backup tornado
warning systems, environmental
sensors (for airport runoff)
This inventory item represents the
traffic management, emergency
management, and maintenance
systems within the jurisdiction of
the airport.
An automated system that allows
frequent travelers the opportunity to
enter and exit lots quickly without
fumbling for cash, credit cards or
coins. Also includes online parking
reservation at
www.indianapolisairport.com/parki
ng/index.php.
Current Indianapolis Department of
Public Works Dispatch Center.
Includes traffic signal maintenance
and operation, as well as MCO
dispatching and emergency
services. Located in the MECA
Building.
Indianapolis DPW MCO vehicles
include ITS devices that provides
the sensory, processing, storage, and
communications functions
necessary to support highway
maintenance and construction.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 8
FINAL REPORT, Version 3.0

System
Indianapolis
DPW Roadside
Equipment
Indianapolis Fire
Communications
Center
Indianapolis Fire
Department
Emergency
Vehicles
Indianapolis
Metropolitan
Police
Department
Emergency
Vehicles
Indianapolis
Metropolitan
Police Dispatch
Indianapolis
MPO
INDOT Arterial
Traffic Mgmt.
System
Associated
Stakeholder
Indianapolis
Department of
Public Works
Indianapolis Fire
Department
Indianapolis Fire
Department
Indianapolis
Metropolitan
Police
Department
Indianapolis
Metropolitan
Police
Department
Indianapolis
MPO
Indiana
Department of
Transportation
District Level
Architecture
Entity
Roadway
Subsystem
Emergency
Management
Emergency
Vehicle
Subsystem
Emergency
Vehicle
Subsystem
Emergency
Management
Information
Service Provider
Traffic
Management
Element
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Element Description
Indianapolis DPW arterial traffic
management roadside equipment
includes any and all equipment
distributed on and along the
roadway which monitors and
controls traffic, including traffic
signals, speed advisory signs, and
vehicle detection devices, including
MCO equipment.
The communications center is
responsible for fire and EMS
dispatch services for all of Marion
County (including Wishard
Ambulance) with the exception of
the town of Speedway and the cities
of Beech Grove and Lawrence.
Located in the MECA Building.
IFD emergency vehicles include
ITS equipment that provides the
sensory, processing, storage, and
communications functions
necessary to support safe and
efficient emergency response. Also
includes HAZMAT response
vehicles.
IMPD emergency vehicles include
ITS equipment that provides the
sensory, processing, storage, and
communications functions
necessary to support safe and
efficient emergency response.
Central location for all IMPD calls
(including 911) and dispatching.
Located in the MECA Building.
Administers the Regional
Transportation Planning Program,
which results in plans and programs
for highways, transit, and other
means of moving people and goods
in compliance with federal
transportation requirements to guide
the development of an efficient
multi-modal transportation system
within the Indianapolis
Metropolitan Planning Area.
INDOT central control of traffic
signals on state routes within the
MPA.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 9
FINAL REPORT, Version 3.0

System
INDOT Arterial
Traffic Mgmt.
Roadside
Equipment
INDOT Hoosier
Helper Vehicles
INDOT
Indianapolis
TMC
INDOT
Indianapolis
TMC Roadside
Equipment
INDOT
Infrastructure
Inventory
System
INDOT MCO
Field Devices
INDOT MCO
Management
INDOT MCO
Vehicles
Associated
Stakeholder
Indiana
Department of
Transportation
District Level
Indiana
Department of
Transportation
District Level
Indiana
Department of
Transportation
District Level
Indiana
Department of
Transportation
District Level
Indiana
Department of
Transportation
District Level
Indiana
Department of
Transportation
District Level
Indiana
Department of
Transportation
District Level
Indiana
Department of
Transportation
District Level
Architecture
Entity
Roadway
Subsystem
Emergency
Vehicle
Subsystem
Archived Data
Management
Subsystem,
Emergency
Management,
Information
Service Provider,
Traffic
Management
Roadway
Subsystem
Asset
Management
Roadway
Subsystem
Maintenance and
Construction
Management
Maintenance and
Construction
Vehicle
Element
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Element Description
INDOT arterial traffic management
roadside equipment includes any
and all equipment distributed on and
along the roadway which monitors
and controls traffic, including traffic
signals and vehicle detection
devices.
INDOT's Freeway Service Patrol
(FSP). Hoosier Helper vehicles
include ITS equipment that provides
the sensory, processing, storage, and
communications functions
necessary to support safe and
efficient emergency response. Also
includes one CVS Good Samaritan"
van which operates during the
morning and evening peak periods."
Indianapolis Traffic Management
Center located at 21st Street and
Post Road.
Indianapolis TMC roadside
equipment includes any and all
equipment distributed on and along
the roadway which monitors and
controls traffic, including DMS,
HAR, Travel Time Signs (Note:
first deployment in 2011), CCTV
cameras, and vehicle detection
devices.
Electronic inventory of ITS devices
on the interstate system (GIS
format).
INDOT MCO field devices for
operational purposes of
maintenance and construction.
Maintenance dispatch from the
INDOT Indianapolis district
maintenance facilities in Greenfield,
Crawfordsville, and Seymour.
INDOT MCO vehicles include ITS
devices that provides the sensory,
processing, storage, and
communications functions
necessary to support highway
maintenance and construction.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 10
FINAL REPORT, Version 3.0

System
INDOT Security
Monitoring Field
Equipment
IndyGo
Operations
Center
IndyGo Security
Monitoring Field
Equipment
IndyGo Transit
Information
IndyGo Transit
Vehicles
IndyGo Traveler
Card
IndyGo Website
ISP Dispatch
Associated
Stakeholder
Indiana
Department of
Transportation
District Level
Indianapolis
Public
Transportation
Corporation/Indy
Go
Indianapolis
Public
Transportation
Corporation/Indy
Go
Indianapolis
Public
Transportation
Corporation/Indy
Go
Indianapolis
Public
Transportation
Corporation/Indy
Go
Indianapolis
Public
Transportation
Corporation/Indy
Go
Indianapolis
Public
Transportation
Corporation/Indy
Go
Indiana State
Police
Architecture
Entity
Security
Monitoring
Subsystem
Archived Data
Management
Subsystem,
Emergency
Management,
Information
Service Provider,
Parking
Management,
Transit
Management
Remote Traveler
Support,
Security
Monitoring
Subsystem
Remote Traveler
Support
Transit Vehicle
Subsystem
Traveler Card
Information
Service Provider
Emergency
Management,
Information
Service Provider,
Traffic
Management
Element
Status
Existing
Existing
Existing
Planned
Existing
Existing
Existing
Existing
Element Description
INDOT security monitoring field
equipment includes sensors and
surveillance devices that monitor
transportation infrastructure and
public areas.
Dispatching for IndyGo fixed route
and paratransit vehicles.
IndyGo security monitoring field
equipment includes sensors and
surveillance devices that monitor
transportation infrastructure and
public areas.
Sharing of AVL data, including
interactive Real-Time bus arrival
information (phone, text, web)
IndyGo transit vehicles include ITS
devices that support the safe and
efficient government of passengers.
These systems collect, manage, and
disseminate transit-related
information to the driver, operations
and maintenance personnel, and
transit system patrons.
IndyGo traveler cards enable the
transfer of electronic information
from the user of a service (i.e., a
traveler) to the provider of the
service.
The IndyGo website (updated 2011)
and Google Transit currently
provide travelers with static
information on transit schedules,
costs, and service updates. Real
time arrival information to be added
2012-2014.
Dispatching for ISP vehicles in
Districts 51, 52, 53 and the Capital
Police. ISP Post 52 is co-located
with the Indianapolis TMC.
Includes weather/road conditions
hotline (website/telephone line).
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 11
FINAL REPORT, Version 3.0

System
ISP Emergency
Vehicles
ITS Maintenance
Contractor
Lawrence Public
Safety
Lawrence Public
Works/Street
Department
Lawrence
Vehicles
Lawrence
Roadside
Equipment
Lucas Oil
Stadium
Command
Center
Major Employer
Emergency
Vehicles
Major Employer
Management
Systems
MECA System
Associated
Stakeholder
Indiana State
Police
Private
Maintenance
Companies
City of
Lawrence
City of
Lawrence
City of
Lawrence
City of
Lawrence
Major Sporting
Event Venues
Major
Employers
Major
Employers
MECA System
Users
Architecture
Entity
Emergency
Vehicle
Subsystem
Maintenance and
Construction
Field Personnel
Emergency
Management
Traffic
Management,
Maintenance and
Construction
Management
Emergency
Vehicle
Subsystem,
Maintenance and
Construction
Vehicle
Roadway
Subsystem
Emergency
Management
Emergency
Vehicle
Subsystem
Emergency
Management,
Event Promoters
Emergency
Management,
Emergency
Communications
System
Element
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Media Media Services Media Existing
Element Description
ISP emergency vehicles include ITS
equipment that provides the
sensory, processing, storage, and
communications functions
necessary to support safe and
efficient emergency response.
Provides preventative maintenance
and emergency repair services to
ITS equipment
Police, Fire, and EMS dispatching
for the City of Lawrence, including
Public Safety Communications
The DPW/Street Department
maintains all roads within the city
limits.
Lawrence police, fire, EMS, MCO
vehicles
Lawrence arterial traffic
management roadside equipment
includes any and all equipment
distributed on and along the
roadway which monitors and
controls traffic, including traffic
signals and vehicle detection
devices, including MCO equipment.
Command center for events at the
Lucas Oil Stadium.
Ambulance, HAZMAT, and fire
vehicles.
Incident and emergency
management systems for major
employer facilities, including
emergency operations center.
Metropolitan Communications
Agency - emergency
communications system for all of
Marion County (except the towns of
Speedway, Beech Grove, and
Lawrence)
The media element represents the
information systems that provide
traffic reports, travel conditions, and
other transportation-related news
services to the traveling public
through radio, TV, and other media.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 12
FINAL REPORT, Version 3.0

System
Private Towing
Companies
RWIS Sensors
School Buses
School Police
Departments
Speedway Public
Safety
Speedway Public
Works
Speedway
Vehicles
Speedway
Roadside
Equipment
Suburban
Municipality
Emergency
Dispatch
Associated
Stakeholder
Towing
Operators
RWIS Users
Indianapolis
Schools
Indianapolis
Schools
Town of
Speedway
Town of
Speedway
Town of
Speedway
Town of
Speedway
Suburban
Municipalities
Architecture
Entity
Emergency
Management
Roadway
Subsystem,
Emissions
Management
Transit
Management
Emergency
Management
Emergency
Management
Traffic
Management,
Maintenance and
Construction
Management
Emergency
Vehicle
Subsystem,
Maintenance and
Construction
Vehicle
Roadway
Subsystem
Emergency
Management
Element
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Element Description
Towing companies that provide
removal of vehicles and debris from
roadways
Road weather information system
stations (6) located in Marion
County. Four are owned by the
City of Indianapolis, two are owned
by INDOT. RWIS data is obtained
via a web-based application in
conjunction with MADIS (a
National Weather Service protocol).
The effort is being initiated as part
of the CLARUS project. INDOT
and DPW via their joint sharing of
the website make Indiana one of 16
states to be linked to the web-based
RWIS monitoring network.
School bus services for IPS,
township, municipal, and private
schools in the Indianapolis region.
IPS Police includes ninety-one (91)
full-time, and a varying number of
part-time, sworn police officers,
numerous civilian employees. IPS
Police Officers are stationed in all
of the high, middle and alternative
schools of IPS. Also includes
township school district police
departments.
Police, Fire, and EMS dispatching
for the Town of Speedway.
The DPW maintains all roads within
the city limits.
Speedway police, fire, EMS, MCO
vehicles
Speedway arterial traffic
management roadside equipment
includes any and all equipment
distributed on and along the
roadway which monitors and
controls traffic, including traffic
signals and vehicle detection
devices, including MCO equipment.
Police, fire, EMS, and emergency
communications for municipalities
outside of Unigov.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 13
FINAL REPORT, Version 3.0

System
Suburban
Municipality
Emergency
Vehicles
Suburban
Municipality
Street
Department
Dispatch
Suburban
Municipality
Street
Department
Vehicles
Suburban
Municipality
Street
Department
Roadside
Equipment
Surface
Transportation
Weather Service
Surrounding
County Highway
Dispatch
Surrounding
County Highway
Vehicles
Surrounding
County Highway
Roadside
Equipment
Associated
Stakeholder
Suburban
Municipalities
Suburban
Municipalities
Suburban
Municipalities
Suburban
Municipalities
Meridian
Environmental
Technology
Surrounding
Counties
Surrounding
Counties
Surrounding
Counties
Architecture
Entity
Emergency
Vehicle
Subsystem
Traffic
Management,
Maintenance and
Construction
Management
Maintenance and
Construction
Vehicle
Roadway
Subsystem
Surface
Transportation
Weather Service
Traffic
Management,
Maintenance and
Construction
Management
Maintenance and
Construction
Vehicle
Roadway
Subsystem
Element
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Element Description
Suburban municipality emergency
vehicles include ITS equipment that
provides the sensory, processing,
storage, and communications
functions necessary to support safe
and efficient emergency response.
Suburban municipality street
departments responsible for traffic
signal maintenance and operation,
as well as MCO dispatching and
emergency services.
Suburban municipality MCO
vehicles include ITS devices that
provides the sensory, processing,
storage, and communications
functions necessary to support
highway maintenance and
construction.
Suburban municipality arterial
traffic management roadside
equipment includes any and all
equipment distributed on and along
the roadway which monitors and
controls traffic, including traffic
signals and vehicle detection
devices, including MCO equipment.
Providers of value-added sector
specific meteorological services.
These providers utilize National
Weather Service data and
predictions, road condition
information and local environmental
data to provide weather
observations and forecasts.
Surrounding county highway
departments responsible for traffic
signal maintenance and operation,
as well as MCO dispatching and
emergency services.
Surrounding county MCO vehicles
include ITS devices that provides
the sensory, processing, storage, and
communications functions
necessary to support highway
maintenance and construction.
Surrounding county arterial traffic
management roadside equipment
includes any and all equipment
distributed on and along the
roadway which monitors and
controls traffic, including traffic
signals and vehicle detection
devices, including MCO equipment.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 14
FINAL REPORT, Version 3.0

System
Surrounding
County Security
Monitoring Field
Equipment
Surrounding
County Sheriff
Communications
Center
Surrounding
County Sheriff
Emergency
Vehicles
Taxi Services
Traffic Data
Archive
TrafficWise
Website
User Personal
Computing
Devices
Utility
Emergency
Repair/
Response
Vehicles
Weather
Services
Associated
Stakeholder
Surrounding
Counties
Surrounding
Counties
Surrounding
Counties
Taxi Companies
Traffic Data
Archive Users
Group
Indiana
Department of
Transportation
District Level
Traveling
Motorists
Utility
Companies
Traveling
Motorists
National
Weather Service
Architecture
Entity
Security
Monitoring
Subsystem
Emergency
Management
Emergency
Vehicle
Subsystem
Transit
Management
Archived Data
Management
Subsystem
Information
Service Provider
Personal
Information
Access
Emergency
Management
Vehicle
Weather Service
Element
Status
Future
Existing
Existing
Existing
Planned
Existing
Existing
Existing
Existing
Existing
Element Description
Surrounding county security
monitoring field equipment includes
sensors and surveillance devices
that monitor transportation
infrastructure and public areas.
Emergency call centers
(911)/dispatch centers in adjoining
counties
Surrounding county sheriff
emergency vehicles include ITS
equipment that provides the
sensory, processing, storage, and
communications functions
necessary to support safe and
efficient emergency response.
Online traffic data archive.
INDOT ITS traveler information
source.
User personal computing devices
refers to equipment an individual
owns and can personalize with their
choices for information about
transportation networks. An
Internet-connected PC is an
example.
A general element that represents
personal automobiles and fleet
vehicles that include ITS safety,
navigation and traveler information
systems that may be applicable to
any highway vehicle.
Weather services include the
National Weather Service as well as
private disseminators of weather
data.
* ‘Existing’ describes an element that is in-place, ‘planned’ describes a system that is funded and scheduled for deployment, ‘future’
describes a system that is not funded but is expected to be deployed within the next 10 years
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 15
FINAL REPORT, Version 3.0

2.2 Needs and Services
In order to determine how the systems in Table 3
can best be applied, the stakeholder workshop held
on February 8, 2005, included an ITS needs
analysis. The attendees considered a number of
critical transportation issues as identified in the
Indianapolis Early Deployment Plan (EDP) and
from the United States Department of
Transportation (USDOT). Each transportation issue
was defined, discussed, and compared. After
discussion, the identified issues were prioritized
through a voting process. The prioritized list of
issues is as follows:
1. Safety (9 votes)
2. Efficiency (9 votes)
3. Interagency communication (7 votes)
4. Security (6 votes)
5. Traveler Information (6 votes)
6. Mobility (5 votes)
7. Integration of systems/services (4 votes)
8. Improvement in the environment (4 votes)
9. Productivity (3 votes)
10. Maintenance and construction (3 votes)
11. Transportation data (1 vote)
12. Energy reduction (0 votes)
These prioritized issues serve as the basis for the development of ITS goals and objectives for the
region, as well as the identification of ITS services.
Each of the systems listed in Table 3 are applied by their associated stakeholder to provide some
service to the traveling public. In terms of transportation, a ‘service’ can be defined as:
capabilities you put in place to meet transportation needs.
The National ITS Architecture contains 91 “market packages” which correspond to the services
provided by various transportation agencies. These market packages demonstrate how the
various subsystems and terminators identified in Section 2.1 work together to provide
transportation services. As an example, Figure 4 shows the ‘Network Surveillance’ market
package (ATMS01), with its associated subsystems (Information Service Provider, Roadway, and
Traffic Management Roadway) and terminators (Map Update Provider, Other Roadway, Traffic,
and Traffic Operations Personnel). As defined by the National ITS Architecture, the Network
Surveillance market package
includes traffic detectors, other surveillance equipment, the supporting field
equipment, and fixed-point to fixed-point communications to transmit the
collected data back to the Traffic Management Subsystem. 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
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 16
FINAL REPORT, Version 3.0

verify incidents, detect faults in 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.
ATMS01 – Network Surveillance
Information
Service Provider
Traffic Operations
Personnel
road network conditions
traffic operator inputs
traffic operator data
Traffic
Management
traffic flow +
traffic images
Other Roadway
roadway
equipment
coordination
Roadway
traffic sensor control +
video surveillance control
Roadway Basic
Surveillance
Map Update
Provider
map update requests
map updates
Collected Traffic
Surveillance
Traffic Maintenance
traffic
characteristics
Roadway Equipment
Coordination
Traffic
Figure 4 Network Surveillance Market Package Diagram
During the stakeholder workshop, the attendees were invited to help identify the market packages
that are appropriate to their agencies. Table 4 provides a listing of the refined list of market
packages (46) for the Indianapolis region, along with the associated element(s) and status.
Table 4 Indianapolis Market Packages (Transportation Services) Inventory
Market
Package
ATMS01
Market
Package Name
Network
Surveillance
Status
Existing
Element
Beech Grove Public Works
Beech Grove Roadside Equipment
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
INDOT Arterial Traffic Mgmt. System
INDOT Arterial Traffic Mgmt. Roadside Equipment
INDOT Indianapolis TMC
INDOT Indianapolis TMC Roadside Equipment
Lawrence Public Works/Street Department
Lawrence Roadside Equipment
Speedway Public Works
Speedway Roadside Equipment
Suburban Municipality Street Department Dispatch
Suburban Municipality Street Department Roadside
Equipment
Surrounding County Highway Dispatch
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 17
FINAL REPORT, Version 3.0

Market
Package
Market
Package Name
Status
Element
Surrounding County Highway Roadside Equipment
Beech Grove Public Works
Beech Grove Roadside Equipment
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
INDOT Arterial Traffic Mgmt. System
INDOT Arterial Traffic Mgmt. Roadside Equipment
ATMS03
Surface Street
Lawrence Public Works/Street Department
Existing
Control
Lawrence Roadside Equipment
Speedway Public Works
Speedway Roadside Equipment
Suburban Municipality Street Department Dispatch
Suburban Municipality Street Department Roadside
Equipment
Surrounding County Highway Dispatch
ATMS04 Freeway Control Future
Surrounding County Highway Roadside Equipment
INDOT Indianapolis TMC
ATMS06
Traffic
Information
Dissemination
Existing
511 Traveler Information
Downtown Event Promoter
Event Promoters
Indianapolis Airport Field Devices
Indianapolis DPW Operations Center
Indianapolis MPO
INDOT Indianapolis TMC
INDOT Indianapolis TMC Roadside Equipment
IndyGo Operations Center
Media
TrafficWise Website
Planned
Indiana Intelligence Fusion Center
Future
Indianapolis DPW Roadside Equipment
Existing
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
INDOT Arterial Traffic Mgmt. System
INDOT Arterial Traffic Mgmt. Roadside Equipment
Beech Grove Public Works
Beech Grove Roadside Equipment
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
INDOT Arterial Traffic Mgmt. System
ATMS07
INDOT Arterial Traffic Mgmt. Roadside Equipment
Regional Traffic
INDOT Indianapolis TMC
Management
INDOT Indianapolis TMC Roadside Equipment
Planned Lawrence Public Works/Street Department
Lawrence Roadside Equipment
Speedway Public Works
Speedway Roadside Equipment
Suburban Municipality Street Department Dispatch
Suburban Municipality Street Department Roadside
Equipment
Surrounding County Highway Dispatch
Surrounding County Highway Roadside Equipment
ATMS08 Traffic Incident Existing Ambulance Dispatch
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 18
FINAL REPORT, Version 3.0

Market
Package
ATMS09
ATMS11
Market
Package Name
Management
System
Traffic Forecast
and Demand
Management
Emissions
Monitoring and
Management
Status
Planned
Future
Planned
Existing
Element
Ambulance Vehicles
Avon CSX Rail Yard
Beech Grove Public Safety
Beech Grove Public Works
Beech Grove Vehicles
Downtown Event Promoter
Emergency Operations Center
Event Promoters
IMPD Dispatch
IMPD Emergency Vehicles
IMS Command Center
Indianapolis Airport Emergency Vehicles
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
Indianapolis Fire Communications Center
INDOT Hoosier Helper Vehicles
INDOT Indianapolis TMC
INDOT Indianapolis TMC Roadside Equipment
INDOT MCO Field Devices
INDOT MCO Management
IndyGo Operations Center
ISP Dispatch
ISP Emergency Vehicles
Lawrence Public Safety
Lawrence Public Works/Street Department
Lawrence Vehicles
Major Employer Emergency Vehicles
Major Employer Management Systems
MECA System
Private Towing Companies
RWIS Sensors
School Buses
School Police Departments
Speedway Public Safety
Speedway Public Works
Speedway Vehicles
Suburban Municipality Emergency Dispatch
Suburban Municipality Emergency Vehicles
Suburban Municipality Street Department Dispatch
Utility Emergency Repair/Response
Indiana Intelligence Fusion Center
Surrounding County Highway Dispatch
Surrounding County Sheriff Communications Center
Surrounding County Sheriff Emergency Vehicles
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
INDOT Indianapolis TMC
INDOT Indianapolis TMC Roadside Equipment
Indianapolis DPW Operations Center
RWIS Sensors
ATMS13 Standard Existing Beech Grove Public Works
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 19
FINAL REPORT, Version 3.0

Market
Package
ATMS16
ATMS18
ATMS19
MC01
MC02
MC03
MC04
Market
Package Name
Railroad Grade
Crossing
Parking Facility
Management
Reversible Lane
Management
Speed
Monitoring
Maintenance and
Construction
Vehicle and
Equipment
Tracking
Maintenance and
Construction
Vehicle
Maintenance
Road Weather
Data Collection
Weather
Information
Processing and
Distribution
Status
Existing
Existing
Existing
Planned
Existing
Planned
Existing
Existing
Existing
Element
Beech Grove Roadside Equipment
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
INDOT Arterial Traffic Mgmt. System
INDOT Arterial Traffic Mgmt. Roadside Equipment
Lawrence Public Works/Street Department
Lawrence Roadside Equipment
Speedway Public Works
Speedway Roadside Equipment
Suburban Municipality Street Department Dispatch
Suburban Municipality Street Department Roadside
Equipment
Surrounding County Highway Dispatch
Surrounding County Highway Roadside Equipment
Downtown Event Promoter
Indianapolis Airport Parking Systems
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
Indianapolis DPW Roadside Equipment
ISP Dispatch
Surrounding County Highway Dispatch
Surrounding County Highway Roadside Equipment
Indianapolis DPW Operations Center
Indianapolis DPW Vehicles
INDOT MCO Management
INDOT MCO Vehicles
Beech Grove Public Works
Beech Grove Vehicles
Indianapolis Airport Maintenance Vehicles
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
Indianapolis DPW Vehicles
INDOT MCO Management
INDOT MCO Vehicles
Lawrence Public Works/Street Department
Lawrence Vehicles
Speedway Public Works
Speedway Vehicles
Suburban Municipality Street Department Dispatch
Suburban Municipality Street Department Vehicles
Surrounding County Highway Dispatch
Surrounding County Highway Vehicles
Indianapolis Airport Field Devices
Indianapolis DPW Operations Center
INDOT Indianapolis TMC
INDOT MCO Management
RWIS Sensors
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
INDOT Indianapolis TMC
INDOT MCO Management
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 20
FINAL REPORT, Version 3.0

Market
Package
MC05
MC06
MC07
MC08
Market
Package Name
Roadway
Automated
Treatment
Winter
Maintenance
Roadway
Maintenance and
Construction
Work Zone
Management
Status
Future
Existing
Existing
Existing
Element
Surface Transportation Weather Service
Weather Services
INDOT MCO Field Devices
INDOT MCO Management
Beech Grove Public Works
Beech Grove Vehicles
Indianapolis Airport Maintenance Vehicles
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
Indianapolis DPW Vehicles
INDOT MCO Management
INDOT MCO Vehicles
Lawrence Public Works/Street Department
Lawrence Vehicles
Speedway Public Works
Speedway Vehicles
Suburban Municipality Street Department Dispatch
Suburban Municipality Street Department Vehicles
Surrounding County Highway Dispatch
Surrounding County Highway Vehicles
Beech Grove Public Works
Beech Grove Vehicles
Beech Grove Roadside Equipment
Indianapolis Airport Maintenance Vehicles
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
Indianapolis DPW Vehicles
Indianapolis DPW Roadside Equipment
INDOT MCO Field Devices
INDOT MCO Management
INDOT MCO Vehicles
ITS Maintenance Contractor
Lawrence Public Works/Street Department
Lawrence Vehicles
Lawrence Roadside Equipment
Speedway Public Works
Speedway Vehicles
Speedway Roadside Equipment
Suburban Municipality Street Department Dispatch
Suburban Municipality Street Department Vehicles
Suburban Municipality Street Department Roadside
Equipment
Surrounding County Highway Dispatch
Surrounding County Highway Vehicles
Surrounding County Highway Roadside Equipment
Beech Grove Public Works
Beech Grove Vehicles
Beech Grove Roadside Equipment
Indianapolis Airport Field Devices
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 21
FINAL REPORT, Version 3.0

Market
Package
Market
Package Name
Status
Element
Indianapolis DPW Vehicles
Indianapolis DPW Roadside Equipment
INDOT Indianapolis TMC Roadside Equipment
INDOT MCO Field Devices
INDOT MCO Management
INDOT MCO Vehicles
ITS Maintenance Contractor
Lawrence Public Works/Street Department
Lawrence Vehicles
Lawrence Roadside Equipment
Private Towing Companies
Speedway Public Works
Speedway Vehicles
Speedway Roadside Equipment
Suburban Municipality Street Department Dispatch
Suburban Municipality Street Department Vehicles
Suburban Municipality Street Department Roadside
Equipment
Surrounding County Highway Dispatch
Surrounding County Highway Vehicles
Surrounding County Highway Roadside Equipment
MC09
Work Zone
Safety
Monitoring
Existing
Surrounding County Highway Dispatch
Surrounding County Highway Vehicles
Surrounding County Highway Roadside Equipment
MC10
Indianapolis DPW Operations Center
Maintenance and
Indianapolis MPO
Construction
Existing
INDOT Indianapolis TMC
Activity
511 Traveler Information
Coordination
TrafficWise Website
MC12
Indianapolis DPW Operations Center
Infrastructure
Existing
INDOT MCO Management
Monitoring
RWIS Sensors
APTS01
Transit Vehicle
IndyGo Operations Center
Existing
Tracking
IndyGo Transit Vehicles
APTS02
Transit Fixed-
Route
Operations
Existing
IndyGo Operations Center
IndyGo Transit Vehicles
School Buses
APTS03
Demand
Response Transit
Operations
Existing
IndyGo Operations Center
IndyGo Transit Vehicles
Taxi Services
APTS04
IndyGo Kiosks
Transit Fare
IndyGo Operations Center
Collection Existing
IndyGo Transit Vehicles
Management
IndyGo Traveler Card
APTS05 Transit Security Existing
IndyGo Operations Center
IndyGo Security Monitoring Field Equipment
IndyGo Transit Vehicles
IndyGo Operations Center
APTS06
Transit Fleet
IndyGo Transit Vehicles
Existing
Management
School Buses
Taxi Services
APTS07 Multi-modal Existing Clarian People Mover
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 22
FINAL REPORT, Version 3.0

Market
Package
APTS08
APTS09
APTS10
ATIS01
ATIS02
ATIS08
ATIS09
CVO10
Market
Package Name
Coordination
Transit Traveler
Information
Transit Signal
Priority
Transit
Passenger
Counting
Broadcast
Traveler
Information
Interactive
Traveler
Information
Dynamic
Ridesharing
In Vehicle
Signing
HAZMAT
Management
Status
Planned
Planned
Existing
Existing
Planned
Existing
Existing
Future
Existing
Element
Indianapolis Airport Management Systems
Indianapolis Airport Parking Systems
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
IndyGo Operations Center
IndyGo Transit Vehicles
Taxi Services
Downtown Event Promoter
IndyGo Kiosks
IndyGo Operations Center
IndyGo Transit Displays
IndyGo Transit Vehicles
User Personal Computing Devices
Indianapolis DPW Operations Center
Indianapolis DPW Roadside Equipment
IndyGo Transit Vehicles
IndyGo Operations Center
IndyGo Transit Vehicles
Downtown Event Promoter
Event Promoters
IndyGo Website
Media
Surface Transportation Weather Service
TrafficWise Website
User Personal Computing Devices
Weather Services
511 Traveler Information
INDOT Indianapolis TMC
Convention Center Kiosks
Event Promoters
Indianapolis Airport Parking Systems
TrafficWise Website
User Personal Computing Devices
511 Traveler Information
CICS Website
IndyGo Operations Center
INDOT Indianapolis TMC
INDOT Indianapolis TMC Roadside Equipment
Ambulance Dispatch
Beech Grove Public Safety
Emergency Operations Center
IMPD Dispatch
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
Indianapolis Fire Communications Center
INDOT Indianapolis TMC
ISP Dispatch
Lawrence Public Safety
Major Employer Management Systems
Private Towing Companies
Speedway Public Safety
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 23
FINAL REPORT, Version 3.0

Market
Package
EM01
EM02
Market
Package Name
Emergency Call-
Taking and
Dispatch
Emergency
Routing
Status
Existing
Existing
Element
Suburban Municipality Emergency Dispatch
Surrounding County Sheriff Communications Center
Ambulance Dispatch
Ambulance Vehicles
Beech Grove Public Safety
Beech Grove Vehicles
Emergency Operations Center
IMS Command Center
IMPD Dispatch
IMPD Emergency Vehicles
Indianapolis Fire Communications Center
Indianapolis Fire Department Emergency Vehicles
ISP Dispatch
ISP Emergency Vehicles
Lawrence Public Safety
Lawrence Vehicles
MECA System
Private Towing Companies
Lucas Oil Stadium Command Center
School Police Departments
Speedway Public Safety
Speedway Vehicles
Suburban Municipality Emergency Dispatch
Suburban Municipality Emergency Vehicles
Surrounding County Sheriff Communications Center
Surrounding County Sheriff Emergency Vehicles
Utility Emergency Repair/Response
Ambulance Dispatch
Ambulance Vehicles
Beech Grove Public Safety
Beech Grove Vehicles
Beech Grove Roadside Equipment
IMPD Dispatch
IMPD Emergency Vehicles
Indianapolis DPW Roadside Equipment
Indianapolis Fire Communications Center
Indianapolis Fire Department Emergency Vehicles
INDOT Hoosier Helper Vehicles
INDOT Indianapolis TMC
ISP Dispatch
ISP Emergency Vehicles
Lawrence Public Safety
Lawrence Vehicles
Lawrence Roadside Equipment
Major Employer Emergency Vehicles
Major Employer Management Systems
Speedway Public Safety
Speedway Vehicles
Speedway Roadside Equipment
Suburban Municipality Emergency Dispatch
Suburban Municipality Emergency Vehicles
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 24
FINAL REPORT, Version 3.0

Market
Package
EM03
EM04
EM05
EM06
EM07
EM08
Market
Package Name
Mayday and
Alarms Support
Roadway
Service Patrols
Transportation
Infrastructure
Protection
Wide-Area Alert
Early Warning
System
Disaster
Response and
Recovery
Status
Existing
Existing
Existing
Future
Existing
Planned
Future
Existing
Planned
Existing
Element
Suburban Municipality Street Department Roadside
Equipment
Surrounding County Highway Roadside Equipment
Surrounding County Sheriff Communications Center
Surrounding County Sheriff Emergency Vehicles
Indianapolis Fire Communications Center
INDOT Hoosier Helper Vehicles
INDOT Indianapolis TMC
Emergency Operations Center
IMPD Dispatch
IMPD Security Monitoring Field Equipment
Indianapolis Airport Field Devices
Indianapolis Airport Management Systems
INDOT Indianapolis TMC
INDOT Security Monitoring Field Equipment
Surrounding County Security Monitoring Field Equipment
Surrounding County Sheriff Communications Center
Beech Grove Public Safety
Emergency Operations Center
IMPD Dispatch
Indianapolis DPW Operations Center
Indianapolis Fire Communications Center
Indianapolis Police Dispatch
INDOT Indianapolis TMC
INDOT Indianapolis TMC Roadside Equipment
ISP Dispatch
Lawrence Public Safety
Speedway Public Safety
Suburban Municipality Emergency Dispatch
Surrounding County Sheriff Communications Center
Indiana Intelligence Fusion Center
Indianapolis DPW Roadside Equipment
Emergency Operations Center
Indianapolis Airport Field Devices
Indianapolis Airport Management Systems
INDOT Indianapolis TMC
INDOT Security Monitoring Field Equipment
Surface Transportation Weather Service
Surrounding County Security Monitoring Field Equipment
Surrounding County Sheriff Communications Center
Weather Services
Indiana Intelligence Fusion Center
Ambulance Dispatch
Avon CSX Rail Yard
Beech Grove Public Safety
Emergency Operations Center
IMPD Dispatch
Indianapolis DPW Operations Center
Indianapolis Fire Communications Center
INDOT Indianapolis TMC
IndyGo Operations Center
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 25
FINAL REPORT, Version 3.0

Market
Package
EM09
EM10
Market
Package Name
Evacuation and
Reentry
Management
Disaster Traveler
Information
Status
Planned
Existing
Planned
Existing
Planned
AD1 ITS Data Mart Existing
Element
ISP Dispatch
Lawrence Public Safety
Speedway Public Safety
Suburban Municipality Emergency Dispatch
Surrounding County Sheriff Communications Center
Indiana Intelligence Fusion Center
Avon CSX Rail Yard
Beech Grove Public Safety
Emergency Operations Center
IMPD Dispatch
Indianapolis Airport Management Systems
Indianapolis DPW Operations Center
Indianapolis Fire Communications Center
INDOT Indianapolis TMC
IndyGo Operations Center
ISP Dispatch
Lawrence Public Safety
Speedway Public Safety
Suburban Municipality Emergency Dispatch
Surrounding County Sheriff Communications Center
Intelligence Fusion Center
Beech Grove Public Safety
IMPD Dispatch
Indianapolis DPW Operations Center
INDOT Indianapolis TMC
ISP Dispatch
Lawrence Public Safety
Media
Speedway Public Safety
Suburban Municipality Emergency Dispatch
Surrounding County Sheriff Communications Center
511 Traveler Information
Beech Grove Public Safety
Beech Grove Public Works
IMPD Dispatch
Indianapolis DPW Operations Center
Indianapolis Fire Communications Center
Indianapolis MPO
INDOT Indianapolis TMC
INDOT Infrastructure Inventory System
INDOT MCO Management
IndyGo Operations Center
ISP Dispatch
Lawrence Public Safety
Lawrence Public Works/Street Department
Speedway Public Safety
Speedway Public Works
Suburban Municipality Emergency Dispatch
Suburban Municipality Street Department Dispatch
Surrounding County Highway Dispatch
Surrounding County Sheriff Communications Center
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 26
FINAL REPORT, Version 3.0

Market
Package
AD2
Market
Package Name
ITS Data
Warehouse
Status
Planned
Element
Indianapolis DPW Operations Center
Indianapolis MPO
INDOT Indianapolis TMC
Traffic Data Archive
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 27
FINAL REPORT, Version 3.0

3.0 Concept of Operations
Before intelligent transportation systems can be effectively deployed, ITS stakeholders should
come together to develop a vision for ITS. A key component of this vision is a Concept of
Operations that defines the roles and responsibilities of those agencies that will gather, process,
and act upon the information that is collected by the system.
This section defines the vision for ITS in Indianapolis and what roles and responsibilities each
transportation agency must fulfill to realize this vision.
3.1 Vision Statement
Building upon the needs identified in Section 2.2, those transportation representatives who
gathered at the stakeholder workshop also developed a vision for ITS in Indianapolis. Simply
put, ITS will be applied in Indianapolis
“to enhance the sharing of information to maximize the efficiency, safety, and
security of the transportation system and to encourage modal integration and
consumer choices, promote economic development, and improve social and
environmental quality.”
This vision statement is intended to serve as guidance for the planning and deployment of ITS in
the Indianapolis region for the next 10 years, and should be continually reevaluated to ensure that
it accurately captures the needs and goals of travelers and transportation stakeholders in
Indianapolis.
3.2 Role and Responsibility Areas
To demonstrate how the various regional ITS stakeholders will work together to realize this
vision, twelve ‘role and responsibility’ areas were developed. Each of these areas is described
below in detail using tables that summarize the individual stakeholder roles and responsibilities
by area.
3.2.1 Archived Data Management
Archived data management includes the collection, archiving, management, and sharing of data
generated from regional ITS sources. As more and more ITS data collection devices (e.g., transit
passenger fare counters, environmental monitoring stations, and vehicle detectors) are installed
on the surface transportation system in Indianapolis, the volume of data that they collect will
grow. Table 5 shows the stakeholder roles and responsibilities for the efficient collection and use
of this data.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 28
FINAL REPORT, Version 3.0

Table 5 Archived Data Management Roles and Responsibilities
Stakeholder Role/Responsibility Status
City of Beech Grove
Collect and store traffic data
Analyze traffic data for planning purposes
Existing
Existing
City of Lawrence
Collect and store traffic data
Existing
Analyze traffic data for planning purposes
Existing
Collect and store traffic data
Existing
Indiana Department of Analyze traffic data for planning purposes
Existing
Transportation Provide traffic data to requesting agencies
Existing
Assist universities with research as needed
Existing
Collect and store traffic data
Existing
Analyze traffic data for planning purposes
Existing
Indiana Department of
Provide traffic data to requesting agencies
Existing
Transportation District Level
Provide traffic data to TrafficWise website
Planned
Provide traffic data to 511
Planned
Indiana State Police Collect and store incident reports Existing
Collect and store traffic data
Existing
Indianapolis Department of
Analyze traffic data for planning purposes
Existing
Public Works
Provide traffic data to requesting agencies
Existing
Indianapolis Downtown, Inc. Collect and store parking data Existing
Indianapolis Fire Department Collect and store incident reports Existing
Indianapolis Metropolitan
Police Department
Collect and store incident reports
Existing
Collect and store traffic and parking data
Existing
Indianapolis MPO
Analyze traffic and parking data for planning purposes Existing
Provide traffic data to requesting agencies
Existing
Indianapolis Public
Transportation
Corporation/IndyGo
Suburban Municipalities
Surrounding Counties
Town of Speedway
Traffic Data Archive Users
Group
Universities
Support online traffic data archive
Collect and store traffic data
Analyze traffic data for planning purposes
Collect and store traffic data
Analyze traffic data for planning purposes
Collect and store traffic data
Analyze traffic data for planning purposes
Collect and store traffic data
Analyze traffic data for planning purposes
Access online traffic data
Analyze traffic data for research purposes
Distribute research results
Future
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Future
Existing
Existing
3.2.2 Emergency Management
Emergency management encompasses the detection of, response to, and coordination for regional
emergencies and large-scale disasters (including evacuations). Stakeholders involved in this area
work together to plan and implement response plans for emergencies that arise on the surface
transportation system. Table 6 defines roles and responsibilities of the various participating
stakeholders.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 29
FINAL REPORT, Version 3.0

Table 6 Emergency Management Roles and Responsibilities
Stakeholder Role/Responsibility Status
Receive and process emergency calls
Existing
Ambulance/Emergency
Respond to emergencies
Existing
Services
Provide emergency medical services
Existing
Receive and process emergency calls
Existing
Respond to emergencies
Existing
City of Beech Grove Provide emergency medical services
Existing
Establish emergency command (local routes)
Existing
Support evacuation
Existing
Receive and process emergency calls
Existing
Respond to emergencies
Existing
City of Lawrence Provide emergency medical services
Existing
Establish emergency command (local routes)
Existing
Support evacuation
Existing
Coordinate emergency response between agencies Existing
CTASC
Enact emergency plans
Existing
Enact evacuation plan
Existing
Coordinate emergency response between agencies Existing
Event Promoters/Special Events Enact emergency plans
Existing
Support evacuation
Existing
Indiana Department of Coordinate emergency response between agencies Existing
Transportation Enact evacuation plan
Existing
Receive and process emergency calls
Existing
Indiana Department of
Respond to emergencies
Existing
Transportation District Level
Support evacuation
Existing
Receive and process emergency calls
Existing
Indiana State Police
Respond to emergencies
Existing
Establish emergency command (state routes)
Existing
Support evacuation
Existing
Receive and process emergency calls
Existing
Establish emergency command (on-site)
Existing
Indianapolis Airport Authority Coordinate emergency response between agencies Existing
Enact emergency plans
Existing
Respond to emergencies
Existing
Coordinate emergency response between agencies Existing
Indianapolis Capital
Enact emergency plans
Existing
Improvements Board
Enact evacuation plan
Existing
Receive and process emergency calls
Existing
Indianapolis Department of
Respond to emergencies
Existing
Public Works
Support evacuation
Existing
Coordinate emergency response between agencies Existing
Indianapolis Emergency
Enact emergency plans
Existing
Management Agency
Enact evacuation plan
Existing
Receive and process emergency calls
Existing
Indianapolis Fire Department Respond to emergencies
Existing
Provide emergency medical services
Existing
Receive and process emergency calls
Existing
Indianapolis Metropolitan Respond to emergencies
Existing
Police Department Establish emergency command (local routes)
Existing
Support evacuation
Existing
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 30
FINAL REPORT, Version 3.0

Stakeholder Role/Responsibility Status
Coordinate emergency response between agencies Existing
Indianapolis Motor Speedway Enact emergency plans
Existing
Enact evacuation plan
Existing
Indianapolis Public Respond to emergencies
Existing
Transportation
Corporation/IndyGo Support evacuation
Existing
Receive and process emergency calls
Existing
Respond to emergencies
Existing
Indianapolis Schools Establish emergency command (on-site)
Existing
Enact emergency plans
Existing
Enact evacuation plan
Existing
Respond to emergencies
Existing
Major Employers
Enact emergency plans
Existing
Establish emergency command (on-site)
Existing
Enact evacuation plan
Existing
MECA System Users
Receive and process emergency calls
Existing
Respond to emergencies
Existing
Media Services Initiate general emergency warnings Existing
Meridian Environmental
Technology
Initiate weather emergency warnings
Existing
National Weather Service Initiate weather emergency warnings Existing
Railroad Agencies
Coordinate emergency response between agencies Existing
Enact emergency plans
Existing
Receive and process emergency calls
Existing
Respond to emergencies
Existing
Suburban Municipalities Provide emergency medical services
Existing
Establish emergency command (local routes)
Existing
Support evacuation
Existing
Receive and process emergency calls
Existing
Respond to emergencies
Existing
Surrounding Counties Provide emergency medical services
Existing
Establish emergency command (local routes)
Existing
Support evacuation
Existing
Towing Operators Respond to emergencies Existing
Receive and process emergency calls
Existing
Respond to emergencies
Existing
Town of Speedway Provide emergency medical services
Existing
Establish emergency command (local routes)
Existing
Support evacuation
Existing
Utility Companies Respond to emergencies Existing
3.2.3 Emissions Management
Emissions management involves the measurement and monitoring of regional air quality to
ensure compliance with air quality standards. Participating stakeholders and their respective
roles/responsibilities are listed in Table 7.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 31
FINAL REPORT, Version 3.0

Table 7 Emissions Management Roles and Responsibilities
Stakeholder Role/Responsibility Status
Indiana Department of
Environmental Management
Monitor air quality
Existing
Indianapolis DPW Office of
Sustainability
Air quality planning and data storage
Existing
3.2.4 Freeway Management
Freeway management includes the monitoring and control of regional freeways. Freeway
incident management, including hazardous material incidents, is addressed in the incident
management/response areas. In the Indianapolis region, the Indiana Department of
Transportation is responsible for freeway management, as shown in Table 8.
Table 8 Freeway Management Roles and Responsibilities
Stakeholder Role/Responsibility Status
Indiana Department of
Transportation
Monitor freeway system
Existing
Monitor freeway system
Existing
Detect and verify incidents on freeway
Existing
Indiana Department of Manage freeway service patrols
Existing
Transportation District Level Install and operate ITS freeway devices to collect and
disseminate data
Existing
Determine alternate routes for freeways
Existing
Indiana State Police Monitor vehicle speeds (state routes) Existing
3.2.5 HAZMAT Response
HAZMAT response addresses on-site response activities for regional incidents that involve
hazardous materials. This area is a specialized subset of the Incident Management area.
Members of this role and responsibility area are specially trained for hazardous material incident
response. Table 9 shows HAZMAT response stakeholder roles and responsibilities.
Table 9 HAZMAT Response Roles and Responsibilities
Stakeholder Role/Responsibility Status
Respond to HAZMAT incidents
Existing
Ambulance/Emergency
Provide emergency medical services at HAZMAT
Services
Existing
incidents
Respond to HAZMAT incidents (local routes)
Existing
Establish HAZMAT incident command (local routes) Existing
Isolate HAZMAT incident site (local routes)
Existing
City of Beech Grove Provide traffic control at HAZMAT incident sites (local
routes)
Existing
Coordinate HAZMAT incident site cleanup (local routes) Existing
Provide HAZMAT aid to other responders
Existing
Request HAZMAT incident response aid when necessary Existing
Respond to HAZMAT incidents (local routes)
Existing
City of Lawrence Establish HAZMAT incident command (local routes) Existing
Isolate HAZMAT incident site (local routes)
Existing
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 32
FINAL REPORT, Version 3.0

Stakeholder Role/Responsibility Status
Provide traffic control at HAZMAT incident sites (local
routes)
Existing
Coordinate HAZMAT incident site cleanup (local routes) Existing
Provide HAZMAT aid to other responders
Existing
Request HAZMAT incident response aid when necessary Existing
Respond to HAZMAT incidents
Existing
Provide traffic control at HAZMAT incident sites (state
Indiana Department of routes)
Existing
Transportation District Level Coordinate HAZMAT incident site cleanup (state routes) Existing
Coordinate HAZMAT incident response between
agencies (state routes)
Existing
Respond to HAZMAT incidents
Existing
Isolate HAZMAT incident site (state routes)
Existing
Indiana State Police
Coordinate HAZMAT incident response between
Existing
agencies (state routes)
Respond to HAZMAT incidents (on-site)
Existing
Establish HAZMAT incident command (on-site)
Existing
Indianapolis Airport Authority Coordinate HAZMAT incident site cleanup (on-site) Existing
Provide HAZMAT aid to other responders
Existing
Request HAZMAT incident response aid when necessary Existing
Respond to HAZMAT incidents
Existing
Provide traffic control at HAZMAT incident sites (local
Indianapolis Department of routes)
Existing
Public Works Coordinate HAZMAT incident site cleanup (local routes) Existing
Provide HAZMAT aid to other responders
Existing
Request HAZMAT incident response aid when necessary Existing
Indianapolis Emergency Coordinate large-scale HAZMAT incident response
Management Agency between agencies
Existing
Respond to HAZMAT incidents (local and state routes) Existing
Establish HAZMAT incident command (local and state
routes)
Existing
Indianapolis Fire Department Coordinate HAZMAT incident response (local and state
routes)
Existing
HAZMAT incident site cleanup (local and state routes) Existing
Provide HAZMAT aid to other responders
Existing
Request HAZMAT incident response aid when necessary Existing
Respond to HAZMAT incidents
Existing
Indianapolis Metropolitan Isolate HAZMAT incident site (local routes)
Existing
Police Department Coordinate HAZMAT incident response between
Existing
agencies (local routes)
Isolate HAZMAT incident site (local routes)
Existing
Coordinate HAZMAT incident response between
Indianapolis Airport Authority agencies (local routes)
Existing
Respond to HAZMAT incidents (on-site)
Existing
Respond to HAZMAT incidents (on-site)
Existing
Major Employers
Establish HAZMAT incident command (on-site)
Existing
Coordinate HAZMAT incident site cleanup (on-site) Existing
Request HAZMAT incident response aid when necessary Existing
Respond to HAZMAT incidents (local routes)
Existing
Establish HAZMAT incident command (local routes) Existing
Isolate HAZMAT incident site (local routes)
Existing
Suburban Municipalities
Provide traffic control at HAZMAT incident sites (local
Existing
routes)
Coordinate HAZMAT incident site cleanup (local routes) Existing
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 33
FINAL REPORT, Version 3.0

Stakeholder Role/Responsibility Status
Provide HAZMAT aid to other responders
Existing
Request HAZMAT incident response aid when necessary Existing
Respond to HAZMAT incidents (local routes)
Existing
Establish HAZMAT incident command (local routes) Existing
Isolate HAZMAT incident site (local routes)
Existing
Surrounding Counties
Provide traffic control at HAZMAT incident sites (local
routes)
Existing
Coordinate HAZMAT incident site cleanup (local routes) Existing
Provide HAZMAT aid to other responders
Existing
Request HAZMAT incident response aid when necessary Existing
Towing Operators
Respond to HAZMAT incidents (local and state routes) Existing
HAZMAT incident site cleanup (local and state routes) Existing
Respond to HAZMAT incidents (local routes)
Existing
Establish HAZMAT incident command (local routes) Existing
Isolate HAZMAT incident site (local routes)
Existing
Town of Speedway
Provide traffic control at HAZMAT incident sites (local
routes)
Existing
Coordinate HAZMAT incident site cleanup (local routes) Existing
Provide HAZMAT aid to other responders
Existing
Request HAZMAT incident response aid when necessary Existing
3.2.6 Incident Management
Building on the Emergency Management area, incident management involves on-site response
activities for both planned (e.g., construction) and unplanned (e.g., vehicle crashes) regional
incidents. Table 10 shows stakeholders roles and responsibilities that apply to this area:
Table 10 Incident Management Roles and Responsibilities
Stakeholder Role/Responsibility Status
Ambulance/Emergency Respond to incidents
Existing
Services
Provide emergency medical services at incidents
Existing
Respond to incidents
Existing
Establish incident command (local routes)
Existing
City of Beech Grove Provide traffic control at incident sites (local routes) Existing
Coordinate incident site cleanup (local routes)
Existing
Create incident reports
Existing
Respond to incidents
Existing
Establish incident command (local routes)
Existing
City of Lawrence Provide traffic control at incident sites (local routes) Existing
Coordinate incident site cleanup (local routes)
Existing
Create incident reports
Existing
Event Promoters/Special Events Develop special event traffic plans Existing
Respond to incidents
Existing
Indiana Department of
Provide traffic control at incident sites (state routes) Existing
Transportation District Level
Coordinate incident site cleanup (state routes)
Existing
Create incident reports
Existing
Respond to incidents
Existing
Indiana State Police Establish incident command (state routes)
Existing
Create incident reports
Existing
Indianapolis Department of Respond to incidents
Existing
Public Works Provide traffic control at incident sites (local routes) Existing
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 34
FINAL REPORT, Version 3.0

Stakeholder Role/Responsibility Status
Coordinate incident site cleanup (local routes)
Existing
Create incident reports
Existing
Indianapolis Downtown, Inc. Develop special event traffic plans Existing
Indianapolis Fire Department
Respond to incidents
Existing
Create incident reports
Existing
Respond to incidents
Existing
Indianapolis Metropolitan
Establish incident command (local routes)
Existing
Police Department
Create incident reports
Existing
Indianapolis Motor Speedway Develop special event traffic plans Existing
Major Employers Develop traffic plans Existing
Railroad Agencies Develop incident response plans Existing
Respond to incidents
Existing
Establish incident command (local routes)
Existing
Suburban Municipalities Provide traffic control at incident sites (local routes) Existing
Coordinate incident site cleanup (local routes)
Existing
Create incident reports
Existing
Respond to incidents
Existing
Establish incident command (local routes)
Existing
Surrounding Counties Provide traffic control at incident sites (local routes) Existing
Coordinate incident site cleanup (local routes)
Existing
Create incident reports
Existing
Towing Operators
Respond to incidents
Existing
Provide incident site cleanup (local and state routes) Existing
Respond to incidents
Existing
Establish incident command (local routes)
Existing
Town of Speedway Provide traffic control at incident sites (local routes) Existing
Coordinate incident site cleanup (local routes)
Existing
Create incident reports
Existing
3.2.7 Maintenance and Construction
Maintenance and construction activities occur on all routes within the regional roadway network.
Table 11 lists the transportation agency roles and responsibilities for the stakeholders.
Table 11 Maintenance and Construction Roles and Responsibilities
Stakeholder Role/Responsibility Status
Maintain local routes including snow and ice control,
pavement maintenance, and ITS devices (including traffic Existing
City of Beech Grove signals)
Coordinate construction activities with other maintenance
and construction agencies
Existing
Maintain local routes including snow and ice control,
pavement maintenance, and ITS devices (including traffic Existing
City of Lawrence signals)
Coordinate construction activities with other maintenance
and construction agencies
Existing
Indiana Department of Coordinate construction planning with other maintenance
Transportation and construction agencies
Existing
Maintain state routes including snow and ice control,
Indiana Department of
pavement maintenance, and ITS devices (including traffic
Transportation District Level
signals)
Existing
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 35
FINAL REPORT, Version 3.0

Stakeholder Role/Responsibility Status
Install and operate RWIS sensors to collect road weather
data
Existing
Coordinate construction activities with other maintenance
and construction agencies
Existing
Indianapolis Airport Authority
Maintain on-site and local routes including snow and ice
control, pavement maintenance, and ITS devices
Existing
Coordinate construction activities with other maintenance
and construction agencies
Existing
Maintain local routes including snow and ice control,
pavement maintenance, and ITS devices (including traffic Existing
signals)
Indianapolis Department of
Install and operate RWIS sensors to collect road weather
Public Works
data
Existing
Coordinate construction activities with other maintenance
and construction agencies
Existing
Indianapolis MPO
Coordinate construction planning between maintenance
and construction agencies
Existing
Provide maintenance of ITS devices, including traffic
Private Maintenance
signals, DMS, CCTV, HAR, vehicle detection, and
Companies
lighting systems
Existing
RWIS Users
Install and operate RWIS sensors to collect road weather
data
Existing
Coordinate construction activities with other maintenance
and construction agencies
Existing
Suburban Municipalities Maintain local routes including snow and ice control,
pavement maintenance, and ITS devices (including traffic Existing
signals)
Coordinate construction activities with other maintenance
and construction agencies
Existing
Surrounding Counties Maintain local routes including snow and ice control,
pavement maintenance, and ITS devices (including traffic Existing
signals)
Coordinate construction activities with other maintenance
and construction agencies
Existing
Town of Speedway Maintain local routes including snow and ice control,
pavement maintenance, and ITS devices (including traffic
signals)
Existing
3.2.8 Parking Management
Parking management involves the operation and management of regional parking systems. In
the Indianapolis region, the Indianapolis Airport Authority and Indianapolis Downtown, Inc. are
responsible for parking management activities as shown in Table 12.
Table 12 Parking Management Roles and Responsibilities
Stakeholder Role/Responsibility Status
Maintain inventory of airport parking facilities
Existing
Monitor airport parking
Existing
Indianapolis Airport Authority
Receive, process, and respond to online parking
Existing
reservation requests
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 36
FINAL REPORT, Version 3.0

Stakeholder Role/Responsibility Status
Develop special event parking plans
Existing
Facilitate transit parking programs (i.e. park and ride) Existing
Indianapolis Downtown, Inc. Maintain inventory of Downtown parking garages Existing
Monitor Downtown parking
Existing
Monitor meter occupancy levels
Existing
3.2.9 Surface Street Management
Like the Freeway Management area, surface street management addresses the monitoring and
control of state and local non-freeway routes. This includes the operation of traffic signals
(including those at highway-rail intersections) and the coordination of signal operations across
jurisdictional boundaries. Table 13 shows roles and responsibilities in this area:
Table 13 Surface Street Management Roles and Responsibilities
Stakeholder Role/Responsibility Status
Install and operate traffic signals (local routes)
Existing
City of Beech Grove Determine alternate routes for surface streets (local
routes)
Existing
Install and operate traffic signals (local routes)
Existing
City of Lawrence Determine alternate routes for surface streets (local
routes)
Existing
Install and operate traffic signals (state routes)
Existing
Install and operate ITS surface street devices to collect
and disseminate data (state routes)
Existing
Indiana Department of Monitor surface street system (state routes)
Existing
Transportation District Level Detect and verify incidents on surface street system (state
routes)
Planned
Determine alternate routes for surface streets (state
routes)
Existing
Indianapolis Airport Authority
Install and operate traffic signals (on-site and local
routes)
Existing
Install and operate ITS surface street devices to collect
and disseminate data (on-site)
Planned
Install and operate traffic signals (local routes)
Existing
Install and operate ITS surface street devices to collect
and disseminate data (local routes)
Planned
Indianapolis Department of Manage Downtown wayfinding sign system
Existing
Public Works Monitor surface street system (local routes)
Planned
Detect and verify incidents on surface street system (local
routes)
Planned
Determine alternate routes for surface streets (local
routes)
Existing
Indianapolis Downtown, Inc. Manage Downtown wayfinding sign system Existing
Install and operate traffic signals (local routes)
Existing
Suburban Municipalities Determine alternate routes for surface streets (local
routes)
Existing
Install and operate traffic signals (local routes)
Existing
Surrounding Counties Determine alternate routes for surface streets (local
routes)
Existing
Install and operate traffic signals (local routes)
Existing
Town of Speedway Determine alternate routes for surface streets (local
routes)
Existing
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 37
FINAL REPORT, Version 3.0

3.2.10 Transit Services
Transit services include the operation and management of regional transit systems, including both
fixed-route operations and demand-response transit. Transit service roles and responsibilities are
shown in Table 14.
Table 14 Transit Services Roles and Responsibilities
Stakeholder Role/Responsibility Status
Central Indiana Regional
Transportation Authority
Plan, coordinate, and operate regional transit initiatives Planned
Clarian Health Partners Operate and maintain people mover Existing
Indianapolis Airport Authority Provide airport-to-parking facility shuttle services Existing
Provide fixed route bus services for the region
Existing
Provide paratransit service for the region
Existing
Indianapolis Public
Transportation
Provide on-board functionality needed to implement bus
tracking and signal priority at local/state route
Planned
Corporation/IndyGo intersections
Manage regional ridesharing program (Central Indiana
Commuter Services)
Existing
Indianapolis Schools Provide fixed route school bus services for the region Existing
Taxi Companies
Provide regional demand-responsive transportation
service
Existing
3.2.11 Transportation Security
Transportation security encompasses all regional surface transportation system infrastructure
security monitoring. This area includes stakeholders that are responsible for the monitoring and
protection of the surface transportation system, as shown in Table 15. The roles and
responsibilities of the Regional Transportation Authority (RTA) will be included in this section as
they become more clearly defined.
Table 15 Transportation Security Roles and Responsibilities
Stakeholder Role/Responsibility Status
CTASC
Monitor video surveillance information received from
other agencies
Planned
Indiana Department of
Transportation
Monitor infrastructure (state routes)
Existing
Monitor infrastructure (state routes)
Existing
Indiana Department of
Provide video surveillance information video to
Transportation District Level
Planned
authorized security agencies
Indiana State Police
Monitor video surveillance information received from
other agencies
Existing
Indianapolis Airport Authority Monitor infrastructure (on-site) Existing
Indianapolis Department of
Public Works
Monitor infrastructure (local routes)
Future
Indianapolis Emergency
Management Agency
Monitor infrastructure (local routes)
Existing
Indianapolis Metropolitan
Police Department
Monitor infrastructure (local routes)
Existing
Indianapolis Public
Transportation Monitor infrastructure (in-vehicle)
Planned
Corporation/IndyGo
Railroad Agencies Monitor infrastructure (rail system) Existing
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 38
FINAL REPORT, Version 3.0

3.2.12 Traveler Information
This area addresses the regional dissemination of traveler information through both existing
infrastructures (e.g., radio and television) and real-time interactive request/response systems (e.g.,
Internet or 511). Participating stakeholders are shown in Table 16.
Table 16 Traveler Information Roles and Responsibilities
Stakeholder Role/Responsibility Status
Event Promoters/Special Events Maintain special event website Existing
Indiana Department of Disseminate traffic, incident, and maintenance
Transportation information via 511 system
Planned
Disseminate traffic, incident, and maintenance
information to travelers and the media
Existing
Disseminate traffic, incident, and maintenance
information to emergency management agencies
Existing
Indiana Department of Disseminate traffic, incident, and maintenance
Transportation District Level information to freeway service patrols
Existing
Disseminate traffic, incident, and maintenance
information via Trafficwise website
Planned
Disseminate traffic, incident, and maintenance
information via 511 system
Planned
Indianapolis Airport Authority
Maintain airport website (online parking reservations,
etc.)
Existing
Disseminate traffic, incident, and maintenance
information to travelers and the media
Existing
Indianapolis Capital
Improvements Board
Maintain convention center information kiosks
Existing
Indianapolis Downtown, Inc.
Maintain website (downtown tourism)
Existing
Publish parking statistics
Existing
Maintain IndyGo website (schedules, fares, etc.)
Existing
Indianapolis Public Maintain transit information hotline
Existing
Transportation Maintain Central Indiana Commuter Services website
Corporation/IndyGo (online ridesharing reservations)
Existing
Disseminate real-time arrival data
Future
Disseminate traffic video surveillance data
Existing
Media Services Disseminate traffic video surveillance data provided by
others
Planned
Meridian Environmental Provide value-added weather information
Existing
Technology
Provide weather alerts
Existing
National Weather Service
Provide weather information
Existing
Provide weather alerts
Existing
Traveling Motorists Report traffic and incident info to emergency services Existing
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 39
FINAL REPORT, Version 3.0

4.0 Functional Requirements
After identifying the systems and services of an intelligent transportation system, functional
requirements are used to define what the systems must do to perform their services. It is
important to note that these functional requirements are, like the architecture itself, independent
of specific technologies.
To help identify appropriate functional requirements for the systems of an architecture, the
National ITS Architecture contains ‘equipment packages’ that group together similar processes of
a subsystem into “implementable” packages. These equipment packages are also tied to the 85
market packages of the National ITS Architecture.
Table 17 provides a listing of the applicable equipment packages for the Indianapolis region,
along with the associated element and architecture entity (subsystem) for each. In addition, there
are a number of individual functional requirement statements under each equipment package.
Due to the high level of detail inherent to these functional requirements, they should be viewed
using the Turbo Architecture® tool.
Table 17 Indianapolis Equipment Packages (Functional Areas) Inventory
Element Architecture Entity Equipment Package
511 Traveler
Information
Ambulance Dispatch
Ambulance
Vehicles
Beech Grove Public
Safety
Beech Grove Public
Works
Information Service
Provider
Emergency Management
Emergency Vehicle
Subsystem
Emergency Management
Maintenance and
Construction
Management
Traffic Management
Basic Information Broadcast
Interactive Infrastructure Information
Traveler Telephone Information
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Response Management
On-board EV En Route Support
On-board EV Incident Management Communication
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Data Collection
MCM Vehicle and Equipment Maintenance
Management
MCM Incident Management
MCM Maintenance Decision Support
MCM Winter Maintenance Management
MCM Infrastructure Monitoring
MCM Roadway Maintenance and Construction
MCM Work Zone Management
MCM Data Collection
Collect Traffic Surveillance
TMC Signal Control
TMC Incident Dispatch
Coordination/Communication
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 40
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
Beech Grove Public
Works (cont.)
Beech Grove
Vehicles
Beech Grove
Roadside Equipment
CICS Website
Downtown Event
Promoter
Emergency
Operations Center
IMPD Dispatch
IMPD Emergency
Vehicles
IMPD Security
Monitoring Field
Equipment
IMS Command
Center
Indiana Intelligence
Fusion Center
Traffic Management
(cont.)
Emergency Vehicle
Subsystem
Maintenance and
Construction Vehicle
Roadway Subsystem
Information Service
Provider
Information Service
Provider
Emergency Management
Emergency Management
Emergency Vehicle
Subsystem
Security Monitoring
Field Equipment
Emergency Management
Traffic Management
Emergency Management
HRI Traffic Management
Traffic Maintenance
TMC Work Zone Traffic Management
Traffic Data Collection
On-board EV En Route Support
On-board EV Incident Management Communication
MCV Winter Maintenance
MCV Roadway Maintenance and Construction
MCV Work Zone Support
Roadway Basic Surveillance
Roadway Signal Controls
Standard Rail Crossing
Roadway Signal Priority
Roadway Equipment Coordination
Roadway Work Zone Traffic Control
Infrastructure Provided Dynamic Ridesharing
Interactive Infrastructure Information
Emergency Call-Taking
Emergency Dispatch
Emergency Early Warning System
Emergency Response Management
Emergency Evacuation Support
Emergency Environmental Monitoring
Center Secure Area Surveillance
Center Secure Area Sensor Management
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Data Collection
On-board EV En Route Support
On-board EV Incident Management Communication
Field Secure Area Sensor Monitoring
Field Secure Area Surveillance
Emergency Call-Taking
Emergency Dispatch
Emergency Response Management
Incident Command
TMC Incident Dispatch
Coordination/Communication
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Environmental Monitoring
Center Secure Area Surveillance
Center Secure Area Sensor Management
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 41
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
Emergency Vehicle
Subsystem
Indianapolis Airport
Emergency Vehicles
Indianapolis Airport
Field Devices
Indianapolis Airport
Maintenance Vehicles
Indianapolis Airport
Management Systems
Indianapolis Airport
Parking Systems
Indianapolis DPW
Operations Center
Roadway Subsystem
Security Monitoring
Subsystem
Maintenance and
Construction Vehicle
Emergency Management
Maintenance and
Construction
Management
Traffic Management
Parking Management
Emergency Management
Emissions Management
Maintenance and
Construction
Management
Traffic Management
On-board EV Incident Management Communication
Roadway Traffic Information Dissemination
Roadway Environmental Monitoring
Field Barrier System Control
Field Safeguard System Control
Field Secure Area Sensor Monitoring
Field Secure Area Surveillance
MCV Winter Maintenance
MCV Roadway Maintenance and Construction
Emergency Call-Taking
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Environmental Monitoring
Center Secure Area Surveillance
Center Secure Area Sensor Management
MCM Vehicle and Equipment Maintenance
Management
MCM Environmental Information Processing
MCM Incident Management
MCM Maintenance Decision Support
MCM Winter Maintenance Management
MCM Roadway Maintenance and Construction
MCM Work Zone Management
Barrier System Management
Parking Surveillance
Parking Management
Parking Electronic Payment
Emergency Call-Taking
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Environmental Monitoring
Emergency Data Collection
Emissions Data Management
Emissions Data Collection
MCM Vehicle and Equipment Maintenance
Management
MCM Environmental Information Collection
MCM Environmental Information Processing
MCM Incident Management
MCM Maintenance Decision Support
MCM Winter Maintenance Management
MCM Roadway Maintenance and Construction
MCM Work Zone Management
MCM Work Activity Coordination
MCM Data Collection
Collect Traffic Surveillance
TMC Traffic Information Dissemination
TMC Incident Detection
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 42
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
TMC Incident Dispatch
Coordination/Communication
TMC Evacuation Support
TMC Environmental Monitoring
TMC Signal Control
HRI Traffic Management
TMC Regional Traffic Management
TMC Reversible Lane Management
Traffic Maintenance
TMC Work Zone Traffic Management
TMC Multimodal Coordination
Traffic Data Collection
Indianapolis DPW
Vehicles
Indianapolis DPW
Roadside Equipment
Indianapolis Fire
Communications
Center
Indianapolis Fire
Department
Emergency Vehicles
Indianapolis MPO
INDOT Arterial
Traffic Mgmt. System
INDOT Arterial
Traffic Mgmt.
Roadside Equipment
INDOT Hoosier
Helper Vehicles
INDOT Indianapolis
TMC
Maintenance and
Construction Vehicle
Roadway Subsystem
Emergency Management
Emergency Vehicle
Subsystem
Information Service
Provider
Traffic Management
Roadway Subsystem
Emergency Vehicle
Subsystem
Emergency Management
MCV Vehicle Location Tracking
MCV Winter Maintenance
MCV Roadway Maintenance and Construction
MCV Work Zone Support
Roadway Signal Controls
Roadway Signal Priority
Standard Rail Crossing
Roadway Equipment Coordination
Roadway Reversible Lanes
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Mayday Support
Emergency Data Collection
On-board EV En Route Support
On-board EV Incident Management Communication
ISP Data Collection
Collect Traffic Surveillance
TMC Signal Control
TMC Regional Traffic Management
HRI Traffic Management
Traffic Maintenance
Roadway Basic Surveillance
Roadway Signal Controls
Roadway Signal Priority
Standard Rail Crossing
Roadway Equipment Coordination
On-board EV En Route Support
On-board EV Incident Management Communication
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Early Warning System
Emergency Response Management
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 43
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
Incident Command
Emergency Evacuation Support
Emergency Environmental Monitoring
Center Secure Area Surveillance
Center Secure Area Sensor Management
Service Patrol Management
Emergency Data Collection
INDOT Indianapolis
TMC Roadside
Equipment
INDOT MCO Field
Devices
INDOT MCO
Management
INDOT MCO
Vehicles
Information Service
Provider
Traffic Management
Roadway Subsystem
Roadway Subsystem
Maintenance and
Construction
Management
Maintenance and
Construction Vehicle
Basic Information Broadcast
Interactive Infrastructure Information
Traveler Telephone Information
Infrastructure Provided Trip Planning
ISP Emergency Traveler Information
ISP Data Collection
Collect Traffic Surveillance
TMC Traffic Information Dissemination
TMC Incident Detection
TMC Incident Dispatch
Coordination/Communication
TMC Evacuation Support
TMC Traffic Network Performance Evaluation
TMC Environmental Monitoring
Traffic Maintenance
TMC Work Zone Traffic Management
TMC In-Vehicle Signing Management
Traffic Data Collection
Roadway Basic Surveillance
Roadway Traffic Information Dissemination
Roadway Incident Detection
Roadway Equipment Coordination
Roadway Work Zone Traffic Control
Roadway Short Range Traveler Information
Communications
Traffic and Roadside Data Archival
Government Reporting Systems Support
Roadway Traffic Information Dissemination
Roadway Automated Treatment
Roadway Work Zone Traffic Control
MCM Vehicle Tracking
MCM Vehicle and Equipment Maintenance
Management
MCM Environmental Information Collection
MCM Environmental Information Processing
MCM Automated Treatment System Control
MCM Incident Management
MCM Maintenance Decision Support
MCM Winter Maintenance Management
MCM Infrastructure Monitoring
MCM Roadway Maintenance and Construction
MCM Work Zone Management
MCM Data Collection
MCV Winter Maintenance
MCV Roadway Maintenance
and Construction
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 44
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
MCV Work Zone Support
Security Monitoring
Field Secure Area Surveillance
Subsystem
Field Secure Area Sensor Monitoring
INDOT Security
Monitoring Field
Equipment
IndyGo Kiosks
IndyGo Operations
Center
IndyGo Security
Monitoring Field
Equipment
IndyGo Transit
Displays
IndyGo Transit
Vehicles
IndyGo Website
ISP Dispatch
Remote Traveler Support
Archived Data
Management Subsystem
Emergency Management
Information Service
Provider
Transit Management
Remote Traveler Support
Security Monitoring
Subsystem
Remote Traveler Support
Transit Vehicle
Subsystem
Information Service
Provider
Emergency Management
Remote Interactive Information Reception
Remote Transit Information Services
Remote Transit Fare Management
ITS Data Repository
Government Reporting Systems Support
Emergency Response Management
Incident Command
Emergency Evacuation Support
Center Secure Area Surveillance
Center Secure Area Sensor Management
Center Secure Area Alarm Support
Emergency Data Collection
Interactive Infrastructure Information
Infrastructure Provided Trip Planning
Infrastructure Provided Dynamic Ridesharing
ISP Data Collection
Transit Center Tracking and Dispatch
Transit Center Fixed-Route Operations
Transit Center Paratransit Operations
Transit Center Fare Management
Transit Center Security
Transit Garage Operations
Transit Garage Maintenance
Transit Center Information Services
Transit Center Multi-Modal Coordination
Transit Center Signal Priority
Transit Evacuation Support
Transit Vehicle Operator Assignment
Transit Data Collection
Traveler Secure Area Surveillance
Traveler Secure Area Sensor Monitoring
Remote Traveler Security
Field Secure Area Surveillance
Field Secure Area Sensor Monitoring
Remote Transit Information Services
On-board Transit Trip Monitoring
On-board Fixed Route Schedule Management
On-board Paratransit Operations
On-board Passenger Counting
On-board Transit Fare Management
On-board Transit Security
On-board Maintenance
On-board Transit Signal Priority
On-board Transit Information Services
Basic Information Broadcast
Infrastructure Provided Trip Planning
Emergency Call-Taking
Emergency Dispatch
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 45
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
Emergency Routing
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Data Collection
Information Service
Provider
Traveler Telephone Information
ISP Emergency Traveler Information
ISP Emergency
Vehicles
Lawrence Public
Safety
Lawrence Public
Works/Street
Department
Lawrence Vehicles
Lawrence Roadside
Equipment
Major Employer
Emergency Vehicles
Major Employer
Management Systems
Traffic Management
Emergency Vehicle
Subsystem
Emergency Management
Maintenance and
Construction
Management
Traffic Management
Emergency Vehicle
Subsystem
Maintenance and
Construction Vehicle
Roadway Subsystem
Emergency Vehicle
Subsystem
Emergency Management
TMC Speed Monitoring
On-board EV En Route Support
On-board EV Incident Management Communication
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Data Collection
MCM Vehicle and Equipment Maintenance
Management
MCM Incident Management
MCM Maintenance Decision Support
MCM Winter Maintenance Management
MCM Infrastructure Monitoring
MCM Roadway Maintenance and Construction
MCM Work Zone Management
MCM Data Collection
Collect Traffic Surveillance
TMC Signal Control
TMC Incident Dispatch
Coordination/Communication
HRI Traffic Management
Traffic Maintenance
TMC Work Zone Traffic Management
Traffic Data Collection
On-board EV En Route Support
On-board EV Incident Management Communication
MCV Winter Maintenance
MCV Roadway Maintenance and Construction
MCV Work Zone Support
Roadway Basic Surveillance
Roadway Signal Controls
Roadway Signal Priority
Standard Rail Crossing
Roadway Equipment Coordination
Roadway Work Zone Traffic Control
On-board EV En Route Support
On-board EV Incident Management Communication
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Response Management
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 46
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
Incident Command
MECA System
Emergency Call-Taking
Emergency Call-Taking
Private Towing
Emergency Dispatch
Companies Emergency Management
Emergency Response Management
Lucas Oil Stadium
Command Center
RWIS Sensors
School Buses
School Police
Departments
Speedway Public
Safety
Speedway Public
Works
Speedway Vehicles
Speedway Roadside
Equipment
Roadway Subsystem
Transit Management
Emergency Management
Maintenance and
Construction
Management
Traffic Management
Emergency Vehicle
Subsystem
Maintenance and
Construction Vehicle
Roadway Subsystem
Emergency Call-Taking
Emergency Dispatch
Emissions Data Management
Emissions Data Collection
Roadway Environmental Monitoring
Transit Center Fixed-Route Operations
Transit Garage Operations
Transit Vehicle Operator Assignment
Transit Garage Maintenance
Emergency Call-Taking
Emergency Dispatch
Emergency Response Management
Incident Command
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Data Collection
MCM Vehicle and Equipment Maintenance Mgmt.
MCM Incident Management
MCM Maintenance Decision Support
MCM Winter Maintenance Management
MCM Infrastructure Monitoring
MCM Roadway Maintenance and Construction
MCM Work Zone Management
MCM Data Collection
Collect Traffic Surveillance
TMC Signal Control
TMC Incident Dispatch
Coordination/Communication
HRI Traffic Management
Traffic Maintenance
TMC Work Zone Traffic Management
Traffic Data Collection
On-board EV En Route Support
On-board EV Incident Management Communication
MCV Winter Maintenance
MCV Roadway Maintenance and Construction
MCV Work Zone Support
Roadway Basic Surveillance
Roadway Signal Controls
Roadway Signal Priority
Standard Rail Crossing
Roadway Equipment Coordination
Roadway Work Zone Traffic Control
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 47
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Suburban
Emergency Early Warning System
Municipality Emergency Management
Emergency Response Management
Emergency Dispatch
Incident Command
Emergency Evacuation Support
Emergency Data Collection
Suburban
Municipality
Emergency Vehicles
Suburban
Municipality Street
Department Dispatch
Suburban
Municipality Street
Department Vehicles
Suburban
Municipality Street
Department Roadside
Equipment
Surrounding County
Highway Dispatch
Emergency Vehicle
Subsystem
Maintenance and
Construction
Management
Traffic Management
Maintenance and
Construction Vehicle
Roadway Subsystem
Maintenance and
Construction
Management
Traffic Management
On-board EV En Route Support
On-board EV Incident Management Communication
MCM Vehicle and Equipment Maintenance
Management
MCM Incident Management
MCM Maintenance Decision Support
MCM Winter Maintenance Management
MCM Infrastructure Monitoring
MCM Roadway Maintenance and Construction
MCM Work Zone Management
MCM Data Collection
Collect Traffic Surveillance
TMC Signal Control
TMC Incident Dispatch
Coordination/Communication
HRI Traffic Management
Traffic Maintenance
TMC Work Zone Traffic Management
Traffic Data Collection
MCV Winter Maintenance
MCV Roadway Maintenance and Construction
MCV Work Zone Support
Roadway Basic Surveillance
Roadway Signal Controls
Roadway Signal Priority
Standard Rail Crossing
Roadway Equipment Coordination
Roadway Work Zone Traffic Control
MCM Vehicle and Equipment Maintenance Mgmt.
MCM Incident Management
MCM Maintenance Decision Support
MCM Winter Maintenance Management
MCM Infrastructure Monitoring
MCM Roadway Maintenance and Construction
MCM Work Zone Management
MCM Speed Monitoring
MCM Work Zone Safety Management
MCM Data Collection
Collect Traffic Surveillance
TMC Signal Control
TMC Incident Dispatch
Coordination/Communication
HRI Traffic Management
Traffic Maintenance
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 48
FINAL REPORT, Version 3.0

Element Architecture Entity Equipment Package
TMC Work Zone Traffic Management
Traffic Data Collection
Surrounding County
Highway Vehicles
Surrounding County
Highway Roadside
Equipment
Surrounding County
Security Monitoring
Field Equipment
Surrounding County
Sheriff
Communications
Center
Surrounding County
Sheriff Emergency
Vehicles
Taxi Services
Traffic Data Archive
TrafficWise Website
User Personal
Computing Devices
Utility Emergency
Repair/Response
Maintenance and
Construction Vehicle
Roadway Subsystem
Security Monitoring
Subsystem
Emergency Management
Emergency Vehicle
Subsystem
Transit Management
Archived Data
Management Subsystem
Information Service
Provider
Personal Information
Access
Emergency Management
MCV Winter Maintenance
MCV Roadway Maintenance and Construction
MCV Work Zone Support
Roadway Basic Surveillance
Roadway Signal Controls
Roadway Signal Priority
Standard Rail Crossing
Roadway Equipment Coordination
Roadway Speed Monitoring
Roadway Work Zone Traffic Control
Field Secure Area Sensor Monitoring
Field Secure Area Surveillance
Emergency Call-Taking
Emergency Dispatch
Emergency Routing
Emergency Early Warning System
Emergency Response Management
Incident Command
Emergency Evacuation Support
Emergency Data Collection
On-board EV En Route Support
On-board EV Incident Management Communication
Transit Center Paratransit Operations
Transit Garage Operations
Transit Vehicle Operator Assignment
Transit Garage Maintenance
ITS Data Repository
Traffic and Roadside Data Archival
Government Reporting Systems Support
On-Line Analysis and Mining
Basic Information Broadcast
Interactive Infrastructure Information
Personal Interactive Information Reception
Emergency Call-Taking
Emergency Dispatch
Emergency Response Management
Incident Command
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 49
FINAL REPORT, Version 3.0

5.0 Interfaces and Information Flows
Many of the functional requirements listed in Section 4.0 highlight interactions between the ITS
systems of various regional transportation agencies. These interactions emphasize some of the
benefits that ITS can provide. While traffic sensors and roadway cameras collect information that
is important to a single agency’s operations, the sharing of this information often has a greater
positive effect on the larger regional transportation system.
As demonstrated in Section 2.2, the National ITS Architecture identifies the interactions that
occur between ITS systems to perform services to the traveling public (see Figure 4). The Turbo
Architecture® software tool provides the functionality to display these interactions between
individual ITS systems in a graphical format. Figure 5, the Indianapolis TMC Roadside
Equipment Interconnect Diagram, provides an example of these diagrams. This example shows
how the different subsystems/terminators (with associated stakeholder) are linked. Note that the
status (existing, planned, or future) of those interconnections are also described in the diagram.
Appendix G contains the ‘interconnect diagrams’ for each Indianapolis ITS system. The
architecture also defines the individual bits of information, or ‘architecture flows,’ that are
exchanged between these systems. Due to the high level of detail inherent to the architecture
flows, they should be viewed using the Turbo Architecture® tool.
Indiana Department of Transportation...
INDOT Infrastructure Inventory System
Private Maintenance Companies
ITS Maintenance Contractor
Indiana Department of Transportation...
INDOT Indianapolis TMC
Indiana Department of Transportation...
INDOT Indianapolis TMC_Roadside
Equipment
Existing
Planned
Future
Figure 5 Indianapolis Subsystem Interconnect Diagram
Figure 6 summarizes the various interconnections between the National ITS Architecture
subsystems included in the Indianapolis ITS Architecture. As stated in Section 1.3, commercial
vehicle operations are addressed in the Indiana Statewide ITS Architecture.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 50
FINAL REPORT, Version 3.0

Travelers
Centers
Remote
Traveler Support
Traffic
Management
Emergency
Management
Toll
Administration
Commercial
Vehicle
Administration
Maintenance
and Construction
Management
Personal
Information
Access
Information
Service Provider
Emissions
Management
Transit
Management
Fleet and
Freight
Management
Archived Data
Management
Wide Area Wireless Communications
Fixed-Point to Fixed-Point Communications
Vehicle to Vehicle Communications
Maintenance
and Construction
Vehicle
Transit Vehicle
Commercial
Vehicle
Emergency
Vehicle
Vehicle
Vehicles
Dedicated Short Range
Communications
Roadway
Security
Monitoring
Field
Toll Collection
Parking
Management
Commercial
Vehicle Check
Figure 6 Indianapolis Subsystem Interconnect Diagram
The subsystems that are not a part of the regional ITS architecture are shown in gray, and include
the subsystems related to commercial vehicles (not included in the regional ITS architecture as
stated above) and tolling collection/administration. Currently, toll collection is not being
considered for use in the Indianapolis region. However, should tolling become part of the
regional ITS infrastructure in the future, the appropriate regional ITS architecture revisions will
need to be made at that time.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 51
FINAL REPORT, Version 3.0

6.0 Project Sequencing
Within the timeframe of this report as outlined in Section 1.2, a wide variety of ITS projects are
planned for deployment and/or implementation in the Indianapolis region. These projects involve
many agencies and funding sources, and are identified in an assortment of regional planning
documents.
The purpose of this section of the Indianapolis Regional Architecture is not to document the
projects in detail, but to provide information regarding sequencing and coordination of projects to
ensure current/future ITS projects are deployed and implemented in the most effective manner in
terms of cost, constructability, and functionality. For most of the projects, details such as indepth
project descriptions and construction cost estimates can be found in the various planning
documents listed in Appendix A.
Key current/planned ITS projects in the Indianapolis region are provided in Table 18. This table
provides a deployment year, project title, description, and geographic scope for each key project.
In some cases, the projects listed in may represent several smaller initiatives (e.g., the INDOT
ATMS).
A more detailed listing of all ITS projects in the region over the next 15 years can be found in
Appendix H.
Deployment
Year
1987 MECA
2003 CICS Website
2004
2004
Table 18 Indianapolis ITS Projects Inventory
Project Description Scope
Indiana
Intelligence
Fusion Center
(IIFC)
Road Weather
Information
System (RWIS)
Metropolitan Emergency Communications
Agency - a regional, integrated emergency
communications system that includes
emergency responders, law enforcement,
transportation agencies, and other public
officials in Marion County
Central Indiana Commuter Services
(CICS) is an IndyGo service federally
funded to reduce air pollution and traffic
congestion. CICS offers commuting
solutions to area employers and
employees. These commuting solutions
are alternatives to driving alone, such as
carpooling, vanpooling, riding transit,
biking or walking.
The purpose of Indiana Intelligence Fusion
Center (IIFC), a division of the Indiana
Department of Homeland Security, is to
collect, integrate, evaluate, analyze and
disseminate information and intelligence
to support local, state and federal agencies
in detecting, preventing, and responding to
criminal and terrorist activity.
Road weather information system (RWIS)
sensors owned by INDOT and the City of
Indianapolis collect and distribute real-
Marion County
(excluding the towns of
Speedway, Beech
Grove, and Lawrence)
Entire nine-county
region
The State of Indiana
Indianapolis
metropolitan area
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 52
FINAL REPORT, Version 3.0

Deployment
Year
2006
2007
2007
2007
2008
2008
2008
Project Description Scope
IndyGo Onboard
Surveillance
Cameras
Advanced
Traffic
Management
System (ATMS)
City of
Indianapolis
Signal
Improvement
Projects
Indianapolis
Marion County
Camera Project
511 Traveler
Information
IndyGo AVL
System
IndyGo Trip
Planner
time weather data to both agencies over
the Internet.
IndyGo has installed surveillance cameras
(7 per vehicle) on its buses to record
incidents. Video data is recorded and
stored for a defined period.
An Advanced Traffic Management System
(ATMS) is a system of vehicle detection
and camera information sent to the INDOT
Indianapolis Traffic Management Center
(TMC) which is then distributed to the
public through dynamic message signs,
highway advisory radio, and the
TrafficWise website. The ATMS provides
camera images, overall traffic speed
information, and estimated travel times
between key junctions to TMC operators
and the public.
Various traffic signal improvement
projects in the City of Indianapolis
Cameras deployed at various locations in
Marion County to reduce fatal crashes and
combat high crime areas
On July 21, 2000 the Federal
Communications Commission (FCC)
designated 511 as the single travel
information telephone number to be made
available to states & local jurisdictions
across the country. Indiana is currently
participating in the CARS-511 Pooled
Fund.
IndyGo's automatic vehicle location
(AVL) system is used to track transit
vehicle movements in real-time. This can
be used for measuring schedule adherence,
paratransit operations, and general asset
tracking.
This application displays IndyGo bus
routes and allows a user to plan a trip from
one location to another within the IndyGo
service area. In addition to the routing
functions from the Route Mapper
application, this application allows the
user to constrain the arrival or departure
times.
IndyGo service area
Indianapolis
metropolitan area
City of Indianapolis
Various locations in
Marion County
Statewide
IndyGo service area
IndyGo service area
In addition to the above table (Specified in Appendix H), there is much ITS project activity due to
occur over the course of the next several years in the Indianapolis region. It is imperative that
implementation of these projects be coordinated as described in order to for the region to achieve
optimal ITS benefits from a cost, constructability, and functionality standpoint.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 53
FINAL REPORT, Version 3.0

7.0 Agreements
In the Indianapolis region, a substantial amount of coordination is required between the various
ITS stakeholders to ensure that ITS resources are being utilized in the most efficient possible
manner. In many cases, the coordination is governed via an agreement between stakeholders.
Agreements allow for each party to obtain a clear understanding of what their responsibilities are,
and what they can expect from the other party (or parties) involved. A total of 24 ITS stakeholder
agreements are currently in place in the region, with an additional two agreements due to be
finalized in the near future.
The agreements vary in scope and depth, ranging from informal “handshake” agreements to
formal contracts. A wide variety of regional public and private sector ITS stakeholders are
participants in the agreements, and a wide variety of ITS activities are addressed.
Table 19 provides a listing of current/planned ITS stakeholder agreements in the Indianapolis
region. Included in the table are the agreement title, type, and description, as well as the
stakeholders involved and the status of each Indianapolis region ITS stakeholder agreement. A
description of each column heading in the table is as follows:
• Number: The agreement’s assigned number. The number has no significance other
than to provide a “placeholder” in the table.
• Title: The agreement’s title.
• Type: Indicates the type of agreement. Handshake = informal, verbal agreement.
MOU = memorandum of understanding (written document providing minimal detail
and demonstrating general consensus). Contract = annual written contract stating
specific duties and responsibilities of each party. Operational agreement = written
document (more specific than an MOU) identifying respective responsibilities for all
activities associated with system maintenance and operations.
• Description: A brief description of what activities the agreement is intended to
govern, and which stakeholders will be involved.
• Lead Stakeholder: Stakeholder responsible for initiating and/or the agreement.
• Associated Stakeholders: All stakeholders involved in the coordination/execution
of the agreement with the lead stakeholder. Stakeholder acronyms are as follows:
o IPTC/IndyGo = Indianapolis Public Transportation Corporation
o Indianapolis DPW = Indianapolis Department of Public Works
o INDOT = Indiana Department of Transportation
o ISP = Indiana State Police
o IMPD = Indianapolis Metropolitan Police Department
o IFD = Indianapolis Fire Department
o MPO = Indianapolis Metropolitan Planning Organization
o IDI = Indianapolis Downtown, Inc.
o IMS = Indianapolis Motor Speedway
o IPS = Indianapolis Public Schools
o IAA = Indianapolis Airport Authority
• Status: Existing = agreement is currently in place. Planned = agreement is planned
for the near future.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 54
FINAL REPORT, Version 3.0

Table 19 Indianapolis ITS Agreements Inventory
No. Title Type Description
001
002
003
004
005
006
007
008
Indianapolis
DPW
Incident
Response
Indianapolis
DPW /
INDOT
Route
Maintenance
Jurisdiction
Indianapolis
DPW /
INDOT
Route
Maintenance
Jurisdiction
Indianapolis
DPW South
and East
County Line
Route
Maintenance
Jurisdiction
Indianapolis
DPW / IDI
Traffic
Control
Indianapolis
DPW
Municipal
Traffic
Signal
Maintenance
"Knozone"
Action Day
Messages
INDOT
Indianapolis
Traffic
Mgmt.
Center
(TMC)
Handshake
Handshake
MOU
MOU
Contract
Operational
Agreement
MOU
MOU
The Indianapolis DPW is
available 24/7, and will provide
incident traffic control
(barricades, vehicles, etc. as
deemed necessary by the IFD and
IMPD. This agreement includes
HAZMAT response coordination.
Transfer of route maintenance
(including traffic signals) inside
I-465 on former INDOT routes
US 36, SR 67, US 52, and US
421 from INDOT to Indianapolis
DPW. This agreement includes
traffic signal maintenance.
Transfer of route maintenance
(including traffic signals)inside I-
465 on former INDOT routes US
31, SR 37, US 40 and SR 135
from INDOT to Indianapolis
DPW. This agreement includes
traffic signal maintenance.
Indianapolis DPW provides route
maintenance (including traffic
signals) on routes along the south
and east county line of Marion
County.
Indianapolis DPW provides
barricades, etc. for large events
(Black Expo, Circle City Classic,
etc.)
Indianapolis DPW provides
traffic signal maintenance an all
signals within the "Excluded
Cities" in Marion County (Beech
Grove, Lawrence, Speedway),
and on all signals at interstate
ramp intersections in Marion Co.
INDOT displays "Knozone"
Action Day messages on INDOT
dynamic message signs as
advised by the City of
Indianapolis.
Cost-sharing agreement for the
INDOT Indianapolis TMC,
including overall funding
(INDOT cost), construction
(INDOT cost), building security
(ISP cost), and facility
maintenance (ISP cost).
Lead
Stakeholder
Indianapolis
DPW
Indianapolis
DPW
Indianapolis
DPW
Indianapolis
DPW
Indianapolis
DPW
Indianapolis
DPW
INDOT
District
Level
INDOT
District
Level
Associated
Stakeholders
IFD, IMPD
INDOT
District Level
INDOT
District Level
Surrounding
Counties
Event
Promoters /
Special Events
INDOT
District Level,
City of Beech
Grove, City of
Lawrence,
Town of
Speedway
INDOT,
Indianapolis
DPW,
Indianapolis
MPO
INDOT, ISP
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 55
FINAL REPORT, Version 3.0
Status
Existing
Existing
Existing
Existing
Existing
Existing
Existing
Existing
009 INDOT / MOU Information for sharing INDOT INDOT, ISP Existing

No. Title Type Description
ISP
operations, including ISP input
Operations
for INDOT dynamic message
Agreement
signs and ISP access to INDOT
freeway surveillance cameras
010
011
013
014
015
016
017
018
019
020
021
022
INDOT /
ISP Work
Zone
Agreement
INDOT
Media
Agreements
IPTC/
IndyGo/
MECA
Radio Use
Indianapolis
DPW GIS
Sharing
Central
Indiana
Commuter
Services
(CICS)
Various
Special
Event
Agreements
Race Day
Incident
Mgmt.
IPS Mutual
Aid
Agreements
Eli Lilly and
Co.
Emergency
Mgmt.
Indianapolis
Airport
Mutual Aid
Agreements
Bomb Squad
Agreement
Indianapolis
Airport
MOU
MOU
MOU
MOU
MOU
MOU
MOU
MOU
Handshake
MOU
MOU
MOU
(ISP has no control of cameras).
ISP provides work zone speed
enforcement and INDOT
compensates ISP for overtime
hours worked.
Sharing of traffic information
collected by INDOT assets with
the media.
MECA provides use of its backup
communications system (system
2) to IPTC/IndyGo for their use.
Indianapolis DPW provides
IPTC/IndyGo with GIS data
IPTC/IndyGo coordinates with
INDOT to promote the use of
alternative commuting options
such as ridesharing (carpooling
or vanpooling) and public
transportation.
Event-specific agreements for
transit use during special events.
Various municipalities perform
incident management functions at
the IMS on race days.
Agreements between IPS and
municipal/county law
enforcement for mutual aid
during incident response.
Emergency mgmt. coordination
between Eli Lilly and Co. and
municipal/county emergency
management agencies.
Agreements between
Indianapolis Airport and
municipal/county law
enforcement for mutual aid
during incident response.
Agreement between Indianapolis
Airport and municipal law
enforcement for bomb squad
action.
Airport emergency response
coordination agreement between
Lead
Stakeholder
District
Level
INDOT
District
Level
INDOT
Associated
Stakeholders
INDOT, ISP
INDOT
District Level,
Media
Services
Status
Existing
Existing
MECA IPTC/IndyGo Planned
Indianapolis
DPW
IPTC/
IndyGo
IPTC/
IndyGo
IMS
IPS
Major
Employers
IAA
IPTC/IndyGo
INDOT,
INDOT
District Level
Event
Promoters /
Special Events
City of
Lawrence,
Surrounding
Municipalities
IPD, Marion
County
Sheriff's Dept.
IFD, IPD,
Marion
County
Sheriff's Dept.
Marion Co.
Sheriff's Dept.,
Suburban
Municipalities,
Surrounding
Counties
Existing
Existing
Existing
Existing
Existing
Existing
Existing
IAA IPD Existing
IAA
IMPD, ISP,
Marion
Planned
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 56
FINAL REPORT, Version 3.0

No. Title Type Description
Emergency
Indianapolis Airport and
Response
municipal/county public safety
023
024
City of
Indianapolis
/INDOT
Emergency
Vehicle
Preemption
INDOT 511
Traveler
Information
Blanket
Agreement
MOU
agencies.
The DPW has an agreement with
INDOT for emergency vehicle
preemption device installation
and maintenance on INDOT
signals. EVP is used extensively
by DPW, but INDOT only allows
it at certain locations adjacent to
DPW EVP systems.
Agreement between INDOT and
wireless phone carriers to provide
traffic information to wireless
customers
Lead
Stakeholder
Indianapolis
Department
of Public
Works
INDOT
Associated
Stakeholders
County
Sheriff's
Department
INDOT
Media
Services
Status
Existing
Existing
Table 19 is not meant to serve as a “final” list of agreements. As ITS technologies continue to
evolve, and as other ITS entities are introduced to the region (light rail, for example), new
agreements between stakeholders will need to be developed. Also, as new ITS technologies
replace older ones, and as stakeholders come and go, certain existing agreements may become
obsolete and may need to be either revised or voided. Potential future agreements could include:
• Highway Incident Management Plan – agreements between INDOT, ISP, HAZMAT
response teams, and other freeway incident management agencies to promote interagency
coordination and cooperation for freeway incidents.
• Emergency Communications – agreements to expand MECA system to INDOT and other
agencies not yet on the system.
• Indianapolis TMC – agreements between the City of Indianapolis and various incident,
emergency, and traffic management agencies, including IFD, IPD, ISP and INDOT. This
agreement could address operational coordination and CCTV video sharing.
• Light Rail Transit – agreements to promote the use and operational efficiency of a future
light rail system in Indianapolis.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 57
FINAL REPORT, Version 3.0

8.0 Standards
In order to support regional and national interoperability, a system of nationwide ITS standards
has been developed. These standards establish a common protocol for agencies that allows them
to cost-effectively design, deploy, and maintain ITS systems in a consistent fashion. With ITS
technologies continuing to evolve, many ITS standards are still in their infancy, while others are
in various stages of development.
The goal of ITS standards is to ensure that the consistency of ITS system implementation
resulting from adherence to ITS standards will allow for more efficient data exchange, and will
allow for equipment replacement, system upgrades, and system expansion to be more readily
accommodated. Also, ITS standards, as a protocol for consistency and uniformity, should
provide a more innovative and competitive regional and nationwide market for transportation
products and services.
ITS standards are mapped to the architecture flows between ITS architecture subsystems. For
instance, ITS standards are mapped to the file transfer protocol for the transmission of roadway
network conditions between a metropolitan traffic management center and a suburban traffic
management center. A variety of ITS standards are in use in the Indianapolis region based upon
the architecture flows connecting the various regional architecture elements as identified in the
Turbo Architecture® software file. A listing of the ITS standards mapped to the architecture
flows within the Indianapolis regional ITS architecture is provided in Table 20. Included in the
table are the Standards Development Organization(s), the standard name, and the document ID
for each standard or group of standards. A description of each column heading in the table is as
follows:
• Lead SDO: The main standards development organization(s) (SDO) responsible for
the development of the listed standard. SDO acronyms are as follows:
o AASHTO = American Association of State Highway and
Transportation Officials
o ITE = Institute of Transportation Engineers
o NEMA = National Electrical Manufacturer’s Association
o ASTM = American Society for Testing and Materials
o IEEE = Institute of Electrical and Electronics Engineers
o SAE = Society of Automotive Engineers
• Standard: The name of the standard or group of standards. For each standards
group, the individual standards contained within the group are listed directly below
the group identifier. Standard name acronyms not identified in the table are as
follows:
o NTCIP = National Transportation Communications for ITS
Protocol
o TCIP = Transit Communications Interface Profile
• Document ID: Indicates the identification of each standard’s supporting
documentation.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 58
FINAL REPORT, Version 3.0

Table 20 Indianapolis ITS Standards Inventory
Lead SDO Standard Name Document ID
AASHTO/ITE
Traffic Management Data Dictionary and Message Sets for External
TMC Communication (TMDD and MS/ETMCC)
ITE TMDD 2.1
NTCIP Center-to-Center Standards Group
• Octet Encoding Rules (OER) Base Protocol NTCIP 1102
• Center-to-Center Naming Convention Specification NTCIP 1104
• Ethernet Subnetwork Profile NTCIP 2104
AASHTO/ITE/NEMA • Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202
• File Transfer Protocol (FTP) Application Profile NTCIP 2303
• Application Profile for DATEX-ASN (AP-DATEX) NTCIP 2304
• Application Profile for XML Message Encoding and Transport
in ITS Center-to-Center Communications (C2C XML)
NTCIP 2306
NTCIP Center-to-Field Standards Group
• Octet Encoding Rules (OER) Base Protocol NTCIP 1102
• Transportation Management Protocols (STMP) NTCIP 1103
• Point to Multi-Point Protocol Using RS-232 Subnetwork
Profile
NTCIP 2101
• Point to Multi-Point Protocol Using FSK Modem Subnetwork
Profile
NTCIP 2102
AASHTO/ITE/NEMA • Point-to-Point Protocol Over RS-232 Subnetwork Profile NTCIP 2103
• Ethernet Subnetwork Profile NTCIP 2104
• Transportation Transport Profile NTCIP 2201
• Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202
• Simple Transportation Management Framework (STMF)
Application Profile
NTCIP 2301
• Trivial File Transfer Protocol (TFTP) Application Profile NTCIP 2302
• File Transfer Protocol (FTP) Application Profile NTCIP 2303
AASHTO/ITE/NEMA Global Object Definitions NTCIP 1201
AASHTO/ITE/NEMA
Object Definitions for Actuated Traffic Signal Controller (ASC)
Units
NTCIP 1202
AASHTO/ITE/NEMA Object Definitions for Dynamic Message Signs (DMS) NTCIP 1203
AASHTO/ITE/NEMA Object Definitions for Environmental Sensor Station (ESS) NTCIP 1204
AASHTO/ITE/NEMA
Object Definitions for Closed Circuit Television (CCTV) Camera
Control
NTCIP 1205
AASHTO/ITE/NEMA
Object Definitions for Data Collection and Monitoring (DCM)
Devices
NTCIP 1206
AASHTO/ITE/NEMA Object Definitions for Closed Circuit Television (CCTV) Switching NTCIP 1208
AASHTO/ITE/NEMA Data Element Definitions for Transportation Sensor Systems (TSS) NTCIP 1209
AASHTO/ITE/NEMA
Field Management Stations (FMS) - Part 1: Object Definitions for
Signal Systems Masters
NTCIP 1210
AASHTO/ITE/NEMA Object Definitions for Signal Control and Prioritization (SCP) NTCIP 1211
APTA Standard for Transit Communications Interface Profiles
APTA TCIP-S-
001 3.0.0
ASTM
Dedicated Short Range Communication at 915 MHz Standards
Group
• Standard Specification for Dedicated Short Range
Communication (DSRC) Physical Layer using Microwave in the ASTM E2158-01
902-928 MHz Band
• Standard Provisional Specification for Dedicated Short Range
Communication (DSRC) Data Link Layer
ASTM
PS 105-99
ASTM Standard Practice for Metadata to Support Archived Data ASTM E2468-05
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 59
FINAL REPORT, Version 3.0

Lead SDO Standard Name Document ID
Management Systems
ASTM
Standard Specification for Archiving ITS-Generated Traffic
Monitoring Data
ASTM WK7604
Dedicated Short Range Communication at 5.9 GHz Standards Group
• Standard Specification for Telecommunications and
ASTM E2213-03
Information Exchange Between Roadside and Vehicle Systems
- 5 GHz Band Dedicated Short Range Communications
(DSRC) Medium Access Control (MAC) and Physical Layer
(PHY) Specifications
• Standard for Wireless Access in Vehicular Environments
(WAVE) – Resource Manager
IEEE 1609.1-
2006
• Standard for Wireless Access in Vehicular Environments
IEEE 1609.2-
(WAVE) – Security Services for Applications and
ASTM/SAE/IEEE
2006
Management Messages
• Standard for Wireless Access in Vehicular Environments
(WAVE) – Multi-Channel Operation
IEEE 1609.4-
2006
• Standard for Wireless Access in Vehicular Environments IEEE P1609.3
(WAVE) – Networking Services
• Standard for Information Technology – Telecommunications IEEE P802.11p
and Information Exchange Between Systems – Local and
Metropolitan Area Networks – Specific Requirements – Part II:
Wireless LAN Medium Access Control (MAC) and Physical
Layer (PHY) Specifications
Incident Management Standards Group
• Standard for Common Incident Management Message Sets for
use by Emergency Management Centers
IEEE
1512-2006
• Standard for Traffic Incident Management Message Sets for Use
by Emergency Management Centers
IEEE
1512.1-2006
IEEE
• Standard for Public Safety Traffic Incident Management Sets
for Use by Emergency Management Centers
IEEE 1512.2-
2004
• Standard for Hazardous Material Incident Management Message
Sets for Use by Emergency Management Centers
IEEE
1512.3-2006
• Standard for Common Traffic Incident Management Message
Sets for Use in Entities External to Centers
IEEE P1512.4
IEEE Standard Message Sets for Vehicle/Roadside Communications IEEE 1455-1999
Advanced Traveler Information Systems (ATIS) Bandwidth Limited
Standards Group
• Location Referencing Message Specification (LRMS)
SAE J2266
• Message Set for Advanced Traveler Information System
(ATIS)
SAE J2354
SAE
• Standard for ATIS Message Sets Delivered Over Reduced
Bandwidth Media
SAE J2369
• Messages for Handling Strings and Look-Up Tables in ATIS
Standards
SAE J2540
• RDS (Radio Data System) Phrase Lists SAE J2540/1
• ITIS (International Traveler Information Systems) Phrase Lists SAE J2540/2
• National Names Phrase List SAE J2540/3
Advanced Traveler Information Systems (ATIS) General Use
Standards
SAE
• Location Referencing Message Specification (LRMS)
SAE J2266
• Message Set for Advanced Traveler Information System (ATIS) SAE J2354
• Messages for Handling Strings and Look-Up Tables in ATIS
Standards
SAE J2540
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 60
FINAL REPORT, Version 3.0

Lead SDO Standard Name Document ID
• RDS (Radio Data System) Phrase List SAE J2540/1
• ITIS (International Traveler Information Systems) Phrase Lists SAE J2540/2
• National Names Phrase List SAE J2540/3
SAE
Dedicated Short Range Communications (DSRC) Message Set
Dictionary
SAE J2735
As new ITS technologies continue to be implemented within the Indianapolis region, or as
obsolete technologies are phased out, ITS standards may need to be added or subtracted from the
ITS standards list as needed.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 61
FINAL REPORT, Version 3.0

9.0 Use of the Architecture
As shown in Figure 1, step five of the architecture process is use of the regional architecture. A
regional ITS architecture is developed so that it can be used as a tool for region-wide
transportation planning, ITS project development, and ITS project implementation. It is
important that the regional ITS architecture be used in conjunction with other regional planning
documents to ensure that proposed ITS projects are implemented in the most practical, costeffective,
and beneficial manner.
9.1 Planning
From a planning standpoint, the regional ITS architecture should be used as a reference when
updating regional transportation plans such as the Indianapolis Regional Transportation Plan, the
Statewide Long Range Transportation Plan, the Indianapolis Regional Transportation
Improvement Program (IRTIP), and the Statewide Transportation Improvement Program (STIP).
ITS projects as listed in the Indianapolis regional ITS architecture add to the pool of potential
regional projects to be programmed. The planning agencies responsible for updating the
transportation plans will now be able to make a more informed determination of transportation
project priority given the information the regional ITS architecture provides concerning ITS
projects and their potential effect on other roadway and transit projects.
Another planning document which plays a significant role in the planning process is the Indiana
Department of Transportation (INDOT) ITS Strategic Deployment Plan. This document provides
detailed information on planned ITS projects on the INDOT system, including INDOT routes
within the Indianapolis region. The regional ITS architecture, in conjunction with the INDOT
ITS Strategic Deployment Plan, will work together to provide comprehensive ITS data to be used
in determining transportation project priority in the region.
Since ITS technologies are continually evolving, expanding, and changing, regional ITS
architectures (including the Indianapolis Regional ITS Architecture) are generally developed to a
medium-term timeframe of approximately 10 years. Therefore, the regional ITS architecture will
be of some benefit in determining medium-term project priority within a long range plan, and will
be of substantial benefit in prioritizing projects within the short-term IRTIP and STIP plans.
9.2 Project Development and Implementation
From a project development and implementation standpoint, the regional ITS architecture can aid
individual stakeholders in defining the scope and details of an ITS project. Generally, the
stakeholder has an idea of the general parameters of a project, but the ITS architecture allows the
stakeholder to develop a detailed scope via identification of:
• the appropriate systems or parts of systems that will need to be employed,
• the various interconnections with other systems and/or stakeholders that may be required,
and
• what information needs to flow across the interconnections.
Determination of systems to be employed begins with identification of stakeholder roles and
responsibilities, which are defined in the regional ITS architecture operational concept. The
appropriate interconnections can be partially or completely defined using the regional ITS
architecture functional requirements applicable to the project. The requirements for the
information flows across the interconnections can be identified by mapping to the ITS standards
within the regional ITS architecture.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 62
FINAL REPORT, Version 3.0

The development of an ITS project as outlined above follows the left side of the standard systems
engineering approach as illustrated in Figure 7 below.
Figure 7 Standard Systems Engineering Diagram
The concept of operations, functional requirements, and standards as defined in the regional ITS
architecture allow for the stakeholder to develop the project to the detailed design level, then
onward into the implementation stage. The systems engineering approach, which includes the
identification of roles and responsibilities, functional requirements, and ITS standards, is also
important to follow since it is required by the FHWA/FTA Rule/Policy governing ITS projects
funded via the Highway Trust Fund.
Once a project has been defined and funding has been committed, the implementation portion can
proceed with the generation of a Request for Proposal (RFP), a common governmental practice
for initiating a contract with the private sector to implement the project. The regional ITS
architecture can support the RFP generation process by developing the project definition as
described above, which forms the basis for the items/equipment to be procured in the contract.
Also, mapping the project to the regional ITS architecture allows potential bidders to have a clear
understanding of the project scope and the interfaces that need to be developed. After the project
has been awarded, the process moves up the right side of the systems engineering diagram shown
above via installation of the appropriate systems and devices, testing and integration, acceptance
and verification, and then maintenance.
As detailed above, the regional ITS architecture represents a plan for the implementation of ITS
systems throughout the Indianapolis region. It is a valuable tool that can and should be used to
support and supplement regional transportation planning and ITS project development/
implementation efforts.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 63
FINAL REPORT, Version 3.0

10.0 Architecture Maintenance Plan
The sixth and final step in developing a regional architecture is the maintenance of the
architecture. The Indianapolis Regional ITS Architecture is a dynamic framework for the
planning, development, and deployment of ITS in the region. As such, the architecture will need
to be periodically updated as ITS projects are implemented and as the ITS needs and services
evolve within the region. The FHWA/FTA has emphasized the importance of this step in its
Final Rule/Final Policy, stating that “The agencies and other stakeholders participating in the
development of the regional ITS architecture shall develop and implement procedures and
responsibilities for maintaining it, as needs evolve within the region.”
In order to define these procedures, the following three questions are addressed in this
maintenance plan:
• Who will maintain the architecture?
• What will be maintained?
• How will it be maintained?
The following subsections demonstrate how the three primary questions of architecture
maintenance will be addressed in the Indianapolis region.
10.1 Who Will Maintain the Architecture?
The Indianapolis Metropolitan Planning Organization (MPO), with assistance from the Indiana
Department of Transportation (INDOT), will maintain the Indianapolis Regional ITS
Architecture. As the primary transportation planning and coordinating agency within the
geographic boundary of the Indianapolis Regional ITS Architecture (which matches the
metropolitan planning area), the MPO is well suited to serve this role. In addition, the periodic
updating of the Indianapolis Architecture will coincide with the Indianapolis MPO’s other
transportation planning activities, such as regular updates to the Regional Transportation
Improvement Program. INDOT’s familiarity with the Turbo Architecture® software tool and
broad role in regional transportation matters emphasize the importance of their involvement in
architecture maintenance.
In order to facilitate maintenance of the Indianapolis Regional ITS Architecture, the Indianapolis
MPO shall formulate an ITS Working Group. The ITS Working Group shall be responsible for
ensuring that the Indianapolis Regional ITS Architecture is maintained in accordance with the
FHWA/FTA Final Rule and Policy.
ITS Working Group voting members shall include, but not be limited to:
• Indiana Department of Transportation
• Indiana State Police
• Indianapolis Department of Public Works
• Indianapolis Fire Department
• Indianapolis MPO
• Indianapolis Metropolitan Police Department
• IndyGo
• Contracted architecture maintenance consultant (as requested at the discretion of the
Indianapolis MPO)
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 64
FINAL REPORT, Version 3.0

ITS Working Group ad hoc members shall include, but not be limited to:
• Indianapolis Regional Transportation Council (IRTC) Policy Committee Members
• IRTC Technical Committee Members
10.2 What Will Be Maintained?
The Indianapolis ITS Architecture consists of two components: this architecture document and
the Turbo Architecture® database. Architecture changes approved by the ITS Working Group
should be reflected in both components.
10.3 How Will It Be Maintained?
Maintenance of the architecture is a multi-step process. First, a potential architecture change
must be identified by a regional ITS stakeholder (or stakeholders). Next, the change request form
(see below) must be submitted by the stakeholder and reviewed by the ITS Working Group to
determine if an architecture change is in order. If the change is approved, it is to be documented
in the list of changes for the next architecture update and then implemented.
Change Request Identification
Change requests must originate within the ITS Working Group membership using the Change
Request Form found at the conclusion of this section. Entries on the form include:
• Change identification,
• Request date,
• Change description,
• Rationale for change,
• Request originator contact information, and
• Administrative fields.
All change request forms will be catalogued by the Indianapolis MPO in the Change Database
(described below).
Change Request Review
Each requested change will be reviewed by the ITS Working Group to ensure that the request
warrants a change in the architecture. The following are examples of circumstances that could
lead to an architecture change request:
1. Changes in regional needs
2. Change in description of the region
3. Stakeholders added, deleted, or revised
4. Change in service scope or change to the National ITS Architecture
5. Changes to adjacent or overlapping regional ITS architectures
6. Changes in status of systems or services
7. Changes in ITS standards
8. Interagency agreements added, deleted, or revised
9. Changes in project priority, including new or deleted ITS-related projects
10. Changes to existing regional transportation plans, including the Transportation Improvement
Program (TIP), the Long Range Transportation Plan, or the INDOT ITS Strategic
Deployment Plan
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 65
FINAL REPORT, Version 3.0

For change requests concerning ITS-related projects, the ITS Working Group will determine if a
proposed project is, in fact, an intelligent transportation systems project. Next, the Working
Group will determine if the Indianapolis ITS Architecture already includes the requested item. If
the project is not yet reflected in the architecture, the ITS Working Group will vote to determine
if it should be recommended for IRTC Policy and Technical Committee approval.
To maintain open communication channels, it is recommended that a messaging email list be
created and at least one member from each working group be subscribed. This will facilitate
open communication to track ITS system changes in real-time, rather than only in periodic
reviews. The MPO should send out occasional solicitations for any new information, and post
and resulting change requests on their website alongside the latest complete document.
Change Request Approval
In order for an architecture change to be approved by the ITS Working Group, a majority vote
(quorum of five members) is required. This vote could be made via an ITS Working Group
meeting, or email/telephone. At a minimum, the Working Group should convene on an annual
basis to review and/or approve requested architecture changes.
If a change request is rejected by the Working Group, within two weeks the request originator
will be informed of the decision (and the reason(s) for the decision) and will be invited to
resubmit a change request if deemed appropriate by the maintainer.
Once the ITS Working Group has voted to approve a change to the architecture, the Indianapolis
Regional ITS Architecture Change Database will be updated to reflect approval of the change.
Below is a sample Change Database Entry which highlights the information that would be taken
from the Change Request forms and entered into the Change Database. Subsequent sheets in the
Change Database will record individual changes to the architecture (e.g., new stakeholders, ITS
standards updates).
Change
Number
XX-YY*
Change
Description
Expanded
description of
the requested
change
Request
Originator
Name of
request
originator
Change
Decision
Accept,
reject, or
defer
* XX = year and YY = chronological value
Decision
Date
Date
decision
is made
Decision
Comment
Pertinent
details
associated
with change
decision
Architecture
Components
Affected
Listing of
affected
architecture
components
Change
Type
Minor or
major
Change Implementation
Formal implementation of changes to the Indianapolis Regional ITS Architecture will occur on a
triennial basis. In the event that an approved architecture change is needed sooner, the change
can be made before the next change cycle. The MPO (or its Architecture Maintenance
Contractor) will implement the approved changes from the Change Database. The maintainer
should ensure that updates are consistent with the most recent version of the National ITS
Architecture and Turbo Architecture®. To properly track updates to the Indianapolis Regional
ITS Architecture, the maintainer should update the proper sheet(s) of the Change Database, the
Document Revision History table at the front of this document, and the Change Log in Turbo
Architecture®.
Once the architecture update process is complete, the maintainer shall submit the updated
architecture document and Turbo Architecture® file to the ITS Working Group for approval. The
updated architecture will then be carried forward to the IRTC Policy and Technical Committees
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 66
FINAL REPORT, Version 3.0

for their approval. Approval will then be granted by these committees in accordance with current
MPO procedures.
Summary
Below is a bulleted chronological summary of the Indianapolis ITS Regional Architecture
maintenance process:
• Regional ITS Architecture change requested by stakeholder
• Regional ITS Architecture Change Form submitted to MPO by requesting stakeholder
• Change request catalogued in MPO Regional ITS Architecture Change Database
• ITS Working Group meets annually (minimum) to review Regional ITS Architecture
change requests
• Changes approved, denied, or deferred by ITS Working Group are indicated as such by
MPO in Regional ITS Architecture Change Database, and requesting stakeholders are
informed of the Group’s decision
• Regional ITS Architecture revised by Architecture Maintainer on a triennial basis (or on
an as-needed basis, where appropriate) to include all approved Regional ITS
Architecture changes since most recent architecture update
• Regional ITS Architecture revision documented by Architecture Maintainer in the proper
sheet(s) of the Change Database, the Architecture Revision History table, and Turbo
Software® change log.
• Revised Regional ITS Architecture Document and Turbo Software® file submitted to
ITS Working Group and IRTC Technical/Policy Committees for approval
Adherence to the above process will ensure that the Indianapolis Regional ITS Architecture is
maintained in accordance with the FHWA/FTA Final Rule and policy.
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 67
FINAL REPORT, Version 3.0

Indianapolis Regional ITS Architecture Change Request Form
Change Identification:
Request
Date:
Change Description
(describe affected
architecture elements):
Rationale for Change:
Request Originator
Contact Information:
Name:
Agency:
Address:
Telephone:
Fax:
Email:
To be filled out by Architecture Maintainer
Change Number*:
Change Decision: Accept Reject Defer
Decision Comments:
Decision Date:
Architecture
Components Affected:
Change Type: Minor
Major
* XX-YY, where XX = year and YY = chronological value, e.g., the first change request of 2006
would be ’06-01’
Indianapolis Regional Intelligent Transportation System (ITS) Architecture 68
FINAL REPORT, Version 3.0