University of Akron Roo Express Shuttle Service Vehicles
Status: Existing
Description
Represents the fixed–route shuttle vehicles for the Roo Express Shuttle Service. All shuttle vehicles are equipped with AVL to track bus location information in real–time, which riders can access via the University website or using the DoubleMap Bus Tracker mobile application.
Stakeholders
Physical Objects
Functional Objects
| Functional Object | Description | User Defined |
|---|
| ITS Communications Support | 'ITS Communications Support' provides means to send and receive messages to and from other ITS Objects. It provides mechanisms for scheduling and prioritizing communications traffic. It may also provide relay functions. | False |
|---|
| ITS Management Support | 'ITS Management Support' provides management of the ITS Object. This includes management of regulatory information and policies, management of application processes, management of communication system configuration and update management, communications interfaces, protocol–specific techniques to ensure interoperability such as service advertisements, communications congestion management and interference management, local device states and communications information, billing management, fault management, service level and performance monitoring. | False |
|---|
| ITS Security Support | 'ITS Security Support' provides communications and system security functions to the ITS Object, including privacy protection functions. It may include firewall, intrusion management, authentication, authorization, profile management, identity management, cryptographic key management. It may include a hardware security module and security management information base. | False |
|---|
| 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. | False |
|---|
| Transit Vehicle Schedule Management | 'Transit Vehicle Schedule Management' monitors schedule performance and identifies corrective actions when a deviation is detected. It provides two–way communication between the transit vehicle and center, enabling the center to communicate with the vehicle operator and monitor on–board systems. | False |
|---|
| Transit Vehicle Signal Priority | 'Transit Vehicle Signal Priority' provides the capability for transit vehicles to determine eligibility for priority and request signal priority at signalized intersections, ramps, and interchanges through short range communication with traffic control equipment at the roadside. | False |
|---|
| Vehicle Data Subscription Management | 'Vehicle Data Subscription Management' manages data subscriptions for an end user. It provides access to a catalog of available data, manages the necessary user information and rules that govern the data subscriptions, supports communications with data providers to collect data per the subscription rules, and makes the data available to the end user. It provides the local user interface through which a user can specify and manage subscriptions. It supports different mechanisms for collecting data for the end–user including one–time query–response as well as publish–subscribe services. | False |
|---|
Physical Standards
| Document Number | Title | Description |
|---|
| ISO 21217 | Intelligent transport systems –– Communications access for land mobiles (CALM) –– Architecture | ISO 21217 describes the communications reference architecture of nodes called "ITS station units" designed for deployment in ITS communication networks. While it describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. It also describes the various communication modes for peer–to–peer communications over various networks between ITS communication nodes. These nodes may be ITS station units as described in the document or any other reachable nodes. ISO 21217 specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain. |
|---|
| NIST FIPS PUB 140–2 | Security Requirements for Cryptographic Modules | This Federal Information Processing Standard (140–2) specifies the security requirements that will be satisfied by a cryptographic module, providing four increasing, qualitative levels intended to cover a wide range of potential applications and environments. The areas covered, related to the secure design and implementation of a cryptographic module, include specification; ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self–tests; design assurance; and mitigation of other attacks. |
|---|
Interfaces To
(View Context Diagram)