< < PT06 : PT07 : PT08 > >

PT07: Transit Passenger Counting

This service package counts the number of passengers entering and exiting a transit vehicle using sensors mounted on the vehicle and communicates the collected passenger data back to the management center. The collected data can be used to calculate reliable ridership figures and measure passenger load information at particular stops/stations.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Transit Management Center Developer	Transit Management Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Transit Vehicle OBE Developer	Transit Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Transit Vehicle OBE Developer	Transit Vehicle OBE	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Traveler Support Equipment Developer	Transit Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Traveler Support Equipment Developer	Traveler Support Equipment	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Transit Management Center Installer	Transit Management Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Transit Management Center Owner	Transit Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transit Management Center Owner	Transit Management Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Transit Vehicle OBE Installer	Transit Vehicle OBE	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Transit Vehicle OBE Owner	Transit Vehicle OBE Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transit Vehicle OBE Owner	Transit Vehicle OBE Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Traveler Support Equipment Installer	Traveler Support Equipment	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Traveler Support Equipment Owner	Traveler Support Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Traveler Support Equipment Owner	Traveler Support Equipment Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Transit Management Center Maintainer	Transit Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Transit Management Center Manager	Transit Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Transit Management Center Manager	Transit Operations Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Transit Management Center Owner	Transit Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Transit Management Center Owner	Transit Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Transit Management Center Supplier	Transit Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Transit Operations Personnel	Transit Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Transit Vehicle OBE Maintainer	Transit Vehicle OBE	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Transit Vehicle OBE Manager	Transit Vehicle OBE	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Transit Vehicle OBE Owner	Transit Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Transit Vehicle OBE Owner	Transit Management Center Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Transit Vehicle OBE Owner	Transit Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Transit Vehicle OBE Owner	Transit Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Transit Vehicle OBE Owner	Transit Operations Personnel	Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Transit Vehicle OBE Owner	Transit Vehicle OBE Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Transit Vehicle OBE Owner	Transit Vehicle OBE Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Transit Vehicle OBE Supplier	Transit Vehicle OBE Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Traveler Support Equipment Maintainer	Traveler Support Equipment	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the 'maintains' role typically is delegated authority by the entity with the "Owns" or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Traveler Support Equipment Manager	Traveler Support Equipment	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Traveler Support Equipment Owner	Transit Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Traveler Support Equipment Owner	Transit Management Center Owner	Information Exchange and Action Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Traveler Support Equipment Owner	Transit Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Traveler Support Equipment Owner	Transit Operations Personnel	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Traveler Support Equipment Owner	Traveler Support Equipment Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Traveler Support Equipment Owner	Traveler Support Equipment Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Traveler Support Equipment Supplier	Traveler Support Equipment Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Transit Management Center	Transit Center Passenger Counting	4.1.4	Collect and Process Transit Vehicle Data
		4.1.5.2	Manage Transit Vehicle Deviations
		4.2.1.5	Manage Transit Operational Data Store
Transit Vehicle OBE	Transit Vehicle Passenger Counting	4.1.1	Process On-Board Systems Data
Transit Vehicle OBE	Transit Vehicle Passenger Counting	4.1.2	Determine Transit Vehicle Service Status
Traveler Support Equipment	Transit Stop Information Services	4.7.1	Provide Traveler Roadside & Vehicle Data Interface
		4.7.2.1	Detect Traveler at Roadside
		4.7.2.5	Provide Traveler Roadside Fare Interface
		4.7.2.7	Provide Transit Roadside Passenger Data
		6.3.2	Inform Traveler

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
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.
Traveler Support Equipment	Field	'Traveler Support Equipment' provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes (e.g., rest stops, merchant locations), and major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops this might be simple displays providing schedule information and imminent arrival signals. This may be extended to include multi-modal information including traffic conditions and transit schedules to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveler. It also supports service enrollment and electronic payment of transit fares. In addition to the traveler information provision, it also enhances security in public areas by supporting traveler activated silent alarms.

Includes Functional Objects:

Functional Object	Description	Physical Object
Transit Center Passenger Counting	'Transit Center Passenger Counting' receives and processes transit vehicle loading data using two-way communications from equipped transit vehicles.	Transit Management Center
Transit Stop Information Services	'Transit Stop Information Services' furnishes transit users with real-time travel-related information at transit stops, multi-modal transfer points, and other public transportation areas. It provides transit users with information on transit routes, schedules, transfer options, available services, fares, and real-time schedule adherence. In addition to tailored information for individual transit users, it supports general annunciation and/or display of imminent arrival information and other information of general interest to transit users.	Traveler Support Equipment
Transit Vehicle Passenger Counting	'Transit Vehicle Passenger Counting' collects transit vehicle loading data and makes it available to the center.	Transit Vehicle OBE

