Transit Management Center --> Remote Vehicle Operator:
remote operator data
Definitions
remote operator data (Information Flow): Presentation of status of a remote controlled vehicle and its surrouding environment. This data keeps the operator appraised of current vehicle status and provides feedback to the operator as control commands are provided. It also supports review of historical data and preparation for future service activities.
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.
Remote Vehicle Operator (Destination Physical Object): The 'Remote Vehicle Operator' represents the person or people that support remote vehicle control, monitoring the controlled vehicle and it's surrounding environment and providing control commands for use by the automated driving system in the remote vehicle.
This Triple is an instantiation of the more general triple:
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:
- None
This Triple has the following triple relationships:
| None |
This Triple is an instantiation of the more general triple:
Communication Solutions
This Triple is an instantiation of the more general triple:
Characteristics
| Characteristic | Value |
|---|---|
| None defined |
| Interoperability | Description |
|---|---|
| Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
This Triple is an instantiation of the more general triple:
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | High | Moderate | |
| Basis | While it is unlikely this has any safety impact, it may betray commercial operations, so should be protected for competitive reasons, and potentially for privacy reasons depending on the configuration of the vehicle. | If this flow is incorrect or unavailable remote operations will be negatively impacted, which can also impact surrounding vehicles; it may have a negative impact to convenience and safety, which could be MODERATE or HIGH depending on the type of vehicle, what it is carrying and where it is. | If this flow is incorrect or unavailable remote operations will be negatively impacted, which can also impact surrounding vehicles; it may have a negative impact to convenience and safety, which could be MODERATE or HIGH depending on the type of vehicle, what it is carrying and where it is. | |
| Security Characteristics | Value |
|---|