< < PM05 : PM06 : PS01 > >

PM06: Loading Zone Management

This service package manages the occupancy of spaces in a loading/ unloading zone. It monitors the current status of each loading/unloading zone space under its control and makes this information available to arriving vehicles. The service package also operates a reservation system for loading zones, providing the capability for loading zone users, including commercial vehicle drivers or fleet operators, to reserve and pay for future use of a loading/unloading space. Interfaces to the general Vehicle OBE are included since loading zones may be used by any vehicle, though commercial vehicles are the most frequent users.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Driver Vehicle Operates
Fleet and Freight Management Center Maintainer Fleet and Freight Management Center Maintains
Fleet and Freight Management Center Manager Fleet and Freight Management Center Manages
Fleet and Freight Management Center Owner Fleet and Freight Management Center Maintainer System Maintenance Agreement
Fleet and Freight Management Center Owner Fleet and Freight Management Center Manager Operations Agreement
Fleet and Freight Management Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Fleet and Freight Management Center Owner Transportation Information Center Owner Information Exchange Agreement
Fleet and Freight Management Center Owner Transportation Information Center User Service Usage Agreement
Fleet and Freight Management Center Supplier Fleet and Freight Management Center Owner Warranty
Parking Area Equipment Maintainer Parking Area Equipment Maintains
Parking Area Equipment Manager Parking Area Equipment Manages
Parking Area Equipment Owner Driver Application Usage Agreement
Parking Area Equipment Owner Parking Area Equipment Maintainer System Maintenance Agreement
Parking Area Equipment Owner Parking Area Equipment Manager Operations Agreement
Parking Area Equipment Owner Parking Management Center Maintainer Maintenance Data Exchange Agreement
Parking Area Equipment Owner Parking Management Center Owner Information Exchange and Action Agreement
Parking Area Equipment Owner Parking Management Center User Service Usage Agreement
Parking Area Equipment Owner Parking Manager Application Usage Agreement
Parking Area Equipment Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Parking Area Equipment Owner Vehicle Owner Information Exchange and Action Agreement
Parking Area Equipment Owner Vehicle User Service Usage Agreement
Parking Area Equipment Supplier Parking Area Equipment Owner Warranty
Parking Management Center Maintainer Parking Management Center Maintains
Parking Management Center Manager Parking Management Center Manages
Parking Management Center Manager Parking Manager System Usage Agreement
Parking Management Center Owner Parking Area Equipment Maintainer Maintenance Data Exchange Agreement
Parking Management Center Owner Parking Area Equipment Owner Information Provision Agreement
Parking Management Center Owner Parking Area Equipment User Service Usage Agreement
Parking Management Center Owner Parking Management Center Maintainer System Maintenance Agreement
Parking Management Center Owner Parking Management Center Manager Operations Agreement
Parking Management Center Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Parking Management Center Owner Personal Information Device Owner Information Provision Agreement
Parking Management Center Owner Personal Information Device User Service Usage Agreement
Parking Management Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Parking Management Center Owner Transportation Information Center Owner Information Exchange Agreement
Parking Management Center Owner Transportation Information Center User Service Usage Agreement
Parking Management Center Supplier Parking Management Center Owner Warranty
Parking Manager Parking Management Center Operates
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Owner Parking Management Center Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Parking Management Center Owner Information Provision and Action Agreement
Personal Information Device Owner Parking Management Center User Service Usage Agreement
Personal Information Device Owner Parking Manager Application Usage Agreement
Personal Information Device Owner Personal Information Device Maintainer System Maintenance Agreement
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Transportation Information Center Owner Information Provision and Action Agreement
Personal Information Device Owner Transportation Information Center User Service Usage Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Transportation Information Center Maintainer Transportation Information Center Maintains
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Fleet and Freight Management Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Fleet and Freight Management Center Owner Information Exchange Agreement
Transportation Information Center Owner Fleet and Freight Management Center User Service Usage Agreement
Transportation Information Center Owner Parking Management Center Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Parking Management Center Owner Information Exchange Agreement
Transportation Information Center Owner Parking Management Center User Service Usage Agreement
Transportation Information Center Owner Parking Manager Application Usage Agreement
Transportation Information Center Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Personal Information Device Owner Information Provision Agreement
Transportation Information Center Owner Personal Information Device User Service Usage Agreement
Transportation Information Center Owner Transportation Information Center Maintainer System Maintenance Agreement
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Vehicle Characteristics Maintainer Vehicle Characteristics Maintains
Vehicle Characteristics Manager Vehicle Characteristics Manages
Vehicle Characteristics Owner Vehicle Characteristics Maintainer System Maintenance Agreement
Vehicle Characteristics Owner Vehicle Characteristics Manager Operations Agreement
Vehicle Characteristics Supplier Vehicle Characteristics Owner Warranty
Vehicle Maintainer Vehicle Maintains
Vehicle Manager Driver System Usage Agreement
Vehicle Manager Vehicle Manages
Vehicle Owner Parking Area Equipment Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Parking Area Equipment Owner Expectation of Data Provision
Vehicle Owner Parking Area Equipment User Service Usage Agreement
Vehicle Owner Vehicle Maintainer System Maintenance Agreement
Vehicle Owner Vehicle Manager Operations Agreement
Vehicle Supplier Vehicle Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Fleet and Freight Management Center Fleet Administration 2.1.1.1 Manage Commercial Fleet Electronic Credentials and Tax Filing
2.1.1.2 Manage Commercial Vehicle Routes
2.1.1.3 Provide Commercial Fleet Static Route
2.1.1.6 Monitor Commercial Vehicle Route
2.1.2 Provide Commercial Vehicle Fleet Manager Interface
2.1.3 Provide Fleet Manager Commercial Vehicle Communications
2.1.5 Manage Driver Instruction Store
2.1.6 Manage Commercial Vehicle Incidents
2.2.1 Manage CV Electronic Credential and Tax Filing Interface
2.6.1 Provide Commercial Vehicle Manager Tag Data Interface
2.7.6 Provide Freight Manager Interface
2.7.7 Provide Shipper Booking Interface
2.7.8 Manage External Intermodal System Interface
Parking Area Equipment Loading Zone Management 1.2.5.10 Provide Loading Zone Parking Data
1.2.5.3 Provide Parking Lot Operator Interface
1.2.5.7 Output Parking Lot Information to Drivers
7.2.2 Produce Parking Lot Displays
Parking Management Center Parking Coordination 1.2.5.1 Provide Parking Lot Static Data
1.2.5.11 Provide Parking Manager Interface
1.2.5.12 Manage Loading Zone Use
1.2.5.2 Coordinate Other Parking Data
1.2.5.4 Determine Dynamic Parking Lot State
7.2.1.9 Manage Parking Lot Reservations
Personal Information Device Personal Interactive Traveler Information 6.8.1.1.1 Determine Personal Portable Device Guidance Method
6.8.1.1.2 Provide Personal Portable Device Dynamic Guidance
6.8.3.1 Get Traveler Personal Request
6.8.3.2 Provide Traveler with Personal Travel Information
6.8.3.3 Provide Traveler Personal Interface
6.8.3.4 Update Traveler Personal Display Map Data
6.8.3.5 Provide Traveler Transit Services Interface
6.8.3.6 Provide Personal Safety Messages
6.8.3.7 Manage Traveler Personal Social Media Interface
7.5.3 Provide Personal Payment Device Interface
7.6.6.3 Provide Road Use Charging Services Personal Interface
Transportation Information Center TIC Data Collection 6.2.1 Collect Misc Traveler Information
6.2.2 Collect Traffic Data
6.2.3 Collect Transit Operations Data
6.2.4 Collect Multimodal Data
6.2.5 Collect Situation and Sensor Data From Vehicles
6.2.6 Collect Emergency Traveler Data
6.5.4 Process Travel Services Provider Data
6.6.2.3 Provide Route Segment Data for Other Areas
7.4.2 Collect Price Data for Traveler Information Use
TIC Freight-Specific Travel Planning 6.10 Manage Traveler Profiles
6.5.11 Provide Interactive Data Interface for Commercial Vehicle and Freight Operations
TIC Travel Services Information and Reservation 6.2.1 Collect Misc Traveler Information
6.5.1 Provide Broadcast Data Interface
6.5.3 Register Travel Services Providers
6.5.4 Process Travel Services Provider Data
7.4.1.2 Process Travel Services Provider Payments
7.4.1.6 Process Traveler Trip and Other Services Payments

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Driver Vehicle The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Fleet and Freight Management Center Center The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet.
Parking Area Equipment Field '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 Center 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.
Parking Manager Center 'Parking Manager' is the human operator that supports back office operations for one or more parking areas.
Personal Information Device Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Transportation Information Center Center The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Vehicle Vehicle This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
Vehicle Characteristics Vehicle 'Vehicle Characteristics' represents the external view of individual vehicles of any class from cars and light trucks up to large commercial vehicles and down to micromobility vehicles (MMVs). It includes vehicle physical characteristics such as height, width, length, weight, and other properties (e.g., magnetic properties, number of axles) of individual vehicles that can be sensed and measured or classified. This physical object represents the physical properties of vehicles that can be sensed by vehicle-based or infrastructure-based sensors to support vehicle automation and traffic sensor systems. The analog properties provided by this terminator represent the sensor inputs that are used to detect and assess vehicle(s) within the sensor's range to support safe AV operation and/or responsive and safe traffic management.

Includes Functional Objects:

Functional Object Description Physical Object
Fleet Administration 'Fleet Administration' provides vehicle tracking, dispatch, and reporting capabilities to fleet management personnel. It gathers current road conditions, commercial vehicle-specific traffic and parking information, prepares vehicle routes, and provides a fleet interface for toll collection. It also provides route plan information for network performance evaluation. As part of the tracking function, it monitors commercial vehicle location, compares it against the known route and notifies the Emergency Management Center and Fleet-Freight Manager of any deviations, including HAZMAT route restriction violations. It supports carrier participation in wireless roadside inspection programs, monitoring geographic trigger areas and providing current safety data on behalf of the commercial vehicles it manages. It supports pre-hiring checks for potential drivers and monitors the performance of each driver who is hired. It also supports ongoing monitoring of the company's safety performance. Fleet and Freight Management Center
Loading Zone Management 'Loading Zone Management' manages loading zones. It monitors loading zone space occupancy and makes this information available to arriving vehicles and other applications. It monitors the time each vehicle spends in the loading zone and provides this information to drivers in the zone and other applications. Day and time specific management is supported for loading zones that revert to normal vehicle parking spaces in off hours and other day/time specific management strategies. In advanced implementations, reservations are accepted so that a loading zone spot can be reserved with an optional accompanying payment. Vehicles associated with the reservation are identified on arrival and directed to the reserved spot. Parking Area Equipment
Parking Coordination 'Parking Coordination' supports communication and coordination between equipped parking facilities and also supports regional coordination between parking facilities and traffic management systems. Coordination with traffic management supports local traffic control coordination in and around the parking facility and broader regional coordination. It also shares information with transit management systems and information providers to support multimodal travel planning, including parking reservations capabilities. Information including current parking availability, system status, and operating strategies are shared to enable local parking facility management that supports regional transportation strategies. Parking Management Center
Personal Interactive Traveler Information 'Personal Interactive Traveler Information' provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by personal devices including personal computers and personal portable devices such as smart phones. Personal Information Device
TIC Data Collection 'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. Transportation Information Center
TIC Freight-Specific Travel Planning 'TIC Freight-Specific Travel Planning' provides traveler information and trip planning services for freight routes from source to destination, customized for freight users to indicate truck routes, truck stops, inspection stations, steep grades, etc. Transportation Information Center
TIC Travel Services Information and Reservation 'TIC Travel Services Information' disseminates information about traveler services such as lodging, restaurants, electric vehicle charging, and service stations. Tailored traveler service information is provided on request that meets the constraints and preferences specified by the traveler. This application also supports reservations and advanced payment for traveler services including parking and loading zone use. Transportation Information Center
Vehicle Loading Zone Access 'Vehicle Loading Zone Access' collects information on loading zone availability and makes this information available to the driver. It also provides the capability to reserve loading zone space prior to arrival. Vehicle

Includes Information Flows:

Information Flow Description
commercial vehicle trip information Information about vehicle trips including load information, location, speed, and routing. The information would be sanitized for distribution outside of the commercial vehicle company.
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver parking information Presentation of general parking information to drivers including lot status, parking availability, and directions to available spaces, entrances, and exits.
driver updates Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
freight traveler information preferences Traveler information preferences from fleet and freight management systems or commercial vehicle drivers including: area covered by fleet/driver, types of freight managed (including special restrictions), preferred routes, other travel preferences pertaining to trip costs or tolls. Also covers revised trip planning requirements for trips already underway.
freight-specific traveler information Traveler information customized for freight users to indicate truck routes, permit information, truck stops, inspection stations, steep grades, high-profile vehicle advisories, etc. Information provided includes freight-related road and weather conditions, parking information, and route plans.
loading zone application info Loading zone application information including loading zone parking configuration and associated parameters and thresholds that control the algorithms that monitor loading zone occupancy and the loading zone information that is delivered. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
loading zone application status Loading zone application status that includes current operational state and status of the field equipment and current, aggregate loading zone data that can be used to monitor loading zone space usage and availability.
loading zone information Information about a loading zone including static information (operating hours, rules, restrictions, and fee schedule as applicable) and real time information about current occupancy.
loading zone parking information Information provided for a loading zone and associated holding areas. It includes parking reservation(s), confirmation (or non-confirmation) information, alternative options, and detailed information on the holding parking areas, and the loading zone, including guidance within and between the holding and loading zone areas.
loading zone reservation confirmation Loading zone reservation confirmation and associated instructions.
loading zone reservation request Request for a loading zone space that identifies the requestor and vehicle, the requested date/time, the vehicle type, the estimated duration, and associated identification and payment information.
loading zone use request Request, booking, and confirmation that supports reservation for use of a loading or unloading area.
parking manager input Input from the parking manager to query current status and control back office operations for a parking management system.
parking status Presentation of information to the parking manager including operational status and transaction reports. This includes aggregated status for parking areas as well as status for back office operations.
travel services information Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveler.
travel services request Request for travel service information including tourist attractions, lodging, restaurants, electric vehicle charging, service stations, and emergency services. The request identifies the type of service, the area of interest, optional reservation request information, parameters that are used to prioritize or filter the returned information, and sorting preferences.
user account reports Reports on services offered/provided and associated charges.
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes.
user profile Information provided to register for a travel service and create a user account. The provided information includes personal identification, traveler preferences (e.g., travel mode, micro-mobility options, accessibility needs, and assistance needs), priorities for the preferences, device information, a user ID and password, and information to support payment transactions, if applicable.
vehicle characteristics The physical or visible characteristics of individual vehicles that can be used to detect, classify, and monitor vehicles and imaged to uniquely identify vehicles.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Improve freight network
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
G. Promote efficient system management and operation; Improve efficiency

Associated Objective Categories

Objective Category
Freight Management: Travel Time Delay
Special Event Management: Parking Management

Associated Objectives and Performance Measures

Objective Performance Measure
Decrease the annual average travel time index for freight by X points in Y years. Travel time index: ratio of observed average travel time to free-flow travel time.
Decrease the time spent clearing special event venue parking lots of vehicles by X percent in Y years following each event. Percent decrease in time to clear parking lots.
Enhance parking facility services and management Number of parking facilities with advanced parking information to customers
Enhance parking facility services and management Number of parking facilities with automated occupancy counting and space management
Enhance parking facility services and management Number of parking facilities with coordinated availability information
Enhance parking facility services and management Number of parking facilities with coordinated electronic payment systems
Enhance parking facility services and management Number of parking facilities with electronic fee collection
Enhance parking facility services and management Number parking facilities with electronic fee collection
Increase on-street parking restrictions on X percent of widely used routes during special events in Y years. Percent of routes widely used during planned special events with on-street parking restrictions.
Increase the mobility index ([Ton-miles of travel] / [Vehicle-miles of travel * Average speed]) by X percent in Y years. Mobility index for system users defined as [Ton-miles of travel] / [Vehicle-miles of travel * Average speed].
Increase the number of special events that use shared parking facilities (e.g., parking lots of nearby businesses or organizations) by X percent in Y years. Number of special events that use shared parking facilities.
Increase the use of flexible pricing mechanisms near special event locations on X percent of parking spaces in Y years. Percent of parking spaces near special event locations that use flexible pricing mechanisms.

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Parking Operations needs to be capable of monitoring occupancy of spaces in a loading/unloading zone. Fleet Administration 14 The center shall provide routes to its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, and incident information.
Loading Zone Management 01 The parking element shall monitor the current status of each loading/unloading zone space under its control.
03 The parking element shall provide real-time status of loading/ unloading zone spaces to drivers or fleet operations.
Parking Coordination 01 The parking element shall exchange parking management data with other parking facilities including location, hours, availability, status, lot usage, operating strategies, and charging information.
05 The parking element shall distribute parking lot information upon request to traveler information providers to support travel planning.
02 Parking Operations needs to be capable of accepting reservations for the use of spaces in a loading/unloading zone. Loading Zone Management 02 The parking element shall support requests for reservations of loading/unloading zone space under its control.
TIC Data Collection 05 The center shall collect, process, and store parking information, including location, availability, and fees.
Vehicle Loading Zone Access 01 The vehicle shall be able to make a request of a parking element for reservation of loading/unloading zone space under the parking element's control.
03 A driver or fleet operator needs to be able to book a loading/ unloading zone space. Fleet Administration 02 The center shall obtain and manage commercial vehicle routes for its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, loading zone conditions, and incident information provided by traveler information systems.
Loading Zone Management 04 The parking element shall inform the customer of future times available to reserve a loading/unloading zone space.
05 The parking element shall accept reservations for loading/unloading zone space at a specific future time.
Personal Interactive Traveler Information 03 The personal traveler interface shall receive traveler services information (such as lodging, restaurants, theaters, bicycle facilities, and other tourist activities) from a center and present it to the traveler upon request.
07 The personal traveler interface shall accept reservations for confirmed trip plans.
08 The personal traveler interface shall support payment for services, such as confirmed trip plans, tolls, transit fares, parking lot charges, map updates, and advanced payment for tolls.
10 The personal traveler interface shall base requests from the traveler on the traveler's current location or a specific location identified by the traveler, and filter the provided information accordingly.
11 The personal traveler interface shall support traveler input in audio or manual form.
12 The personal traveler interface shall present interactive information to the traveler in audible or visual forms consistent with a personal device, and suitable for travelers with hearing and vision physical disabilities.
13 The personal traveler interface shall store frequently requested or used data, including the traveler's identity, home and work locations, etc.
14 The personal traveler interface shall receive travel alerts and present them to the traveler. Relevant alerts are provided based on pre-supplied trip characteristics and preferences.
15 The personal traveler interface shall accept personal preferences, recurring trip characteristics, and traveler alert subscription information from the traveler and send this information to a center to support customized traveler information services.
19 The personal traveler interface shall provide the ability for a traveler to set up and modify a user account for a regional electronic payment system.
26 The personal device shall receive information on available parking including available spaces with associated information about parking restrictions and location for each available space.
TIC Data Collection 10 The center shall collect, process, and store freight specific traveler information.
TIC Freight-Specific Travel Planning 01 The center shall provide customized traveler information for freight users to include truck routes, permit information, truck stops, inspection stations, steep grades, high-profile vehicle advisories, etc. Information provided includes freight-related road and weather conditions, parking information, and route plans.
02 The center shall indicate the area covered by the freight traveler information service.
TIC Travel Services Information and Reservation 05 The center shall manage registration of yellow pages service providers, store provider details, and transact payments for the provider's registration.
11 The center shall support yellow pages service information and reservation requests from a personal device.
Vehicle Loading Zone Access 01 The vehicle shall be able to make a request of a parking element for reservation of loading/unloading zone space under the parking element's control.
02 The vehlcle shall receive loading zone information, including reservation information from a parking element.
04 Parking Operations needs to be able to support a system of electronic payment, either at the time of use, or in advance, for loading/ unloading zone spaces. Loading Zone Management 06 The parking element shall accept payment for a reservation for a loading/unloading zone space at a specific future time.
TIC Data Collection 06 The center shall collect, process, and store toll fee information.
Vehicle Loading Zone Access 03 The vehicle shall be able to make an electronic paymenmt for a space in a loading or unloading zone.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005
CO-UMP Urban Parking Availability 5/31/2021


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Fleet and Freight Management Center Moderate Moderate Moderate Class 2
Parking Area Equipment Moderate Moderate Moderate Class 2
Parking Management Center High High Moderate Class 4
Personal Information Device High High Moderate Class 4
Transportation Information Center Moderate Moderate Moderate Class 2
Vehicle Moderate Moderate Moderate Class 2
Vehicle Characteristics  



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Driver Vehicle driver input Moderate High High
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner Commands must always be able to be given or the driver has no control.
Fleet and Freight Management Center Transportation Information Center commercial vehicle trip information Moderate Moderate Moderate
This data would be sanitized and so would not contain any PII. However it will include the location of commercial vehicles and their loads, which could be competitive if not made available on an equal basis. Thus there is a minimal confidentiality requirement. Data should be correct as it relates to CVO, however there this data is not used for any safety or security purposes, this MODERATE and not HIGH. Freight specific planning activities depend on the sharing of this data, so the flow must be reasonably available to support that application.
Fleet and Freight Management Center Transportation Information Center freight traveler information preferences Moderate Moderate Moderate
Includes identity of the freight traveler, which should be protected as it is PII. DISC: Changed from WYO's suggestion of LOW due to PII. No severe consequences if incorrect, but difficult to justify allowing errors in a flow with MODERATE confidentiality. Preferences settings while useful and convenient, do not necessarily need anything beyond LOW. DISC: WYO disagrees
Parking Area Equipment Driver driver parking information Low Moderate Moderate
This information is presented visually to the driver, essentially broadcast in a limited area. This information deserves some degree of confidence in its accuracy, as if it were compromised could be used to direct drivers to unsafe or inappropriate locations. Without direction information, could be LOW. Depending on the size of the parking infrastructure this might be LOW. For larger facilities, directions and locations of available spaces and exits will not be as readily observable, so this is more useful.
Parking Area Equipment Parking Management Center loading zone application status Moderate Moderate Moderate
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Parking Area Equipment Vehicle loading zone parking information Moderate Moderate Moderate
Reservation-related information is likely to have an identifier that can be associated with a specific vehicle and/or driver, compromise of which could affect the driver's privacy, or the operating company's business. Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused. Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused.
Parking Management Center Parking Area Equipment loading zone application info Low Moderate Moderate
This information flow does not contain any secret data. Information such as the loading zone operational areas will intentionally be broadcast at a later point. This may be raised if it contains sensitive data, as determined by the supplier (for example, because this flow contains proprietary or security-sensitive information about the device). The geofenced loading zone areas must be tracked accurately, otherwise a loading functions may occur in areas not expected, and personnel may be exposed to safety dangers because they are in areas they not expected to be. However, inaccurate information here does not directly lead to the injury of a crew member because there are other indicators of where the incident work zone is. This data should be received in a timely manner after it is sent. This will determine which lanes are blocked off for maintenance vehicle use.
Parking Management Center Parking Manager parking status Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Parking Management Center Personal Information Device user account reports High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Parking Management Center Transportation Information Center loading zone information Low Moderate Moderate
Occupancy information may be sensitive but is also directly observable. So long as this information contains no identifiers other than the zone occupied, it is unlikely that compromise of this information has any significant impacts. If this information is inaccurate it may lead to double-bookings or less optimal usage of the loading zone. This is in effect a monitoring flow that should 'flip' fairly often. If this informaiton is not regularly available it will result in less optimal use of the loading zone.
Parking Management Center Transportation Information Center loading zone reservation confirmation Low Moderate Moderate
Occupancy information may be sensitive but is also directly observable. So long as this information contains no identifiers other than the zone occupied, it is unlikely that compromise of this information has any significant impacts. Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused. Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused.
Parking Manager Parking Management Center parking manager input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Personal Information Device Parking Management Center user account setup High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Personal Information Device Transportation Information Center travel services request Moderate Moderate Moderate
Includes PII such as charges, time and location, reservations. If this information were corrupted or modified the reservations might be misinterpreted and/or incorrectly made, inconveniencing all parties, costing time and money. There are likely to be many different TICs that can provide this service, but loss of availability would represent a loss of use, which tends to lead to negative feedback. From a business perspective, MODERATE availability should be the minimum for this type of convenience service.
Personal Information Device Transportation Information Center user profile Moderate Moderate Low
Personal preferences and similar information will be associated with a user id of some kind, which should be protected to avoid identity and related thefts. User configuration information needs to be correct the user is subject to third party manipulation or poor quality of service. Probably many opportunities to exchange this data, and will not need to be done often.
Transportation Information Center Fleet and Freight Management Center freight-specific traveler information Moderate Moderate Low
Includes origin and destination of the freight traveler, which should be protected as it is PII. Consequences if incorrect limited to a specific vehicle or small group of vehicles, though they could be high priority or hazmat vehicles. Regardless, difficult to justify allowing errors in a flow with MODERATE confidentiality. Detailed routing information is a result, which has a significant effect on an individual commercial vehicle. Could possibly be LOW.
Transportation Information Center Parking Management Center loading zone reservation request Moderate Moderate Moderate
Reservation-related information is likely to have an identifier that can be associated with a specific vehicle and/or driver, compromise of which could affect the driver's privacy, or the operating company's business. Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused. Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused.
Transportation Information Center Personal Information Device travel services information Low Moderate Low
This information is intended for a registry and distribution to interested parties. Obfuscating it will delay and help control the release of the information, but it is difficult to see what advantage might be gained by sniffing this data. Since this data will be used to direct business toward particular travel providers, it must be correct or the provider might be harmed by misrepresentation of its offerings. This could have a substantial financial impact. This information probably does not not need to be updated very often.
Vehicle Driver driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.
Vehicle Parking Area Equipment loading zone use request Moderate Moderate Moderate
Reservation-related information is likely to have an identifier that can be associated with a specific vehicle and/or driver, compromise of which could affect the driver's privacy, or the operating company's business. Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused. Reservation-related information needs to be available and correct or the vehicle will not be able to access need loading zones and loading zones will be underused.

