Parking Area Equipment --> Parking Management Center:
parking area information
Definitions
parking area information (Information Flow): Current status for the parking area. This includes information on general parking area status (operating hours, open entrances and exits, entrance queue status, parking operator information, current parking occupancy and availability).
Parking Area Equipment (Source 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.
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:
- Parking Area Management
- Parking Area Park and Ride Operations
- Parking Coordination
- Parking Management
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- Parking - Secure Internet (ITS) (19)
- (None-Data) - Secure Internet (ITS) (43)
- Data for Distribution (TBD) - Apache Kafka (44)
- Data for Distribution (TBD) - OMG DDS (44)
- Data for Distribution (TBD) - OASIS MQTT (50)
- Data for Distribution (TBD) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
OASIS MQTT DMP |
Facilities
OASIS MQTT |
Security
|
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
TempBCL2 TempSTDL2
TempBCL3 TempSTDL3
TempBCL4 TempSTDL4
TempBCL5 TempSTDL5
Access Access
TempBCL2 TempSTDL2
TempBCL3 TempSTDL3
TempBCL4 TempSTDL4
TempBCL5 TempSTDL5
ITS Application ITS Application
TempBCL2 TempSTDL2
TempBCL3 TempSTDL3
TempBCL4 TempSTDL4
TempBCL5 TempSTDL5
Mgmt Mgmt
TempBCL2 TempSTDL2
TempBCL3 TempSTDL3
TempBCL4 TempSTDL4
TempBCL5 TempSTDL5
Facility Facility
TempBCL2 TempSTDL2
TempBCL3 TempSTDL3
TempBCL4 TempSTDL4
TempBCL5 TempSTDL5
Security Security
TempBCL2 TempSTDL2
TempBCL3 TempSTDL3
TempBCL4 TempSTDL4
TempBCL5 TempSTDL5
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 | False |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
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. | While useful, there is no signficant impact if this flow is not available. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |