Other Parking Management Centers --> Parking Management Center:
parking coordination
This triple is bi-directional. See also
Parking Management Center --> Other Parking Management Centers: parking coordination
Definitions
parking coordination (Information Flow): Information that enables parking management activities to be coordinated between different parking operators or systems in a region.
Other Parking Management Centers (Source Physical Object): Representing another parking facility's back office operations, 'Other Parking Management Centers' provides a source and destination for information that may be exchanged between peer parking systems. It enables parking management activities to be coordinated between different parking operators or systems in a 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:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: DATEX - DATEX Messaging (6)
- (None-Data) - Secure Internet (ITS) (32)
Selected Solution
Solution Description
ITS Application Entity
|
Click gap icons for more info.
|
||
Mgmt
|
Facilities
No Standard Needed |
Security
IETF RFC 8446 |
|
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 | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
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 | This should not include any PII, but may include pricing schedules, entry restrictions and similar data. May also include configurtion-related information; generally wise to obfuscate all of this information. | Inter-agency and system-to-system coordination data needs to be correct or systems may not properly coordinate | Should not need to be exchanged often. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |