< < PT14 : PT15 : PT16 > >

PT15: Transit Stop Request

This service package allows a transit passenger to send a stop request to an approaching transit vehicle. The transit vehicle receives the request and notifies the vehicle operator of the stop request.

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
Basic Transit Vehicle Developer	Basic Transit Vehicle	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.
Basic Transit Vehicle Developer	Transit Vehicle OBE 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.
Connected Vehicle Roadside Equipment Developer	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Developer	Transit Vehicle OBE 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.
Connected Vehicle Roadside Equipment Developer	Traveler Support Equipment 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.
Personal Information Device Developer	Personal Information Device	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.
Personal Information Device 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.
Personal Information Device Developer	Transit Vehicle OBE 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 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 Management Center Developer	Transit Vehicle OBE 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	Connected Vehicle Roadside Equipment 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	Personal Information Device 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	Connected Vehicle Roadside Equipment 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	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
Basic Transit Vehicle Installer	Basic Transit Vehicle	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.
Basic Transit Vehicle Owner	Basic Transit Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Basic Transit Vehicle Owner	Basic Transit Vehicle 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.
Connected Vehicle Roadside Equipment Installer	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside 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.
Personal Information Device Installer	Personal Information Device	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.
Personal Information Device Owner	Personal Information Device Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Personal Information Device Owner	Personal Information Device 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 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
Basic Transit Vehicle Maintainer	Basic Transit Vehicle	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.
Basic Transit Vehicle Manager	Basic Transit Vehicle	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.
Basic Transit Vehicle Manager	Transit Vehicle Operator	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.
Basic Transit Vehicle Owner	Basic Transit Vehicle 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.
Basic Transit Vehicle Owner	Basic Transit Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Basic Transit Vehicle Owner	Transit Vehicle OBE 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.
Basic Transit Vehicle Owner	Transit Vehicle OBE 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.
Basic Transit Vehicle Owner	Transit Vehicle OBE User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Basic Transit Vehicle Owner	Transit Vehicle Operator	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.
Basic Transit Vehicle Owner	Transit Vehicle Operator	Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Basic Transit Vehicle Supplier	Basic Transit Vehicle Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Connected Vehicle Roadside Equipment Maintainer	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Manager	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside 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.
Connected Vehicle Roadside Equipment Owner	Transit Vehicle OBE 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.
Connected Vehicle Roadside Equipment Owner	Transit Vehicle OBE 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.
Connected Vehicle Roadside Equipment Owner	Transit Vehicle OBE User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Connected Vehicle Roadside Equipment Owner	Transit Vehicle Operator	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.
Connected Vehicle Roadside Equipment Owner	Traveler	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.
Connected Vehicle Roadside Equipment Owner	Traveler Support Equipment 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.
Connected Vehicle Roadside Equipment Owner	Traveler Support Equipment 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.
Connected Vehicle Roadside Equipment Owner	Traveler Support Equipment User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Connected Vehicle Roadside Equipment Supplier	Connected Vehicle Roadside 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.
Personal Information Device Maintainer	Personal Information Device	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.
Personal Information Device Manager	Personal Information Device	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.
Personal Information Device Manager	Traveler	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.
Personal Information Device Owner	Personal Information Device 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.
Personal Information Device Owner	Personal Information Device Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Personal Information Device 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.
Personal Information Device Owner	Transit Management Center Owner	Information Provision and Action Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personal Information Device 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.
Personal Information Device Owner	Transit Vehicle OBE 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.
Personal Information Device Owner	Transit Vehicle OBE Owner	Information Provision and Action Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Personal Information Device Owner	Transit Vehicle OBE User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Personal Information Device Owner	Transit Vehicle Operator	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.
Personal Information Device Supplier	Personal Information Device 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 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 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 Owner	Transit Vehicle OBE 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 Management Center Owner	Transit Vehicle OBE Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Transit Management Center Owner	Transit Vehicle OBE 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 Management Center Owner	Transit Vehicle Operator	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 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 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 Manager	Transit Vehicle Operator	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 Vehicle OBE Owner	Connected Vehicle Roadside Equipment 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	Connected Vehicle Roadside Equipment 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	Connected Vehicle Roadside Equipment 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	Personal Information Device 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	Personal Information Device 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	Personal Information Device 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 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 Owner	Traveler	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	Traveler	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 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.
Transit Vehicle Operator	Basic Transit Vehicle	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 Operator	Transit Vehicle OBE	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.
Traveler	Personal Information Device	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.
Traveler	Traveler Support Equipment	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.
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	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.
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	Connected Vehicle Roadside Equipment 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	Connected Vehicle Roadside Equipment 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	Connected Vehicle Roadside Equipment 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 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	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
Connected Vehicle Roadside Equipment	RSE Transit User Guidance	1.1.1.6	Collect Vehicle Roadside Safety Data
Connected Vehicle Roadside Equipment	RSE Transit User Guidance	4.7.3	Provide Transit Traveler Roadside Interface
Personal Information Device	Personal Trip Planning and Route Guidance	6.8.1.1.1	Determine Personal Portable Device Guidance Method
		6.8.1.1.2	Provide Personal Portable Device Dynamic Guidance
		6.8.1.2	Provide Personal Portable Device Guidance Interface
		6.8.1.4	Update Traveler Navigable Map Database
		6.8.3.1	Get Traveler Personal Request
		6.8.3.2	Provide Traveler with Personal Travel Information
		6.8.3.3	Provide Traveler Personal Interface
		6.8.3.5	Provide Traveler Transit Services Interface
		7.5.3	Provide Personal Payment Device Interface
