Parent Service Package: PT14
< < PT13.1 : PT14.1 : PT15.1 > >

PT14.1: Multi-modal Coordination Implementation

This 'implementation' is a holistic view of the PT14 service package, including all Physical Objects, Functional Objects, and Triples associated with the service package. It distinguishes between items that are fundamental to the service and items that are optional. Your specific implementation is likely to include the fundamental items and selected optional items, based on your specific project requirements.

Relevant Regions:

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Alternate Mode Transportation Center MaintainerAlternate Mode Transportation Center Maintains
Alternate Mode Transportation Center ManagerAlternate Mode Transportation Center Manages
Alternate Mode Transportation Center ManagerAlternate Mode Transportation Center Operator System Usage Agreement
Alternate Mode Transportation Center OperatorAlternate Mode Transportation Center Operates
Alternate Mode Transportation Center OwnerAlternate Mode Transportation Center Maintainer System Maintenance Agreement
Alternate Mode Transportation Center OwnerAlternate Mode Transportation Center Manager Operations Agreement
Alternate Mode Transportation Center OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
Alternate Mode Transportation Center OwnerTraffic Management Center Owner Information Provision Agreement
Alternate Mode Transportation Center OwnerTraffic Management Center User Service Usage Agreement
Alternate Mode Transportation Center OwnerTraffic Operations Personnel Application Usage Agreement
Alternate Mode Transportation Center OwnerTransit Management Center Maintainer Maintenance Data Exchange Agreement
Alternate Mode Transportation Center OwnerTransit Management Center Owner Information Exchange Agreement
Alternate Mode Transportation Center OwnerTransit Management Center User Service Usage Agreement
Alternate Mode Transportation Center OwnerTransit Operations Personnel Application Usage Agreement
Alternate Mode Transportation Center SupplierAlternate Mode Transportation Center Owner Warranty
Event Promoter System MaintainerEvent Promoter System Maintains
Event Promoter System ManagerEvent Promoter System Manages
Event Promoter System ManagerEvent Promoter System Operator System Usage Agreement
Event Promoter System OperatorEvent Promoter System Operates
Event Promoter System OwnerEvent Promoter System Maintainer System Maintenance Agreement
Event Promoter System OwnerEvent Promoter System Manager Operations Agreement
Event Promoter System OwnerTransit Management Center Maintainer Maintenance Data Exchange Agreement
Event Promoter System OwnerTransit Management Center Owner Information Exchange Agreement
Event Promoter System OwnerTransit Management Center User Service Usage Agreement
Event Promoter System OwnerTransit Operations Personnel Application Usage Agreement
Event Promoter System SupplierEvent Promoter System Owner Warranty
Other Transit Management Centers MaintainerOther Transit Management Centers Maintains
Other Transit Management Centers ManagerOther Transit Management Centers Manages
Other Transit Management Centers ManagerOther Transit Management Centers Operator System Usage Agreement
Other Transit Management Centers OperatorOther Transit Management Centers Operates
Other Transit Management Centers OwnerOther Transit Management Centers Maintainer System Maintenance Agreement
Other Transit Management Centers OwnerOther Transit Management Centers Manager Operations Agreement
Other Transit Management Centers OwnerTransit Management Center Maintainer Maintenance Data Exchange Agreement
Other Transit Management Centers OwnerTransit Management Center Owner Information Exchange Agreement
Other Transit Management Centers OwnerTransit Management Center User Service Usage Agreement
Other Transit Management Centers OwnerTransit Operations Personnel Application Usage Agreement
Other Transit Management Centers SupplierOther Transit Management Centers Owner Warranty
Parking Management Center MaintainerParking Management Center Maintains
Parking Management Center ManagerParking Management Center Manages
Parking Management Center ManagerParking Manager System Usage Agreement
Parking Management Center OwnerParking Management Center Maintainer System Maintenance Agreement
Parking Management Center OwnerParking Management Center Manager Operations Agreement
Parking Management Center OwnerTransit Management Center Maintainer Maintenance Data Exchange Agreement
Parking Management Center OwnerTransit Management Center Owner Information Provision Agreement
Parking Management Center OwnerTransit Management Center User Service Usage Agreement
Parking Management Center OwnerTransit Operations Personnel Application Usage Agreement
Parking Management Center SupplierParking Management Center Owner Warranty
Parking ManagerParking Management Center Operates
Traffic Management Center MaintainerTraffic Management Center Maintains
Traffic Management Center ManagerTraffic Management Center Manages
Traffic Management Center ManagerTraffic Operations Personnel System Usage Agreement
Traffic Management Center OwnerTraffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center OwnerTraffic Management Center Manager Operations Agreement
Traffic Management Center SupplierTraffic Management Center Owner Warranty
Traffic Operations PersonnelTraffic Management Center Operates
Transit Management Center MaintainerTransit Management Center Maintains
Transit Management Center ManagerTransit Management Center Manages
Transit Management Center ManagerTransit Operations Personnel System Usage Agreement
Transit Management Center OwnerAlternate Mode Transportation Center Maintainer Maintenance Data Exchange Agreement
Transit Management Center OwnerAlternate Mode Transportation Center Operator Application Usage Agreement
Transit Management Center OwnerAlternate Mode Transportation Center Owner Information Exchange Agreement
Transit Management Center OwnerAlternate Mode Transportation Center User Service Usage Agreement
Transit Management Center OwnerEvent Promoter System Maintainer Maintenance Data Exchange Agreement
Transit Management Center OwnerEvent Promoter System Operator Application Usage Agreement
Transit Management Center OwnerEvent Promoter System Owner Information Exchange Agreement
Transit Management Center OwnerEvent Promoter System User Service Usage Agreement
Transit Management Center OwnerOther Transit Management Centers Maintainer Maintenance Data Exchange Agreement
Transit Management Center OwnerOther Transit Management Centers Operator Application Usage Agreement
Transit Management Center OwnerOther Transit Management Centers Owner Information Exchange Agreement
Transit Management Center OwnerOther Transit Management Centers User Service Usage Agreement
Transit Management Center OwnerTraffic Management Center Maintainer Maintenance Data Exchange Agreement
Transit Management Center OwnerTraffic Management Center Owner Information Provision Agreement
Transit Management Center OwnerTraffic Management Center User Service Usage Agreement
Transit Management Center OwnerTraffic Operations Personnel Application Usage Agreement
Transit Management Center OwnerTransit Management Center Maintainer System Maintenance Agreement
Transit Management Center OwnerTransit Management Center Manager Operations Agreement
Transit Management Center OwnerTransit Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Transit Management Center OwnerTransit Vehicle OBE Owner Information Exchange Agreement
Transit Management Center OwnerTransit Vehicle OBE User Service Usage Agreement
Transit Management Center OwnerTransit Vehicle Operator Application Usage Agreement
Transit Management Center SupplierTransit Management Center Owner Warranty
Transit Operations PersonnelTransit Management Center Operates
Transit Vehicle OBE MaintainerTransit Vehicle OBE Maintains
Transit Vehicle OBE ManagerTransit Vehicle OBE Manages
Transit Vehicle OBE ManagerTransit Vehicle Operator System Usage Agreement
Transit Vehicle OBE OwnerTransit Management Center Maintainer Maintenance Data Exchange Agreement
Transit Vehicle OBE OwnerTransit Management Center Owner Information Exchange Agreement
Transit Vehicle OBE OwnerTransit Management Center User Service Usage Agreement
Transit Vehicle OBE OwnerTransit Operations Personnel Application Usage Agreement
Transit Vehicle OBE OwnerTransit Vehicle OBE Maintainer System Maintenance Agreement
Transit Vehicle OBE OwnerTransit Vehicle OBE Manager Operations Agreement
Transit Vehicle OBE SupplierTransit Vehicle OBE Owner Warranty
Transit Vehicle OperatorTransit Vehicle OBE Operates

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Alternate Mode Transportation Center Center The 'Alternate Mode Transportation Center' provides the interface through which non-ITS transportation systems (e.g., airlines, ferry services, passenger-carrying heavy rail) can exchange data with ITS. This two-way interface enables coordination for efficient movement of people across multiple transportation modes. It also enables the traveler to efficiently plan itineraries which include segments using other modes.
Event Promoter System Center 'Event Promoter System' represents Special Event Sponsors that have knowledge of events that may impact travel on roadways or other modal means. Examples of special event sponsors include sporting events, conventions, motorcades/parades, and public/political events. These promoters interface to the ITS to provide event information such as date, time, estimated duration, location, and any other information pertinent to traffic movement in the surrounding area.
Other Transit Management Centers Center Representing another transit operations center, 'Other Transit Management Centers' is intended to provide a source and destination for information flows between peer transit management centers. It enables transit management activities to be coordinated across geographic boundaries or jurisdictions.
Parking Management Center Center The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Transit Management Center Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transit Operations Personnel Center 'Transit Operations Personnel' represents the people that are responsible for fleet management, maintenance operations, and scheduling activities of the transit system. These different roles represent a variety of individuals in the transit industry. Within the transit industry the person responsible for fleet management is known by many names: Street Supervisor, Starter, Dispatcher, Supervisor, Traffic Controller, Transportation Coordinator. This person actively monitors, controls, and modifies the transit fleet routes and schedules on a day to day basis (dynamic scheduling). The modifications will take account of abnormal situations such as vehicle breakdown, vehicle delay, detours around work zones or incidents (detour management, connection protection, and service restoration), and other causes of route or schedule deviations. Transit operations personnel are also responsible for demand responsive transit operation and for managing emergency situations within the transit network such as silent alarms on board transit vehicles, or the remote disabling of the vehicle. In addition the Transit Operations Personnel may be responsible for assigning vehicle operators to routes, checking vehicle operators in and out, and managing transit stop issues. This object also represents the personnel in the transit garage that are responsible for maintenance of the transit fleets, including monitoring vehicle status, matching vehicles with operators, and maintenance checking of transit vehicles. Finally, it represents the people responsible for planning, development, and management of transit routes and schedules.
Transit Vehicle OBE Vehicle The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.

