Parking Management Center --> Vehicle Operations and Service Center:
parking maneuver request

Definitions

parking maneuver request (Information Flow): Request to move a vehicle to a designated parking spot, an intermediate staging area, or a pickup location. The request identifies the vehicle, the starting location, destination location, and information about the recommended route.

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.

Vehicle Operations and Service Center (Destination Physical Object): 'Vehicle Operations and Service Center' (VOSC) represents centers that provide telematics services to vehicles using wide-area (e.g. cellular) communications, including traveler information, emergency services, vehicle diagnostics, over-the-air software updates, vehicle maintenance information and warnings, remote vehicle operation, and provision of service options for these vehicles. See also 'Transportation Information Center' that provides traveler information, trip planning, and routing services and 'Emergency Management Center' that provides call-taking and emergency response services that may also be implemented by a VOSC.

This Triple is an instantiation of the more general triple:

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:

  • None

This Triple has the following triple relationships:

None

This Triple is an instantiation of the more general triple:

Communication Solutions

  • No communications solutions identified.

    • This Triple is an instantiation of the more general triple:

    Characteristics

    CharacteristicValue
    Time Context Now
    Spatial Context Regional
    Acknowledgement True
    CardinalityUnicast
    InitiatorSource
    AuthenticableTrue
    EncryptTrue


    InteroperabilityDescription
    RegionalInteroperability 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).

    This Triple is an instantiation of the more general triple:

    Security

    Information Flow Security
      Confidentiality Integrity Availability
    Rating Moderate Moderate Moderate
    Basis Vehicle commands should result in vehicle movement, which is directly observable. There may be instances where remote monitoring of these instructions enables a nefarious use case, which suggests a MODERATE level of obfuscation is reasonable, as the impact is likely limited to a single vehicle with no safety impact. This flow directs vehicle movement, so needs to be unaltered lest the vehicle behave unexpectedly. There must always be a fallback for a driveable vehicle though, suggesting MODERATE at most. Availability will depend on the parking structure; in some cases this will be MODERATE, in others LOW, depending on how much automated movements facilitate parking opreations.


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt True