Transit Management Center --> Parking Management Center:
transit park and ride information
Definitions
transit park and ride information (Information Flow): Detailed transit information to support parking and ride operations. This includes transit scheduled and actual arrival times at the park and ride facility and services offered by arriving transit vehicles.
Transit Management Center (Source Physical Object): 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.
Parking Management Center (Destination Physical Object): The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- dynamic_park_and_ride_lot_information_request
- transit_services_for_park_and_ride
- transit_vehicle_arrival_time
This Triple has the following triple relationships:
| None |
Communication Solutions
-
(None-Data) - Secure Internet (ITS) (32)
-
(None-Data) - Apache Kafka (36)
-
(None-Data) - OMG DDS (36)
-
(None-Data) - OASIS MQTT (42)
-
(None-Data) - OASIS AMQP (45)
Selected Solution
(None-Data) - Secure Internet (ITS)Solution Description
|
ITS Application Entity
Development needed  |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
Development needed |
Security
|
|
|
TransNet
|
|||
|
Access
Internet Subnet Alternatives |
|||
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Local |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | True |
| Interoperability | Description |
|---|---|
| Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | Moderate | Low | |
| Basis | Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | Most likely not a frequently updated flow. If application context requires frequent update this could be MODERATE. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |