Parent Service Package: PM06
< < PM05.1 : PM06.1 : PM06.2 > >

PM06.1: Loading Zone Information

Monitors the current status of loading/unloading zone spaces and makes this information available to arriving vehicles.

Relevant Regions:

Enterprise
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Fleet and Freight Management Center Developer	Fleet and Freight Management Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Fleet and Freight Management Center Developer	Transportation Information Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Parking Area Equipment Developer	Parking Area Equipment	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Parking Area Equipment Developer	Parking Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Parking Area Equipment Developer	Vehicle Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Parking Management Center Developer	Parking Area Equipment Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Parking Management Center Developer	Parking Management Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Parking Management Center Developer	Transportation Information Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Transportation Information Center Developer	Fleet and Freight Management Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Transportation Information Center Developer	Transportation Information Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Vehicle Developer	Vehicle	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Fleet and Freight Management Center Installer	Fleet and Freight Management Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Fleet and Freight Management Center Owner	Fleet and Freight Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Fleet and Freight Management Center Owner	Fleet and Freight Management Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Parking Area Equipment Installer	Parking Area Equipment	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Parking Area Equipment Owner	Parking Area Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Parking Area Equipment Owner	Parking Area Equipment Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Parking Management Center Installer	Parking Management Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Parking Management Center Owner	Parking Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Parking Management Center Owner	Parking Management Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Transportation Information Center Installer	Transportation Information Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Transportation Information Center Owner	Transportation Information Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Transportation Information Center Owner	Transportation Information Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Vehicle Installer	Vehicle	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Vehicle Owner	Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Vehicle Owner	Vehicle Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Driver	Vehicle	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Fleet and Freight Management Center Maintainer	Fleet and Freight Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Fleet and Freight Management Center Manager	Fleet and Freight Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Fleet and Freight Management Center Manager	Fleet-Freight Manager	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Fleet and Freight Management Center Owner	Fleet and Freight Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Fleet and Freight Management Center Owner	Fleet and Freight Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Fleet and Freight Management Center Owner	TIC Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Fleet and Freight Management Center Owner	Transportation Information Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Fleet and Freight Management Center Owner	Transportation Information Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Fleet and Freight Management Center Owner	Transportation Information Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Fleet and Freight Management Center Supplier	Fleet and Freight Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Fleet-Freight Manager	Fleet and Freight Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Parking Area Equipment Maintainer	Parking Area Equipment	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Parking Area Equipment Manager	Parking Area Equipment	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Parking Area Equipment Manager	Parking Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Parking Area Equipment Owner	Driver	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Parking Area Equipment Owner	Parking Area Equipment Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Parking Area Equipment Owner	Parking Area Equipment Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Parking Area Equipment Owner	Parking Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Parking Area Equipment Owner	Parking Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Parking Area Equipment Owner	Parking Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Parking Area Equipment Owner	Parking Manager	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Parking Area Equipment Owner	Vehicle Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Parking Area Equipment Owner	Vehicle Owner	Expectation of Information Provision (hide) An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Parking Area Equipment Owner	Vehicle User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Parking Area Equipment Supplier	Parking Area Equipment Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Parking Management Center Maintainer	Parking Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Parking Management Center Manager	Parking Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Parking Management Center Manager	Parking Manager	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Parking Management Center Owner	Parking Area Equipment Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Parking Management Center Owner	Parking Area Equipment Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Parking Management Center Owner	Parking Area Equipment User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Parking Management Center Owner	Parking Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Parking Management Center Owner	Parking Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Parking Management Center Owner	Parking Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Parking Management Center Owner	TIC Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Parking Management Center Owner	Transportation Information Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Parking Management Center Owner	Transportation Information Center Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Parking Management Center Owner	Transportation Information Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Parking Management Center Supplier	Parking Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Parking Manager	Parking Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Parking Operator	Parking Area Equipment	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
TIC Operator	Transportation Information Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Transportation Information Center Maintainer	Transportation Information Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Transportation Information Center Manager	TIC Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Transportation Information Center Manager	Transportation Information Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Transportation Information Center Owner	Fleet and Freight Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Transportation Information Center Owner	Fleet and Freight Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Transportation Information Center Owner	Fleet and Freight Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Transportation Information Center Owner	Fleet-Freight Manager	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Transportation Information Center Owner	Transportation Information Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Transportation Information Center Owner	Transportation Information Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Transportation Information Center Supplier	Transportation Information Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Vehicle Maintainer	Vehicle	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Vehicle Manager	Driver	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Vehicle Manager	Vehicle	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Vehicle Owner	Vehicle Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Vehicle Owner	Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Vehicle Supplier	Vehicle Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

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
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
	TIC Freight-Specific Travel Planning	6.5.11	Provide Interactive Data Interface for Commercial Vehicle and Freight Operations
Vehicle	Vehicle Loading Zone Access	6.7.3.1	Provide Driver with Personal Travel Information
Vehicle	Vehicle Loading Zone Access	6.7.3.2	Provide Driver Information Interface

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.
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 (including motorcycles), 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, occupants, emissions) 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
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, pathway information, 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
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.
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.
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 and characterize their performance (e.g., speed, occupants, emissions).

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective	Performance Measure

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

Related Sources

Document Name	Version	Publication Date
None

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
Parking Area Equipment
Parking Management Center
Transportation Information Center
Vehicle
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
Source	Destination	Information Flow	Basis	Basis	Basis
Driver	Vehicle	driver input	Moderate	High	High
Driver	Vehicle	driver input	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
Fleet and Freight Management Center	Transportation Information Center	commercial vehicle trip information	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
Fleet and Freight Management Center	Transportation Information Center	freight traveler information preferences	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
Parking Area Equipment	Driver	driver parking information	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
Parking Area Equipment	Parking Management Center	loading zone application status	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
Parking Area Equipment	Vehicle	loading zone parking information	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
Parking Management Center	Parking Area Equipment	loading zone application info	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
Parking Management Center	Parking Manager	parking status	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	Transportation Information Center	loading zone information	Low	Moderate	Moderate
Parking Management Center	Transportation Information Center	loading zone information	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 Manager	Parking Management Center	parking manager input	Moderate	High	High
Parking Manager	Parking Management Center	parking manager input	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.
Transportation Information Center	Fleet and Freight Management Center	freight-specific traveler information	Moderate	Moderate	Low
Transportation Information Center	Fleet and Freight Management Center	freight-specific traveler information	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.
Vehicle	Driver	driver updates	Not Applicable	Moderate	Moderate
Vehicle	Driver	driver updates	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 Characteristics	Parking Area Equipment	vehicle characteristics
Vehicle Characteristics	Parking Area Equipment	vehicle characteristics

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. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

System Requirements

No System Requirements