Standards

Currently, there are no standards associated with the physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.





System Requirements

System Requirement Need
001 The system shall obtain and manage commercial vehicle routes for its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, loading zone conditions, and incident infor 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
002 The system shall provide routes to its fleet of vehicles, taking into account route restrictions, advance payment of tolls, HAZMAT restrictions, current traffic and road conditions, and incident information. 01 Parking Operations needs to be capable of monitoring occupancy of spaces in a loading/unloading zone.
003 The system shall exchange parking management data with other parking facilities including location, hours, availability, status, lot usage, operating strategies, and charging information. 01 Parking Operations needs to be capable of monitoring occupancy of spaces in a loading/unloading zone.
004 The system shall distribute parking lot information upon request to traveler information providers to support travel planning. 01 Parking Operations needs to be capable of monitoring occupancy of spaces in a loading/unloading zone.
005 The system shall collect, process, and store parking information, including location, availability, and fees. 02 Parking Operations needs to be capable of accepting reservations for the use of spaces in a loading/unloading zone.
006 The system shall collect, process, and store toll fee information. 04 Parking Operations needs to be able to support a system of electronic payment, either at the time of use, or in advance, for loading/ unloading zone spaces.
007 The system shall collect, process, and store freight specific traveler information. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
008 The system shall provide customized traveler information for freight users to include truck routes, permit information, truck stops, inspection stations, steep grades, high-profile vehicle advisories, etc. Information provided includes freight-related ro 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
009 The system shall indicate the area covered by the freight traveler information service. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
010 The system shall manage registration of yellow pages service providers, store provider details, and transact payments for the provider's registration. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
011 The system shall support yellow pages service information and reservation requests from a personal device. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
012 The system shall monitor the current status of each loading/unloading zone space under its control. 01 Parking Operations needs to be capable of monitoring occupancy of spaces in a loading/unloading zone.
013 The system shall support requests for reservations of loading/unloading zone space under its control. 02 Parking Operations needs to be capable of accepting reservations for the use of spaces in a loading/unloading zone.
014 The system shall provide real-time status of loading/ unloading zone spaces to drivers or fleet operations. 01 Parking Operations needs to be capable of monitoring occupancy of spaces in a loading/unloading zone.
015 The system shall inform the customer of future times available to reserve a loading/unloading zone space. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
016 The system shall accept reservations for loading/unloading zone space at a specific future time. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
017 The system shall accept payment for a reservation for a loading/unloading zone space at a specific future time. 04 Parking Operations needs to be able to support a system of electronic payment, either at the time of use, or in advance, for loading/ unloading zone spaces.
018 The system shall receive traveler services information (such as lodging, restaurants, theaters, bicycle facilities, and other tourist activities) from a center and present it to the traveler upon request. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
019 The system shall accept reservations for confirmed trip plans. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
020 The system shall support payment for services, such as confirmed trip plans, tolls, transit fares, parking lot charges, map updates, and advanced payment for tolls. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
021 The system shall base requests from the traveler on the traveler's current location or a specific location identified by the traveler, and filter the provided information accordingly. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
022 The system shall present interactive information to the traveler in audible or visual forms consistent with a personal device, and suitable for travelers with hearing and vision physical disabilities. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
023 The system shall store frequently requested or used data, including the traveler's identity, home and work locations, etc. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
024 The system shall receive travel alerts and present them to the traveler. Relevant alerts are provided based on pre-supplied trip characteristics and preferences. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
025 The system shall accept personal preferences, recurring trip characteristics, and traveler alert subscription information from the traveler and send this information to a center to support customized traveler information services. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
026 The system shall provide the ability for a traveler to set up and modify a user account for a regional electronic payment system. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
027 The system shall accept reservations for yellow pages services, non-motorized transportation information and event information. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
02 Parking Operations needs to be capable of accepting reservations for the use of spaces in a loading/unloading zone.
03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
028 The system shall base requests from the driver on the vehicle's current location, and filter the provided information accordingly. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
029 The system shall accept personal preferences, recurring trip characteristics, and traveler alert subscription information from the driver and send this information to a center to support customized traveler information services. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
04 Parking Operations needs to be able to support a system of electronic payment, either at the time of use, or in advance, for loading/ unloading zone spaces.
030 The system shall support interactive information requests in audio or manual form. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
031 The system shall present traveler information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.
032 The system shall receive information on available parking including available spaces with associated information about parking restrictions and location for each available space. 03 A driver or fleet operator needs to be able to book a loading/ unloading zone space.