Transit Management Center	Transit Center Information Services	4.2.1.3	Produce Transit Service Data for External Use
		4.2.1.6	Produce Transit Service Data for Manage Transit Use
		4.2.1.7	Provide Interface for Other Transit Management Data
Transit Vehicle OBE	Transit Vehicle On-Board Information Services	4.1.1	Process On-Board Systems Data
		4.1.2	Determine Transit Vehicle Service Status
		4.1.7	Provide Transit Advisory Interface on Vehicle
		4.6.2	Determine Traveler Needs on Vehicle
	Transit Vehicle On-Board Trip Monitoring	4.1.1	Process On-Board Systems Data
		4.1.2	Determine Transit Vehicle Service Status
		4.1.3	Provide Transit Vehicle Location Data
		4.6.2	Determine Traveler Needs on Vehicle
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	Provide Public Traveler Interface

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
Basic Transit Vehicle	Vehicle	The 'Basic Transit Vehicle' represents the transit vehicle that hosts the on-board equipment that provides ITS functions. It includes a specialized and extended databus that is subject to different vehicle databus standards and hosts a broad range of components that are unique to a transit vehicle including the farebox and associated electronics, passenger counters, and transit security systems. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers.
Connected Vehicle Roadside Equipment	Field	'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Personal Information Device	Personal	The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
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 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.
Transit Vehicle Operator	Vehicle	The 'Transit Vehicle Operator' represents the person that receives and provides additional information that is specific to operating the ITS functions in all types of transit vehicles. The information received by the operator would include status of on-board systems. Additional information received depends upon the type of transit vehicle. In the case of fixed route transit vehicles, the Transit Vehicle Operator would receive operator instructions that might include actions to take to correct schedule deviations. In the case of flexible fixed routes and demand response routes the information would also include dynamic routing or passenger pickup information.
Traveler	Personal	The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers.
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
Personal Trip Planning and Route Guidance	'Personal Trip Planning and Route Guidance' provides a personalized trip plan to the traveler. The trip plan is calculated based on preferences and constraints supplied by the traveler and provided to the traveler for confirmation. Coordination may continue during the trip so that the route plan can be modified to account for new information. Many equipment configurations are possible including systems that provide a basic trip plan to the traveler as well as more sophisticated systems that can provide transition by transition guidance to the traveler along a multi-modal route with transfers. Devices represented by this functional object include desktop computers at home, work, or at major trip generation sites, plus personal devices such as tablets and smart phones.	Personal Information Device
RSE Transit User Guidance	'RSE Transit User Guidance' uses short range communications to provide terminal or stop-specific guidance to transit user devices that assists users in finding the right stop and the right bus. Optionally, this object can collect the transit user location and planned itinerary so that tailored guidance can be provided.	Connected Vehicle Roadside Equipment
Transit Center Information Services	'Transit Center Information Services' collects the latest available information for a transit service and makes it available to transit customers and to Transportation Information Centers for further distribution. Customers are provided information at transit stops and other public transportation areas before they embark and on-board the transit vehicle once they are en route. Information provided can include the latest available information on transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, yellow pages, and special events. In addition to general service information, tailored information (e.g., itineraries) are provided to individual transit users.	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 On-Board Information Services	'Transit Vehicle On-board Information Services' furnishes en route transit users with real-time travel-related information on-board a transit vehicle. Current information that can be provided to transit users includes transit routes, schedules, transfer options, fares, real-time schedule adherence, current incidents, weather conditions, non-motorized transportation services, and special events are provided. In addition to tailored information for individual transit users, it also supports general annunciation and/or display of general schedule information, imminent arrival information, and other information of general interest to transit users.	Transit Vehicle OBE
Transit Vehicle On-Board Trip Monitoring	'Transit Vehicle On-Board Trip Monitoring' tracks vehicle location, monitors fuel usage, collects operational status (doors opened/closed, running times, etc.) and sends the collected, time stamped data to the Transit Management Center.	Transit Vehicle OBE

Includes Information Flows:

Information Flow	Description
host transit vehicle status	Information provided to the ITS on-board equipment from other systems on the Transit Vehicle Platform.
transit stop request	Notification that a transit stop has been requested by a transit user at a roadside stop. This flow identifies the route, stop, and the time of the request.
transit user information	Information about individual transit users boarding a transit vehicle, used to track a user's progress on a scheduled transit trip.
transit vehicle information	Information about the transit vehicle route and stops, including current location along the route and next stop.
transit vehicle operator display	Visual, audible, and tactile outputs to the transit vehicle operator including vehicle surveillance information, alarm information, vehicle system status, information from the operations center, and information indicating the status of all other on-board ITS services.
transit vehicle operator input	Transit vehicle operator inputs to on-board ITS equipment, including tactile and verbal inputs. Includes authentication information, on-board system control, emergency requests, and fare transaction data.
traveler input	User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service.
traveler interface updates	Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users;	Reduce fatalities and injuries
C. Increase the security of the transportation system for motorized and nonmotorized users;	Improve security
D. Increase the accessibility and mobility of people and for freight;	Reduce congestion
J. Enhance travel and tourism.	Support travel and tourism

Associated Objective Categories

Objective Category
Transit Operations and Management: Customer Service
Transit Operations and Management: Safety

Associated Objectives and Performance Measures

Objective	Performance Measure
Decrease by X percent on an annual basis the number of complaints per 1,000 boarding passengers.	Complaint rate.
Decrease the number of personal safety incidents by X percent within Y years.	Number of reported personal safety incidents.
Increase customer service ratings by X percent in Y years.	Customer satisfaction rating
Increase personal safety ratings by X percent within Y years.	Personal safety and customer service ratings.

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 accept stop requests from transit users at roadside stops or directly from their personal devices.	Personal Trip Planning and Route Guidance	06	The personal traveler interface shall allow a traveler to send a stop request to an approaching transit vehicle.
		Transit Center Information Services	08	The center shall receive transit stop requests from travelers and provide them to the appropriate transit vehicles.
		Transit Stop Information Services	05	The public interface for travelers shall allow the traveler to request the transit vehicle at the transit stop.
		Transit Vehicle On-Board Trip Monitoring	06	The transit vehicle shall receive transit stop requests from travelers.
02	Transit Vehicles Operators need to be able to receive transit stop requests submitted from the roadside or from Transit Operations.	RSE Transit User Guidance	02	The field element shall provide stop requests to transit vehicles.
		Transit Center Information Services	08	The center shall receive transit stop requests from travelers and provide them to the appropriate transit vehicles.
		Transit Stop Information Services	05	The public interface for travelers shall allow the traveler to request the transit vehicle at the transit stop.
		Transit Vehicle On-Board Information Services	06	The transit vehicle shall provide to the transit vehicle operator transit stop requests received from travelers or from the transit center.
		Transit Vehicle On-Board Trip Monitoring	07	The transit vehicle shall receive transit stop requests from Transit Operations

Related Sources

Document Name	Version	Publication Date
SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods		8/15/2014

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
Basic Transit Vehicle
Connected Vehicle Roadside Equipment	High	High	Moderate	Class 4
Personal Information Device	High	Moderate	Moderate	Class 4
Transit Management Center	High	High	Moderate	Class 4
Transit Vehicle OBE	High	High	Moderate	Class 4
Traveler Support Equipment	High	Moderate	Moderate	Class 4

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
Basic Transit Vehicle	Transit Vehicle OBE	host transit vehicle status	Moderate	Moderate	Moderate
Basic Transit Vehicle	Transit Vehicle OBE	host transit vehicle status	This can include some sensitive data. However, other data, such as vehicle location and motion will then be broadcast. There also may be proprietary information included in this. DISC THEA believes this to be LOW: "sensor data is not confidential; harm should not come from seeing status."	This is used later on to determine whether a vehicle should request priority at an intersection. If this information is incorrect the vehicle may make false requests. All other flows that use the data from this flow have a MODERATE integrity requirement, therefore, this must also have a MODERATE integrity requirement. DISC: THEA believes this should be HIGH: "sensor data needs to be accurate and should not be tampered with."	This information would need to be available immediately for the application to work.DISC: THEA believes this should be HIGH: "sensor data must be consistently available to feed BSMs broadcast at 10Hz, notifications, etc.."
Connected Vehicle Roadside Equipment	Transit Vehicle OBE	transit stop request	High	Moderate	Moderate
Connected Vehicle Roadside Equipment	Transit Vehicle OBE	transit stop request	Contains PII, including traveler identity, location and stop request information, which is predictive of traveler location.	If corrupted, stop request may not be received or acted upon, which would affect the originator of the request. Limited in scope to that request though.	If this flow is not available then stop requests won't be completed and the originator of the request is inconvenienced. Long term however, if this flow is generally not reliable then users are unlikely to use or rely on it. Should be MODERATE to instill confidence and encourage use.
Connected Vehicle Roadside Equipment	Traveler Support Equipment	transit vehicle information	Low	Moderate	Moderate
Connected Vehicle Roadside Equipment	Traveler Support Equipment	transit vehicle information	Data is intended for public use.	General transit schedule information, as well as more specific "next stop" and similar information should be prompt and correct or users will lose confidence and not use the system. Also inconvenienced by the lack of correct and timely information. Impact is localized and limited however, so MODERATE and not HIGH.	General transit schedule information, as well as more specific "next stop" and similar information should be prompt and correct or users will lose confidence and not use the system. Also inconvenienced by the lack of correct and timely information. Impact is localized and limited however, so MODERATE and not HIGH.
Personal Information Device	Transit Management Center	transit stop request	High	Moderate	Moderate
Personal Information Device	Transit Management Center	transit stop request	Contains PII, including traveler identity, location and stop request information, which is predictive of traveler location.	If corrupted, stop request may not be received or acted upon, which would affect the originator of the request. Limited in scope to that request though.	If this flow is not available then stop requests won't be completed and the originator of the request is inconvenienced. Long term however, if this flow is generally not reliable then users are unlikely to use or rely on it. Should be MODERATE to instill confidence and encourage use.
Personal Information Device	Transit Vehicle OBE	transit stop request	High	Moderate	Moderate
Personal Information Device	Transit Vehicle OBE	transit stop request	Contains PII, including traveler identity, location and stop request information, which is predictive of traveler location.	If corrupted, stop request may not be received or acted upon, which would affect the originator of the request. Limited in scope to that request though.	If this flow is not available then stop requests won't be completed and the originator of the request is inconvenienced. Long term however, if this flow is generally not reliable then users are unlikely to use or rely on it. Should be MODERATE to instill confidence and encourage use.
Personal Information Device	Transit Vehicle OBE	transit user information	Moderate	Moderate	Moderate
Personal Information Device	Transit Vehicle OBE	transit user information	May contain the PII of the originator, which should be readable only by the intended recepient lest the originator's privacy be violated. If the implementation does not provide traveler identity, this may be reduced to LOW.	If this is compromised or corrupted, the user's needs may not be properly communicated or met. If this is forged, the transit provider may provide unnecessary services.	If this is not available, the user may not receive transit services offered, and as with other transit services may ceases using the system. While the immediate impact is LOW, long term impact is MODERATE due to user confidence issues.
Personal Information Device	Traveler	traveler interface updates	Not Applicable	Moderate	Moderate
Personal Information Device	Traveler	traveler interface updates	Personalized data that includes directions and guidance for an individual, but eventually evident anyway.	Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral.	Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.
Transit Management Center	Transit Vehicle OBE	transit stop request	High	Moderate	Moderate
Transit Management Center	Transit Vehicle OBE	transit stop request	Contains PII, including traveler identity, location and stop request information, which is predictive of traveler location.	If corrupted, stop request may not be received or acted upon, which would affect the originator of the request. Limited in scope to that request though.	If this flow is not available then stop requests won't be completed and the originator of the request is inconvenienced. Long term however, if this flow is generally not reliable then users are unlikely to use or rely on it. Should be MODERATE to instill confidence and encourage use.
Transit Vehicle OBE	Connected Vehicle Roadside Equipment	transit vehicle information	Low	Moderate	Moderate
Transit Vehicle OBE	Connected Vehicle Roadside Equipment	transit vehicle information	Data is intended for public use. Not broadcast, but destination will broadcast, so no need to obfuscate.	General transit schedule information, as well as more specific "next stop" and similar information should be prompt and correct or users will lose confidence and not use the system. Also inconvenienced by the lack of correct and timely information. Impact is localized and limited however, so MODERATE and not HIGH.	General transit schedule information, as well as more specific "next stop" and similar information should be prompt and correct or users will lose confidence and not use the system. Also inconvenienced by the lack of correct and timely information. Impact is localized and limited however, so MODERATE and not HIGH.
Transit Vehicle OBE	Personal Information Device	transit vehicle information	Low	Moderate	Moderate
Transit Vehicle OBE	Personal Information Device	transit vehicle information	Data is intended for public use.	General transit schedule information, as well as more specific "next stop" and similar information should be prompt and correct or users will lose confidence and not use the system. Also inconvenienced by the lack of correct and timely information. Impact is localized and limited however, so MODERATE and not HIGH.	General transit schedule information, as well as more specific "next stop" and similar information should be prompt and correct or users will lose confidence and not use the system. Also inconvenienced by the lack of correct and timely information. Impact is localized and limited however, so MODERATE and not HIGH.
Transit Vehicle OBE	Transit Vehicle Operator	transit vehicle operator display	Low	Moderate	Low
Transit Vehicle OBE	Transit Vehicle Operator	transit vehicle operator display	This should not include any sensitive information. It would be possible for a person standing behind the driver to observe the information transmitted.	Some minimal guarantee of data integrity is necessary for all C-ITS flows. This entire application should not directly affect the drivers driving habits. The operator should still be slowing and stopping at yellow or red lights, along with observing all other driving regulations. DISC: Original V2I analysis classified this as LOW.	Even if the operator is not made aware of the signal preemption, the system should still operate correctly. The operator should be using the traffic lights to influence their decision about whether or not to stop, not the display.
Transit Vehicle Operator	Transit Vehicle OBE	transit vehicle operator input	Low	Moderate	Low
Transit Vehicle Operator	Transit Vehicle OBE	transit vehicle operator input	This information is transmitted through systems on board the Transit Vehicle. Even if the vehicle were compromised and these communications monitored, most of this information is directly observable.	Some minimal guarantee of data integrity is necessary for all C-ITS flows. If this is compromised, it could result in an incorrect signal priority request, which has minimal impact. DISC: Original V2I analysis classified this as LOW.	A delay in reporting this may result in a signal priority request not going through, which has minimal impact.
Traveler	Personal Information Device	traveler input	Not Applicable	Moderate	Low
Traveler	Personal Information Device	traveler input	This data is informing the vehicle of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it.	While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans.	Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Traveler	Traveler Support Equipment	traveler input	Not Applicable	Moderate	Low
Traveler	Traveler Support Equipment	traveler input	Publicly available information, while not directly observable, is intended for widespread distribution	While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans.	Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE.
Traveler Support Equipment	Connected Vehicle Roadside Equipment	transit stop request	High	Moderate	Moderate
Traveler Support Equipment	Connected Vehicle Roadside Equipment	transit stop request	Contains PII, including traveler identity, location and stop request information, which is predictive of traveler location.	If corrupted, stop request may not be received or acted upon, which would affect the originator of the request. Limited in scope to that request though.	If this flow is not available then stop requests won't be completed and the originator of the request is inconvenienced. Long term however, if this flow is generally not reliable then users are unlikely to use or rely on it. Should be MODERATE to instill confidence and encourage use.
Traveler Support Equipment	Transit Management Center	transit stop request	High	Moderate	Moderate
Traveler Support Equipment	Transit Management Center	transit stop request	Contains PII, including traveler identity, location and stop request information, which is predictive of traveler location.	If corrupted, stop request may not be received or acted upon, which would affect the originator of the request. Limited in scope to that request though.	If this flow is not available then stop requests won't be completed and the originator of the request is inconvenienced. Long term however, if this flow is generally not reliable then users are unlikely to use or rely on it. Should be MODERATE to instill confidence and encourage use.
Traveler Support Equipment	Traveler	traveler interface updates	Not Applicable	Moderate	Moderate
Traveler Support Equipment	Traveler	traveler interface updates	Publicly available information, while not directly observable, is intended for widespread distribution	Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral.	Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name	Title	Physical Object
CTI 4001 RSU	Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589)	Connected Vehicle Roadside Equipment