Includes Functional Objects:

Functional Object Description Physical Object
TMC Multi-Modal Coordination 'TMC Multi-Modal Coordination' supports center-to-center coordination between the Traffic Management and Transit Management Centers. It monitors transit operations and provides traffic signal priority for transit vehicles on request from the Transit Management Center. Traffic Management Center
Transit Center Multi-Modal Coordination 'Transit Center Multi-Modal Coordination' supports transit service coordination between transit properties and coordinates with other surface and air transportation modes. As part of service coordination, it shares schedule and trip information, as well as transit transfer cluster (a collection of stop points, stations, or terminals where transfers can be made conveniently) and transfer point information between Multimodal Transportation Service Providers, Transit Agencies, and ISPs. An interface to Traffic Management also supports demand management strategies. Transit Management Center
Transit Vehicle Schedule Management 'Transit Vehicle Schedule Management' monitors schedule performance and identifies corrective actions when a deviation is detected. It provides two-way communication between the transit vehicle and center, enabling the center to communicate with the vehicle operator and monitor on-board systems. Transit Vehicle OBE

Includes Information Flows:

Information Flow Description
alternate mode information Schedule information for alternate mode transportation providers such as air, ferry, and passenger-carrying heavy rail. This also includes details of incidents and other service disruptions that have occurred in the alternative mode. This also includes measures of service demand that supports assessment of their impact on the road network.
alternate mode service coordination Coordination of service changes to support service coordination between a transit service and an alternate mode (e.g., rail, ferry, air).
alternate mode service data Detailed real-time schedule and other service information from alternate modes that supports coordination between modes to facilitate efficient transfer at connection points.
event plans Plans for major events possibly impacting traffic.
event transit service plans Transit service plans to support the special event. This may include additional runs, tighter headways, stop changes, and other changes to standard operations to accommodate the special event.
parking information General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots.
service information request Request to multimodal (possibly non-roadway) transit provider for general services information and specific trip information or reservation.
service information response Multimodal (possibly non-roadway) transit provider services information and trip reservation confirmations.
transit alternate mode information Transit schedule information provided for coordination at transit interchange points with alternate modes.
transit operations personnel input User input from transit operations personnel including instructions governing service availability, schedules, emergency response plans, transit personnel assignments, transit maintenance requirements, and other inputs that establish general system operating requirements and procedures.
transit operations status Presentation of information to transit operations personnel including accumulated schedule and fare information, ridership and on-time performance information, emergency response plans, transit personnel information, maintenance records, and other information intended to support overall planning and management of a transit property.
transit schedule information Current and projected transit schedule information used to initialize the transit vehicle with a vehicle assignment, monitor schedule performance, and develop corrective actions on-board.
transit service coordination Schedule coordination or AVL information shared between local/regional transit organizations. This includes coordination of connections and control parameters between transit properties as well as coordination of transit-related maintenance activities.
transit system data Current transit system operations information indicating current transit routes and fares, the level of service on each route, and the progress of individual vehicles along their routes for use in forecasting demand and estimating current transportation network performance.
transit vehicle schedule performance Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective Performance Measure


 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement

Related Sources

Document Name Version Publication Date
None


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Alternate Mode Transportation Center  
Event Promoter System  
Other Transit Management Centers  
Parking Management Center  
Traffic Management Center  
Transit Management Center  
Transit Vehicle OBE  



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Alternate Mode Transportation Center Traffic Management Center alternate mode information Low Moderate Low
Should not contain any personal or confidential information. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is little impact if this flow is not available.
Alternate Mode Transportation Center Transit Management Center alternate mode service coordination Low Moderate Moderate
Should not contain any personal or confidential information. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is little impact if this flow is not available.
Alternate Mode Transportation Center Transit Management Center alternate mode service data Moderate Moderate Low
Information related to liaison between entities could have personal and contact information, so should not generally be readable. If no contact information is included Confidentiality would be LOW. Coordination-related information needs to be correct, or route calculation and coordinations will suffer. The impact will not be catastrophic but could be significant. This information is unlikely to change very quickly. Loss of this flow will have minimal impact, as organizations fall back to default operating procedures, assuming some initial coordination has taken place.
Alternate Mode Transportation Center Transit Management Center service information response Moderate Moderate Moderate
The individual service response may include PII, so its reveal may compromise the individual using the transportation service. Data integrity needs to be preserved so that incorrect decisions are not made with regard to procuring transit services. Given that this flow is in response to real-time needs, a prompt response is justified. Lack of response may lead to the a transit user making alternate arrangements, which leads to an overall
Event Promoter System Transit Management Center event plans Moderate High Moderate
This will include PII of the event contact person, which should be protected from casual viewing. This flow will also include details of the planned event, which in some circumstances might not be entire public information and so again, should not be casually viewable. Personal contact information needs to be correct, but so do the details of the planned event because of the potential severity of the event's impact. Generally the more significant the potential impact of the event, the higher this should be, but never below MODERATE. There should be other mechanisms for getting this information, otherwise it would match integrity.
Other Transit Management Centers Transit Management Center transit service coordination Moderate Moderate Moderate
Coordination between transit systems is generally not sensitive, however this flow may include information related to serving individual connection protection requests that are sensitive. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved.
Parking Management Center Transit Management Center parking information Moderate Moderate Moderate
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise.
Transit Management Center Alternate Mode Transportation Center alternate mode service coordination Low Moderate Low
Should not contain any personal or confidential information. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is little impact if this flow is not available.
Transit Management Center Alternate Mode Transportation Center service information request Moderate Moderate Moderate
Individual service response implies activity by an individual, which could be PII. Coordination information between transit agencies needs to be correct, or trip errors (improper dispatch, lack of service) may occur. Some dynamism in this flow, depending on the level of interactivity and coordination, this might be Low.
Transit Management Center Alternate Mode Transportation Center transit alternate mode information Low Moderate Moderate
Coordination information between transit agencies, if compromised, has no obvious impact. Coordination information between transit agencies needs to be correct, or trip errors (improper dispatch, lack of service) may occur. Some dynamism in this flow, depending on the level of interactivity and coordination, this might be Low.
Transit Management Center Event Promoter System event transit service plans Moderate Moderate Moderate
Information includes changes to standing bus routes and related transit routing modifications, that a criminal or other hostile 3rd party might use against the transit vehicle/riders. Information must be accurate so the event promotor plans can proceed as desired. Might be LOW if transit plans are trivial or not counted on. Flow will probably not be used often, but when it is in place will have to be operable to support special events.
Transit Management Center Other Transit Management Centers transit service coordination Moderate Moderate Moderate
Coordination between transit systems is generally not sensitive, however this flow may include information related to serving individual connection protection requests that are sensitive. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved.
Transit Management Center Traffic Management Center transit system data Low Moderate Low
Coordination information between transit and traffic agencies, if compromised, has no obvious impact. Coordination information between transit and traffic agencies needs to be correct, or trip errors (improper dispatch, lack of service) may occur. Some dynamism in this flow, depending on the level of interactivity and coordination, this might be Low.
Transit Management Center Transit Operations Personnel transit operations status Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Transit Management Center Transit Vehicle OBE transit schedule information Low Moderate Moderate
This information is not sensitive. It is generally made public, to support transit system functionality. This data contains the vehicle assignment. It should be accurate, and not easily modified. However, the bus drivers will have some knowledge about what a reasonable configuration is, and should be able to notice any unusual configurations, such as all busses being a #27. This information is necessary for the TSP to work correctly. A few missed messages will not have a large impact. The Transit Management Center needs to know if the TV OBE does not receive the message, so it can resend it.
Transit Operations Personnel Transit Management Center transit operations personnel input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Transit Vehicle OBE Transit Management Center transit vehicle schedule performance Low Moderate Low
This information is directly observable, and in most instances it is made publically available. This information may be used to influence the decision about whether or not to make a traffic control priority request on behalf of the transit vehicle. If it is incorrect it may cause the transit management center to send out incorrect traffic control priority requests, which may delay traffic. There should not be any catastrophic failures caused if this data is occasionally missing.

Standards

Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.





System Requirements

No System Requirements