Parking Management Center --> Transit Management Center:
parking arrival information

Definitions

parking arrival information (Information Flow): Detailed parking information to support park and ride operations. This includes information on entrances available to transit and detailed arrival information indicating where vehicles are currently arriving in the lot for park and ride service.

Parking Management Center (Source 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.

Transit Management Center (Destination 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.

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:

RelationshipSourceDestinationFlow
Depends On Parking Area Equipment Parking Management Center parking area arrival information

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - OMG DDS

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for OMG DDS. The (None-Data) standards include an unspecified set of standards at the upper layers. The OMG DDS standards include lower-layer standards that support secure data sharing and command operations between remote devices.

ITS Application Entity
Mind the gapMind the gap

Development needed
Click gap icons for more info.
Mgmt

OMG DDS
Facilities
Mind the gapMind the gapMind the gap

Development needed
OMG DDS
OMG DDS-RPC
OMG DDSI-RTPS
Security

OMG DDS-Security
TransNet

IETF RFC 768
IP Alternatives
Access

Internet Subnet Alternatives
TransNet TransNet

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 Regional
Acknowledgement False
Cardinality Unicast
Initiator Destination
Authenticable True
Encrypt False


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 Not Applicable Moderate Moderate
Basis This shold be published, public information. If unavailable, corrupted or modified, could lead to degraded performance of park-and-ride operations; dependon on the local geometry and traffic flow, could also impinge other parking. If this flow is not avaliable, park-and-ride services will be hampered. Depending on the volume and local regulations, this could be LOW.


Security Characteristics Value
Authenticable True
Encrypt False