Parking Operator --> Parking Area Equipment:
parking operator input
Definitions
parking operator input (Information Flow): User input from the parking operator to query current status and control the operation of the parking management system.
Parking Operator (Source Physical Object): 'Parking Operator' is the human attendant that may be physically present at the parking lot facility to monitor the operational status of the facility.
Parking Area Equipment (Destination Physical Object): 'Parking Area Equipment' provides electronic monitoring and management of parking facilities. It supports an I2V link to the Vehicle that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. The two primary approaches to monitoring parking area usage are sensing vehicles within parking spots or counting vehicles as they come in and as they leave the area. This portion of the functionality must be located in the parking area where it can monitor, classify, and share information with customers and their vehicles. See also the separate 'Parking Management Center' physical object that may be located in a back office, remote from the parking area, which interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region.
Included In
This Triple is in the following Service Packages:
- CVO05: Commercial Vehicle Parking
- PM01: Parking Space Management
- PM02: Smart Park and Ride System
- PM03: Parking Electronic Payment
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- fpo-current_lot_state
- fpo-cv_parking_lot_inputs
- fpo-lot_occupancy
- fpo-park_and_ride_data_input
- fpo-parking_lot_hours_of_operation
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Interactive | Parking Area Equipment | Parking Operator | parking area status |
Communication Solutions
No communications solutions identified.Characteristics
| 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. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | High | High | |
| Basis | Field operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Field operations flows should generally be correct and available as these are the primary interface between operators and system. | Field operations flows should generally be correct and available as these are the primary interface between maintenance personnel and the system. | |