Includes Information Flows:

Information Flow	Description
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 stop passenger status	The number of passengers waiting at a PT stop with optional route and destination information for waiting passengers to allow current demand at each stop to be monitored and factored into current transit service operations and transit performance monitoring. The stop identity is included.
transit vehicle loading data	Data collected on board the transit vehicle relating to passenger boarding and alighting.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal
D. Increase the accessibility and mobility of people and for freight;	Reduce congestion
G. Promote efficient system management and operation;	Improve efficiency

Associated Objective Categories

Objective Category
Transit Operations and Management: Loading Standards

Associated Objectives and Performance Measures

Objective	Performance Measure
Load factors for (route type) routes at each route's busiest point should not exceed X on any vehicle (or on the average vehicle) during peak/off-peak periods.	Load factor.
No more than X standees should be present at each route's busiest point on any vehicle (or on the average vehicle) during peak/off-peak periods.	Maximum standees.
No passenger will have to stand for more than X minutes during their journey.	Duration of standee time.
Passenger loads on (route type) routes at each route's busiest point should not exceed X passengers on any vehicle (or on average) during the hour during peak/off-peak periods	Maximum passenger loads.

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
01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.	Transit Center Passenger Counting	01	The center shall collect passenger count information from each transit vehicle.
			02	The center shall calculate transit ridership data by route, route segment, transit stop, time of day, and day of week based on the collected passenger count information.
			03	The center shall make the compiled ridership data available to the system operator.
		Transit Stop Information Services	07	The public interface for travelers shall provide the number of passengers entering and exiting a transit vehicle.
		Transit Vehicle Passenger Counting	01	The transit vehicle shall count passengers boarding and alighting.
			02	The passenger counts shall be related to location to support association of passenger counts with routes, route segments, or transit stations/stops.
			03	The passenger counts shall be timestamped so that ridership can be measured by time of day and day of week.
			04	The transit vehicle shall send the collected passenger count information to the transit center.

Related Sources

Document Name	Version	Publication Date
ITS User Services Document		1/1/2005

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
Transit Management Center	Moderate	Moderate	Moderate	Class 2
Transit Vehicle OBE	Moderate	Moderate	Moderate	Class 2
Traveler Support Equipment	Low	Moderate	Moderate	Class 1

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
Source	Destination	Information Flow	Basis	Basis	Basis
Transit Management Center	Transit Operations Personnel	transit operations status	Moderate	High	High
Transit Management Center	Transit Operations Personnel	transit operations status	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 Operations Personnel	Transit Management Center	transit operations personnel input	Moderate	High	High
Transit Operations Personnel	Transit Management Center	transit operations personnel input	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 loading data	Moderate	Moderate	Moderate
Transit Vehicle OBE	Transit Management Center	transit vehicle loading data	While internal, contains identification, passenger load and routing data that if observed could be used by an attacker to identify targets.	Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application.	Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. Loading data is dynamic, so probably needs to be updated frequently.
Traveler Support Equipment	Transit Management Center	transit stop passenger status	Low	Moderate	Moderate
Traveler Support Equipment	Transit Management Center	transit stop passenger status	Directly observable information.	Could be used to make asset allocation decisions, and so could affect the overall network. Manipulation, incorrect data or unavailability would all have negative effects. Severity will depend on the size of the network; larger networks should consider this MODERATE for both integrity and availability, while smaller networks may consider this LOW.	Could be used to make asset allocation decisions, and so could affect the overall network. Manipulation, incorrect data or unavailability would all have negative effects. Severity will depend on the size of the network; larger networks should consider this MODERATE for both integrity and availability, while smaller networks may consider this LOW.

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.

System Requirements

System Requirement		Need
001	The system shall collect passenger count information from each transit vehicle.	01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.
002	The system shall calculate transit ridership data by route, route segment, transit stop, time of day, and day of week based on the collected passenger count information.	01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.
003	The system shall make the compiled ridership data available to the system operator.	01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.
004	The system shall provide the number of passengers entering and exiting a transit vehicle.	01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.
005	The system shall count passengers boarding and alighting.	01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.
006	The system shall be related to location to support association of passenger counts with routes, route segments, or transit stations/stops.	01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.
007	The system shall be timestamped so that ridership can be measured by time of day and day of week.	01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.
008	The system shall send the collected passenger count information to the transit center.	01	Transit Operations needs to be able to count the passengers entering or exiting a transit vehicle in order to support efficient operations.