Parking Manager --> Parking Management Center:
parking manager input
Definitions
parking manager input (Information Flow): Input from the parking manager to query current status and control back office operations for a parking management system.
Parking Manager (Source Physical Object): 'Parking Manager' is the human operator that supports back office operations for one or more parking areas.
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:
- CVO05: Commercial Vehicle Parking
- PM01: Parking Space Management
- PM02: Smart Park and Ride System
- PM03: Parking Electronic Payment
- PM04: Regional Parking Management
- PM05: Parking Reservations
- PM06: Loading Zone Management
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- fpm-archive_commands
- fpm-parking_equipment_controls
- fpm-parking_lot_charge_change_response
- fpm-parking_lot_data
- fpm-parking_lot_static_data_input
- fpm-parking_to_roadside_controls
- fpm-transaction_reports_request
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Interactive | Parking Management Center | Parking Manager | parking status |
Communication Solutions
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. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | High | High | |
| Basis | Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | |
| Security Characteristics | Value |
|---|