System Requirements

System Requirement		Need
001	The system shall receive transit stop requests from travelers and provide them to the appropriate transit vehicles.	01	Transit Operations needs to be able to accept stop requests from transit users at roadside stops or directly from their personal devices.
001		02	Transit Vehicles Operators need to be able to receive transit stop requests submitted from the roadside or from Transit Operations.
002	The system shall provide stop requests to transit vehicles.	02	Transit Vehicles Operators need to be able to receive transit stop requests submitted from the roadside or from Transit Operations.
003	The system shall allow the traveler to request the transit vehicle at the transit stop.	01	Transit Operations needs to be able to accept stop requests from transit users at roadside stops or directly from their personal devices.
003		02	Transit Vehicles Operators need to be able to receive transit stop requests submitted from the roadside or from Transit Operations.
004	The system shall allow a traveler to send a stop request to an approaching transit vehicle.	01	Transit Operations needs to be able to accept stop requests from transit users at roadside stops or directly from their personal devices.
005	The system shall provide to the transit vehicle operator transit stop requests received from travelers or from the transit center.	02	Transit Vehicles Operators need to be able to receive transit stop requests submitted from the roadside or from Transit Operations.
006	The system shall receive transit stop requests from travelers.	01	Transit Operations needs to be able to accept stop requests from transit users at roadside stops or directly from their personal devices.
007	The system shall receive transit stop requests from Transit Operations	02	Transit Vehicles Operators need to be able to receive transit stop requests submitted from the roadside or from Transit Operations.