Parking Management (Subsystem*)

Diagrams for Parking Management Subsystem (PMS):

• Subsystem Interfaces
• Terminator Interfaces

Functionality: Equipment Packages* and PSpecs*

• Parking Coordination (Equipment Package*)
  PSpecs:
  • 1.2.5.1-Provide Parking Lot Static Data
  • 1.2.5.2-Coordinate Other Parking Data
  • 1.2.5.4-Determine Dynamic Parking Lot State
  • 7.2.1.7-Update Parking Lot Data
  • 7.2.1.9-Manage Parking Lot Reservations

• Parking Data Collection (Equipment Package*)
  PSpecs:
  • 1.2.5.5-Manage Parking Archive Data

• Parking Electronic Payment (Equipment Package*)
  PSpecs:
  • 5.4.3-Process Parking Lot Violations
  • 7.2.1.1-Read Parking Lot Vehicle Payment Data
  • 7.2.1.10-Determine Advanced Charges
  • 7.2.1.2-Calculate Vehicle Parking Lot Charges
  • 7.2.1.3-Collect Bad Charge Payment Data
  • 7.2.1.4-Check for Advanced Parking Lot Payment
  • 7.2.1.5-Bill Driver for Parking Lot Charges
  • 7.2.1.6-Manage Parking Lot Financial Processing
  • 7.2.1.7-Update Parking Lot Data
  • 7.2.1.8-Register for Advanced Parking Lot Payment
  • 7.2.2-Produce Parking Lot Displays
  • 7.2.3-Obtain Parking Lot Violator Image
  • 7.2.5-Detect Vehicle for Parking Lot Payment

• Parking Management (Equipment Package*)
  PSpecs:
  • 1.2.5.1-Provide Parking Lot Static Data
  • 1.2.5.3-Provide Parking Lot Operator Interface
  • 1.2.5.4-Determine Dynamic Parking Lot State
  • 1.2.5.6-Detect Vehicles in Parking Lot
  • 1.2.5.7-Output Parking Lot Information to Drivers

• Parking Short Range Traveler Information Communications (Equipment Package*)
  PSpecs:
  • 1.2.5.7-Output Parking Lot Information to Drivers

Inputs/Outputs: Architecture Flows* and Data Flows*

Archived Data Management Subsystem Parking Management

• archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
  Data Flows*:
  • parking_archive_request

• archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
  Data Flows*:
  • parking_archive_status

DMV Parking Management

• registration (Architecture Flow*) - Registered owner of vehicle and associated vehicle information.
  Data Flows*:
  • fdmv-parking_lot_violation_state_identity
  • fdmv-parking_lot_violation_vehicle_registration

Financial Institution Parking Management

• transaction status (Architecture Flow*) - Response to transaction request. Normally dealing with a request for payment.
  Data Flows*:
  • ffi-bad_charges_payment_updates
  • ffi-confirm_charges_payment

Information Service Provider Parking Management

• parking lot data request (Architecture Flow*) - Request for parking lot occupancy, fares, and availability. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
  Data Flows*:
  • advanced_other_charges_request
  • advanced_traveler_charges_request
  • parking_lot_data_request
  • parking_lot_dynamic_information_request_by_isp
  • parking_lot_price_data_request
  • parking_lot_static_information_request_by_isp

• parking reservations request (Architecture Flow*) - Reservation request for parking lot.
  Data Flows*:
  • parking_lot_reservation_request

Other Parking Parking Management

• parking coordination (Architecture Flow*) - Information that enables parking management activities to be coordinated between different parking operators or systems in a region.
  Data Flows*:
  • fop-parking_coordination_data

Parking Management Archived Data Management Subsystem

• parking archive data (Architecture Flow*) - Data used to analyze and monitor trends in parking demand, pricing, and operational actions. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
  Data Flows*:
  • parking_archive_data

Parking Management DMV

• license request (Architecture Flow*) - Request supporting registration data based on license plate read during violation.
  Data Flows*:
  • tdmv-parking_lot_violation_identity_code
  • tdmv-parking_lot_violation_vehicle_license

Parking Management Driver

• driver parking information (Architecture Flow*) - Presentation of general parking information to drivers including lot status, parking availability, and directions to available spaces, entrances, and exits.
  Data Flows*:
  • td-parking_information

• roadside transaction status (Architecture Flow*) - The status of an electronic payment transaction provided directly to the driver via sign or other roadside infrastructure.
  Data Flows*:
  • td-parking_lot_payment_confirmed
  • td-parking_lot_payment_invalid

Parking Management Enforcement Agency

• payment violation notification (Architecture Flow*) - Notification to enforcement agency of a toll, parking, or transit fare payment violation.
  Data Flows*:
  • tea-parking_violation_data

Parking Management Financial Institution

• payment request (Architecture Flow*) - Request for payment from financial institution.
  Data Flows*:
  • tfi-parking_lot_payment_violator_data
  • tfi-request_charges_payment

Parking Management Information Service Provider

• parking information (Architecture Flow*) - General parking information and status, including current parking availability.
  Data Flows*:
  • dynamic_parking_information_for_isp
  • parking_lot_availability
  • parking_lot_price_data
  • static_parking_information_for_isp

• parking lot reservation confirmation (Architecture Flow*) - Confirmation for parking lot reservation.
  Data Flows*:
  • advanced_other_charges_confirm
  • advanced_traveler_charges_confirm
  • parking_lot_reservation_confirm

Parking Management Other Parking

• parking coordination (Architecture Flow*) - Information that enables parking management activities to be coordinated between different parking operators or systems in a region.
  Data Flows*:
  • top-parking_coordination_data

Parking Management Parking Operator

• parking status (Architecture Flow*) - Presentation of information to the parking operator including operational status and transaction reports.
  Data Flows*:
  • tpo-archive_status
  • tpo-change_lot_state
  • tpo-parking_lot_charge_change_request
  • tpo-parking_lot_status
  • tpo-request_advanced_parking_payment
  • tpo-transaction_reports

Parking Management Traffic Management

• parking demand management response (Architecture Flow*) - Response to parking demand management change requests indicating level of compliance with request.
  Data Flows*:
  • parking_lot_charge_change_response
  • parking_lot_charge_direct_details

• parking information (Architecture Flow*) - General parking information and status, including current parking availability.
  Data Flows*:
  • dynamic_parking_information_for_traffic
  • parking_information_for_dissemination
  • parking_lot_current_state
  • static_parking_information_for_traffic

Parking Management Transit Management

• parking information (Architecture Flow*) - General parking information and status, including current parking availability.
  Data Flows*:
  • dynamic_parking_information_for_transit
  • static_parking_information_for_transit

Parking Management Traveler Card

• request for payment (Architecture Flow*) - Request to deduct cost of service from user's payment account.
  Data Flows*:
  • ttc-debited_traveler_parking_payment
  • ttc-request_traveler_parking_payment

Parking Management Vehicle

• vehicle parking information (Architecture Flow*) - Parking information for in-vehicle display that is provided to vehicles approaching or in parking facilities. The information provided would include static sign information (e.g., guide signs, service signs, height, width, and weight restrictions, and directional signs) and dynamic information (e.g., current parking availability and locations).
  Data Flows*:
  • parking_to_vehicle_local_parking_data

• vehicle payment request (Architecture Flow*) - Request for information supporting toll and parking payments.
  Data Flows*:
  • parking_lot_payment_request
  • parking_lot_vehicle_payment_data_request

• vehicle payment update (Architecture Flow*) - Data written to vehicle equipment to support electronic toll collection or parking payment.
  Data Flows*:
  • parking_lot_payment_debited
  • parking_lot_vehicle_payment_data_clear
  • parking_lot_vehicle_payment_data_update

Parking Operator Parking Management

• parking operator inputs (Architecture Flow*) - User input from the parking operator to query current status and control the operation of the parking management system.
  Data Flows*:
  • fpo-archive_commands
  • fpo-confirm_advanced_parking_payment
  • fpo-current_lot_state
  • fpo-lot_occupancy
  • fpo-parking_lot_charge_change_response
  • fpo-parking_lot_data
  • fpo-parking_lot_hours_of_operation

• request for performance data (Architecture Flow*) - User input from the parking operator to request current parking service performance data.
  Data Flows*:
  • fpo-transaction_reports_request

Traffic Management Parking Management

• parking demand management request (Architecture Flow*) - Request to change the demand for parking facility use through pricing or other mechanisms.
  Data Flows*:
  • parking_lot_charge_change_request
  • parking_lot_charge_direct_request

• parking lot data request (Architecture Flow*) - Request for parking lot occupancy, fares, and availability. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
  Data Flows*:
  • parking_lot_dynamic_information_request_by_traffic
  • parking_lot_static_information_request_by_traffic

• parking lot inputs (Architecture Flow*) - Instructions for operation of local parking facilities to support regional traffic management objectives (e.g. which parking lot exits to use). Also, includes inputs from traffic sensors to support calculation of parking lot occupancy and support more effective management of parking entrances and exits.
  Data Flows*:
  • parking_lot_input_data
  • selected_parking_lot_control_strategy
  • static_data_for_parking_lots

Transit Management Parking Management

• parking lot data request (Architecture Flow*) - Request for parking lot occupancy, fares, and availability. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
  Data Flows*:
  • parking_lot_dynamic_information_request_by_transit
  • parking_lot_static_information_request_by_transit

Traveler Card Parking Management

• payment (Architecture Flow*) - Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
  Data Flows*:
  • ftc-confirm_traveler_parking_payment
  • ftc-traveler_parking_input_credit_identity

Vehicle Parking Management

• vehicle payment information (Architecture Flow*) - Information provided for payment of tolls and parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested.
  Data Flows*:
  • parking_lot_payment_confirmation
  • parking_lot_vehicle_payment_data_collect

Vehicle Characteristics Parking Management

• vehicle characteristics (Architecture Flow*) - The physical or visible characteristics of an individual vehicle that can be measured to classify a vehicle and imaged to uniquely identify a vehicle.
  Data Flows*:
  • From_Vehicle_Characteristics