CVO09: Freight-Specific Dynamic Travel Planning
This service package provides both pre-trip and en route travel planning, routing, and commercial vehicle related traveler information, which includes information such as truck parking locations and current status. The information will be based on data collected from the commercial fleet as well as general traffic data collection capabilities. The information, both real time and static can be provided directly to fleet managers, to mobile devices used by commercial vehicle operators, or directly to in vehicle systems as commercial vehicles approach roadway exits with key facilities such as parking. The service package can also provide oversize/ overweight permit information to commercial managers.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
Source | Destination | Role/Relationship |
---|---|---|
Commercial Vehicle Administration Center Maintainer | Commercial Vehicle Administration Center | Maintains |
Commercial Vehicle Administration Center Manager | Commercial Vehicle Administration Center | Manages |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Administration Center Maintainer | System Maintenance Agreement |
Commercial Vehicle Administration Center Owner | Commercial Vehicle Administration Center Manager | Operations Agreement |
Commercial Vehicle Administration Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle Administration Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Commercial Vehicle Administration Center Owner | Transportation Information Center User | Service Usage Agreement |
Commercial Vehicle Administration Center Supplier | Commercial Vehicle Administration Center Owner | Warranty |
Commercial Vehicle OBE Maintainer | Commercial Vehicle OBE | Maintains |
Commercial Vehicle OBE Manager | Commercial Vehicle OBE | Manages |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE Maintainer | System Maintenance Agreement |
Commercial Vehicle OBE Owner | Commercial Vehicle OBE Manager | Operations Agreement |
Commercial Vehicle OBE Owner | Fleet and Freight Management Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle OBE Owner | Fleet and Freight Management Center Owner | Expectation of Data Provision |
Commercial Vehicle OBE Owner | Fleet and Freight Management Center User | Service Usage Agreement |
Commercial Vehicle OBE Owner | Intermodal Customer System Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle OBE Owner | Intermodal Customer System Owner | Expectation of Data Provision |
Commercial Vehicle OBE Owner | Intermodal Customer System User | Service Usage Agreement |
Commercial Vehicle OBE Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Commercial Vehicle OBE Owner | Transportation Information Center Owner | Expectation of Data Provision |
Commercial Vehicle OBE Owner | Transportation Information Center User | Service Usage Agreement |
Commercial Vehicle OBE Supplier | Commercial Vehicle OBE Owner | Warranty |
Emergency Management Center Maintainer | Emergency Management Center | Maintains |
Emergency Management Center Manager | Emergency Management Center | Manages |
Emergency Management Center Owner | Emergency Management Center Maintainer | System Maintenance Agreement |
Emergency Management Center Owner | Emergency Management Center Manager | Operations Agreement |
Emergency Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Emergency Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Emergency Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Emergency Management Center Supplier | Emergency Management Center Owner | Warranty |
Financial Center Maintainer | Financial Center | Maintains |
Financial Center Manager | Financial Center | Manages |
Financial Center Owner | Financial Center Maintainer | System Maintenance Agreement |
Financial Center Owner | Financial Center Manager | Operations Agreement |
Financial Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Financial Center Owner | Transportation Information Center Owner | Information Exchange Agreement |
Financial Center Owner | Transportation Information Center User | Service Usage Agreement |
Financial Center Supplier | Financial Center Owner | Warranty |
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 | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE Owner | Information Provision Agreement |
Fleet and Freight Management Center Owner | Commercial Vehicle OBE User | Service Usage Agreement |
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 | Freight Consolidation Station Maintainer | Maintenance Data Exchange Agreement |
Fleet and Freight Management Center Owner | Freight Consolidation Station Owner | Information Provision Agreement |
Fleet and Freight Management Center Owner | Freight Consolidation Station User | Service Usage Agreement |
Fleet and Freight Management Center Owner | Freight Distribution and Logistics Center Maintainer | Maintenance Data Exchange Agreement |
Fleet and Freight Management Center Owner | Freight Distribution and Logistics Center Owner | Information Provision Agreement |
Fleet and Freight Management Center Owner | Freight Distribution and Logistics Center User | Service Usage Agreement |
Fleet and Freight Management Center Owner | Intermodal Customer System Maintainer | Maintenance Data Exchange Agreement |
Fleet and Freight Management Center Owner | Intermodal Customer System Owner | Information Exchange Agreement |
Fleet and Freight Management Center Owner | Intermodal Customer System User | Service Usage Agreement |
Fleet and Freight Management Center Owner | Intermodal Terminal Maintainer | Maintenance Data Exchange Agreement |
Fleet and Freight Management Center Owner | Intermodal Terminal Owner | Information Provision Agreement |
Fleet and Freight Management Center Owner | Intermodal Terminal User | Service Usage 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 |
Freight Consolidation Station Maintainer | Freight Consolidation Station | Maintains |
Freight Consolidation Station Manager | Freight Consolidation Station | Manages |
Freight Consolidation Station Owner | Fleet and Freight Management Center Maintainer | Maintenance Data Exchange Agreement |
Freight Consolidation Station Owner | Fleet and Freight Management Center Owner | Information Exchange and Action Agreement |
Freight Consolidation Station Owner | Fleet and Freight Management Center User | Service Usage Agreement |
Freight Consolidation Station Owner | Freight Consolidation Station Maintainer | System Maintenance Agreement |
Freight Consolidation Station Owner | Freight Consolidation Station Manager | Operations Agreement |
Freight Consolidation Station Supplier | Freight Consolidation Station Owner | Warranty |
Freight Distribution and Logistics Center Maintainer | Freight Distribution and Logistics Center | Maintains |
Freight Distribution and Logistics Center Manager | Freight Distribution and Logistics Center | Manages |
Freight Distribution and Logistics Center Owner | Freight Distribution and Logistics Center Maintainer | System Maintenance Agreement |
Freight Distribution and Logistics Center Owner | Freight Distribution and Logistics Center Manager | Operations Agreement |
Freight Distribution and Logistics Center Owner | Intermodal Terminal Maintainer | Maintenance Data Exchange Agreement |
Freight Distribution and Logistics Center Owner | Intermodal Terminal Owner | Information Provision Agreement |
Freight Distribution and Logistics Center Owner | Intermodal Terminal User | Service Usage Agreement |
Freight Distribution and Logistics Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Freight Distribution and Logistics Center Owner | Transportation Information Center Owner | Information Exchange Agreement |
Freight Distribution and Logistics Center Owner | Transportation Information Center User | Service Usage Agreement |
Freight Distribution and Logistics Center Supplier | Freight Distribution and Logistics Center Owner | Warranty |
Intermodal Customer System Maintainer | Intermodal Customer System | Maintains |
Intermodal Customer System Manager | Intermodal Customer System | Manages |
Intermodal Customer System Owner | Fleet and Freight Management Center Maintainer | Maintenance Data Exchange Agreement |
Intermodal Customer System Owner | Fleet and Freight Management Center Owner | Information Exchange Agreement |
Intermodal Customer System Owner | Fleet and Freight Management Center User | Service Usage Agreement |
Intermodal Customer System Owner | Intermodal Customer System Maintainer | System Maintenance Agreement |
Intermodal Customer System Owner | Intermodal Customer System Manager | Operations Agreement |
Intermodal Customer System Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Intermodal Customer System Owner | Transportation Information Center Owner | Information Exchange Agreement |
Intermodal Customer System Owner | Transportation Information Center User | Service Usage Agreement |
Intermodal Customer System Supplier | Intermodal Customer System Owner | Warranty |
Intermodal Terminal Maintainer | Intermodal Terminal | Maintains |
Intermodal Terminal Manager | Intermodal Terminal | Manages |
Intermodal Terminal Owner | Fleet and Freight Management Center Maintainer | Maintenance Data Exchange Agreement |
Intermodal Terminal Owner | Fleet and Freight Management Center Owner | Information Exchange and Action Agreement |
Intermodal Terminal Owner | Fleet and Freight Management Center User | Service Usage Agreement |
Intermodal Terminal Owner | Intermodal Terminal Maintainer | System Maintenance Agreement |
Intermodal Terminal Owner | Intermodal Terminal Manager | Operations Agreement |
Intermodal Terminal Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Intermodal Terminal Owner | Transportation Information Center Owner | Information Exchange and Action Agreement |
Intermodal Terminal Owner | Transportation Information Center User | Service Usage Agreement |
Intermodal Terminal Supplier | Intermodal Terminal Owner | Warranty |
Maint and Constr Management Center Maintainer | Maint and Constr Management Center | Maintains |
Maint and Constr Management Center Manager | Maint and Constr Management Center | Manages |
Maint and Constr Management Center Owner | Maint and Constr Management Center Maintainer | System Maintenance Agreement |
Maint and Constr Management Center Owner | Maint and Constr Management Center Manager | Operations Agreement |
Maint and Constr Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Maint and Constr Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Maint and Constr Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Maint and Constr Management Center Supplier | Maint and Constr Management Center Owner | Warranty |
Other Transportation Information Centers Maintainer | Other Transportation Information Centers | Maintains |
Other Transportation Information Centers Manager | Other Transportation Information Centers | Manages |
Other Transportation Information Centers Owner | Other Transportation Information Centers Maintainer | System Maintenance Agreement |
Other Transportation Information Centers Owner | Other Transportation Information Centers Manager | Operations Agreement |
Other Transportation Information Centers Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Other Transportation Information Centers Owner | Transportation Information Center Owner | Information Exchange Agreement |
Other Transportation Information Centers Owner | Transportation Information Center User | Service Usage Agreement |
Other Transportation Information Centers Supplier | Other Transportation Information Centers Owner | Warranty |
Parking Management Center Maintainer | Parking Management Center | Maintains |
Parking Management Center Manager | Parking Management Center | Manages |
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 | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Parking Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Parking Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Parking Management Center Supplier | Parking Management Center Owner | Warranty |
Payment Administration Center Maintainer | Payment Administration Center | Maintains |
Payment Administration Center Manager | Payment Administration Center | Manages |
Payment Administration Center Owner | Payment Administration Center Maintainer | System Maintenance Agreement |
Payment Administration Center Owner | Payment Administration Center Manager | Operations Agreement |
Payment Administration Center Supplier | Payment Administration Center Owner | Warranty |
Personal Information Device Maintainer | Personal Information Device | Maintains |
Personal Information Device Manager | Personal Information Device | Manages |
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 |
Traffic Management Center Maintainer | Traffic Management Center | Maintains |
Traffic Management Center Manager | Traffic Management Center | Manages |
Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
Traffic Management Center Owner | Traffic Management Center Manager | Operations Agreement |
Traffic Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Traffic Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Traffic Management Center Supplier | Traffic Management Center Owner | Warranty |
Transportation Information Center Maintainer | Transportation Information Center | Maintains |
Transportation Information Center Manager | Transportation Information Center | Manages |
Transportation Information Center Owner | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Commercial Vehicle OBE Owner | Information Provision Agreement |
Transportation Information Center Owner | Commercial Vehicle OBE User | Service Usage Agreement |
Transportation Information Center Owner | Financial Center Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Financial Center Owner | Information Exchange Agreement |
Transportation Information Center Owner | Financial Center User | Service Usage Agreement |
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 | Freight Distribution and Logistics Center Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Freight Distribution and Logistics Center Owner | Information Exchange Agreement |
Transportation Information Center Owner | Freight Distribution and Logistics Center User | Service Usage Agreement |
Transportation Information Center Owner | Intermodal Customer System Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Intermodal Customer System Owner | Information Exchange Agreement |
Transportation Information Center Owner | Intermodal Customer System User | Service Usage Agreement |
Transportation Information Center Owner | Other Transportation Information Centers Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Other Transportation Information Centers Owner | Information Exchange Agreement |
Transportation Information Center Owner | Other Transportation Information Centers User | Service Usage Agreement |
Transportation Information Center Owner | Payment Administration Center Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Payment Administration Center Owner | Information Provision Agreement |
Transportation Information Center Owner | Payment Administration Center User | Service 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 |
Weather Service System Maintainer | Weather Service System | Maintains |
Weather Service System Manager | Weather Service System | Manages |
Weather Service System Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Weather Service System Owner | Transportation Information Center Owner | Information Provision Agreement |
Weather Service System Owner | Transportation Information Center User | Service Usage Agreement |
Weather Service System Owner | Weather Service System Maintainer | System Maintenance Agreement |
Weather Service System Owner | Weather Service System Manager | Operations Agreement |
Weather Service System Supplier | Weather Service System Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
Commercial Vehicle Administration Center | Center | The 'Commercial Vehicle Administration Center' performs administrative functions supporting credentials, tax, and safety regulations associated with commercial vehicles. It issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It communicates with motor carriers to process credentials applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with cognizant authorities. It coordinates with other Commercial Vehicle Administration Centers (in other states/regions) to support nationwide access to credentials and safety information for administration and enforcement functions. It communicates with field equipment to enable credential checking and safety information collection at the roadside. It makes safety information available to qualified stakeholders to identify carriers and drivers that operate unsafely. |
Commercial Vehicle OBE | Vehicle | The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. A separate 'Vehicle OBE' physical object supports vehicle safety and driver information capabilities that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general ITS capabilities with capabilities that are specific to commercial vehicles. |
Emergency Management Center | Center | The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency. |
Financial Center | Center | The 'Financial Center' represents the organization that handles electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are covered by this physical object. |
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. |
Freight Consolidation Station | Field | The 'Freight Consolidation Station' is an intermediate point (usually an intermodal terminal located at a port) prior to (or after) container-based shipping, where less-than-container load or less-than-truckload cargoes are consolidated into full container loads (or full containers are disbursed), for cost-effective intermodal shipping. |
Freight Distribution and Logistics Center | Center | The 'Freight Distribution and Logistics Center' provides intermodal logistics support and support for the efficient distribution of freight across transport systems and modes. This can include consolidation arrangements, warehousing, and consignor-to-consignee intermodal shipping arrangements. These capabilities may be provided as part of intermodal fleet management activities or can be provided by an independent logistics specialist. |
Intermodal Customer System | Center | The 'Intermodal Customer System' represents organizations that engage in the shipment of freight, either originator (consigner or shipper) or recipient of the cargo shipment. They enable the movement of goods on routes that require the use of other modes of transportation such as heavy rail, air, sea, etc. The Intermodal Customer System includes those personnel responsible for the movement of freight across international borders. |
Intermodal Terminal | Field | The 'Intermodal Terminal' represents the terminal areas corresponding to modal change points. This includes interfaces between roadway freight transportation and air, rail, and/or water shipping modes. The basic unit of cargo handled by the Intermodal Terminal physical object is the container; less-than-container load handling is typically handled at a different facility (i.e., Freight Consolidation Station). The Intermodal Terminal can include electronic gate control for entrance and exit from the facility, automated guidance of vehicles within the facility, alerting appropriate parties of container arrivals and departures, and inventory and location of temporarily stored containers. |
Maint and Constr Management Center | Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
Other Transportation Information Centers | Center | Representing another Transportation Information Center, this object is intended to provide a source and destination for ITS information flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant. |
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. |
Payment Administration Center | Center | The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center. |
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. |
Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
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. |
Weather Service System | Center | The 'Weather Service System' provides weather, hydrologic, and climate information and warnings of hazardous weather including thunderstorms, flooding, hurricanes, tornadoes, winter weather, tsunamis, and climate events. It provides atmospheric weather observations and forecasts that are collected and derived by the National Weather Service, private sector providers, and various research organizations. The interface provides formatted weather data products suitable for on-line processing and integration with other ITS data products as well as Doppler radar images, satellite images, severe storm warnings, and other products that are formatted for presentation to various ITS users. |
Includes Functional Objects:
Functional Object | Description | Physical Object |
---|---|---|
CV On-Board Trip Monitoring | 'CV On-Board Trip Monitoring' provides the capabilities to support fleet management with automatic vehicle location and automated mileage and fuel reporting and auditing. In addition, this equipment is used to monitor the planned route and notify the Fleet and Freight Management Center of any deviations. | Commercial Vehicle OBE |
CVAC Credentials and Taxes Administration | 'CVAC Credentials and Taxes Administration' issues credentials, collects fees and taxes, and supports enforcement of credential requirements. It manages driver licensing and enrolls carriers in additional CVO programs such as wireless roadside inspection programs. It communicates with the Fleet and Freight Management Centers associated with the motor carriers to process applications and collect fuel taxes, weight/distance taxes, and other taxes and fees associated with commercial vehicle operations. It also receives applications for, and issues special Oversize/Overweight and HAZMAT permits in coordination with other cognizant authorities. It supports user account management and receives and processes requests for review of carrier and driver status. It communicates with peer functional objects in other jurisdictions to exchange credentials database information. | Commercial Vehicle Administration Center |
FDLC Freight Services | 'FDLC Freight Services" provides the core freight distribution and logistics center functionality, including management and coordination of intermodal shipping arrangements, including load consolidation and warehousing services. | Freight Distribution and Logistics Center |
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 |
Freight Administration and Management | 'Freight Administration and Management' manages the movement of freight from source to destination. It interfaces to intermodal customers to setup and schedule transportation and coordinates with intermodal terminals and freight consolidation stations to coordinate the shipment. It coordinates with the appropriate government agencies to expedite the movement of trucks, their drivers, and their cargo across international borders. The application monitors the status of the freight and freight equipment (container, trailer, or chassis) and monitors freight location and compares it against the planned route. | Fleet and Freight Management Center |
Personal Trip Planning and Route Guidance | 'Personal Trip Planning and Route Guidance' provides a personalized trip plan to the traveler. The trip plan is calculated based on preferences and constraints supplied by the traveler and provided to the traveler for confirmation. Coordination may continue during the trip so that the route plan can be modified to account for new information. Many equipment configurations are possible including systems that provide a basic trip plan to the traveler as well as more sophisticated systems that can provide transition by transition guidance to the traveler along a multi-modal route with transfers. Devices represented by this functional object include desktop computers at home, work, or at major trip generation sites, plus personal devices such as tablets and smart phones. | Personal Information Device |
Terminal Management | 'Terminal Management' supports the operation of the roadway aspects of an intermodal terminal. The key capabilities include the ability to identify and control vehicle traffic entering and departing the facility, guide vehicles to loading and unloading points, maintain site security and monitor container integrity, provide an interface to Customs as appropriate, and acknowledge container pickup and drop-off. Other capabilities include the ability to track container locations within the facility, manage any other required assets, like truck chassis, and provide reservation services to manage congestion at busy terminals. This application also provides information to support load matching services for drayage operators. | Intermodal Terminal |
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 Interactive Traveler Information | 'TIC Interactive Traveler Information' disseminates personalized traveler information including traffic and road conditions, transit information, parking information, maintenance and construction information, multimodal information, event information, and weather information. Tailored information is provided based on the traveler's request in this interactive service. | Transportation Information Center |
Includes Information Flows:
Information Flow | Description |
---|---|
account updates | Updates to an account, such as purchases, uses, cancellation, secureID changes or similar material changes to account information. |
booking status | Status of the freight transport booking that includes the identities of the Commercial Vehicle and driver who will pick-up the freight or a request for more information from the originator. This includes proposed transport booking changes including departure/arrival changes, conveyance changes. |
commercial vehicle permit information | Information for commercial vehicle permits for oversize, overweight, or for dangerous goods. The query flow is not explicitly shown. |
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. |
container pickup confirmation | Notice confirming that a container has been picked up at an intermodal facility and that control has been transferred to a shipping or drayage agency. |
container pickup request | Request for permission to pickup a container at an intermodal transfer facility. |
driver to fleet request | Requests from the driver and vehicle for routing, payment, and enrollment information. |
fleet to driver update | Updated instructions to the driver including dispatch, routing, travel and parking information, and special instructions. Special instructions include incident management instruction, operational tasks, impacted transport orders in case of an incident, task descriptions with trip/route/load plan, transport order status information, driver information, vehicle information, cargo information and trip information. |
freight delivery status | A time-stamped status of a freight shipment provided directly by a commercial vehicle to a customer. This includes freight transaction ID (principal order ID and freight operator proposal ID), cargo status ID, current operation (pick-up, conveying, delivering), position, expected time of arrival, with or without incident and incident description. |
freight transport booking | Booking information for the transport of freight that includes company, contact information, point of origin, pick-up location, drop-off location, and freight equipment identifier. |
freight transportation status | A time-stamped status of a freight shipment as it passes through the supply chain from manufacturer through arrival at its final destination; including cargo movement logs, routing information, and cargo ID's. This includes cargo status, current operation, information on incidents associated with the cargo, and identification of delays/penalties. |
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. |
incident information for public | Report of current desensitized incident information prepared for public dissemination. |
intermodal terminal status | Current status of the intermodal terminal including the current queue length/delay, current access requirements and restrictions (e.g., access restricted to appointments only). |
maint and constr work plans | Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations. |
parking information | General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots. |
payment request | Request for payment from financial institution or related financial service requests (e.g., balance inquiry) |
road network conditions | Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included. |
roadway maintenance status | Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status). |
route restrictions | Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits). |
settlement | Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges. |
traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. |
traffic images | High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. |
weather information | Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.). |
work zone information | Summary of maintenance and construction work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts. |
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 |
J. Enhance travel and tourism. | Support travel and tourism |
Associated Objective Categories
Objective Category |
---|
Freight Management: Detours and Routing |
Traveler Information: Customer Satisfaction |
Traveler Information: Information Dissemination |
Traveler Information: Trip Planning Tools |
Associated Objectives and Performance Measures
Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. | CVAC Credentials and Taxes Administration | 05 | The center shall provide route restrictions information, including hazmat restrictions, to other centers and agencies for distribution to commercial vehicle operators. These centers and agencies may include commercial fleet and freight management operators, traveler information centers, digital map update providers, and other commercial vehicle administration centers. |
FDLC Freight Services | 02 | The center shall collect freight shipment status including cargo movement logs, routing information, cargo ID's, current operation, information on incidents associated with the cargo, and identification of delays/penalties. | ||
04 | The center shall receive specific traveler information customized for freight users. | |||
Freight Administration and Management | 02 | The center shall provide the interface with intermodal freight shippers to setup transportation for freight equipment. Inputs to this include information about the shipper, consignee, commodities, pick-up and drop-off locations for freight equipment. Outputs include information about the driver and commercial vehicle that will be transporting the freight. | ||
12 | The center shall provide traveler information center information about vehicle trips including load information, location, speed, and routing. | |||
14 | The center shall provide traveler information centers with fleet-specific traveler information preferences including area covered by fleet/driver, types of freight managed (including special restrictions), preferred routes, and other travel preferences pertaining to trip costs or tolls. | |||
Terminal Management | 02 | The facility shall provide status of a freight shipment; including cargo movement logs, routing information, and cargo ID's. | ||
03 | The facility shall provide transportation information centers with the status of the intermodal terminal including the current queue length/delay, current access requirements and restrictions (e.g., access restricted to appointments only). | |||
02 | Traveler Information needs to provide fleet and freight management with incident and road condition information to drivers and dispatchers so they can make route planning and navigation decisions internally in keeping with prevailing business practices in the industry. | 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. |
TIC Data Collection | 16 | The center shall collect road condition information for freeways, arterials, and secondary roads that are used as freight routes. | ||
TIC Freight-Specific Travel Planning | 02 | The center shall indicate the area covered by the freight traveler information service. | ||
03 | The center shall provide an interface to allow operators to identify roadway links as part of a key freight route. | |||
04 | The center shall provide traveler information for freight routes from source to destination, customized for freight users to indicate truck routes, truck stops, inspection stations, steep grades, etc. | |||
03 | Traveler Information needs to provide freight-specific routing, travel timing, and scheduling for logistics intermediaries so they have a complete data packet for informed decision making. | CV On-Board Trip Monitoring | 08 | The commercial vehicle shall receive customized traveler information from traveler information centers 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. |
Freight Administration and Management | 13 | The center shall receive customized traveler information for freight users from traveler information center 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. | ||
Personal Trip Planning and Route Guidance | 05 | The personal traveler interface shall provide the capability for a traveler to request and receive freight specific traveler information including 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. | ||
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. | ||
05 | The center shall collect metadata for road conditions information that includes the date and time when the information was generated. | |||
06 | The center shall indicate when collected data is older than a prescribed threshold with respect to a current operation. | |||
04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. | CV On-Board Trip Monitoring | 08 | The commercial vehicle shall receive customized traveler information from traveler information centers 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. |
Fleet Administration | 09 | The center shall send data to its commercial vehicles including dispatch, routing, trigger areas, and special instructions, including alerts and other advisories. | ||
TIC Data Collection | 01 | The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. | ||
03 | The center shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities. | |||
05 | The center shall collect, process, and store parking information, including location, availability, and fees. | |||
07 | The center shall collect, process, and store current and forecast road conditions and surface weather conditions. | |||
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. | ||
TIC Interactive Traveler Information | 18 | The center shall support requests for traveler information and advanced payment for traveler services from commercial fleet operators. | ||
19 | The center shall disseminate customized freight information to travelers, including truck routes, permit information, truck stops, inspection stations, steep grades, high-profile vehicle advisories. Information provided includes freight-related road and weather conditions, parking information, and route plans. |
Related Sources
Document Name | Version | Publication Date |
---|---|---|
FRATIS Los Angeles Gateway Project- Final System Design and Architecture for FRATIS Prototype | Final | 5/23/2014 |
Freight Advanced Traveler Information System (FRATIS) - Dallas-Fort Worth Software Architecture Design and Implementation Options | Final | 5/6/2013 |
Freight Advanced Traveler Information System (FRATIS) ConOps | Final | 4/20/2012 |
Freight Advanced Traveler Information System (FRATIS) Demonstration Plan | Draft | 6/10/2013 |
Freight Advanced Traveler Information System Functional Requirements | Final | 5/12/2012 |
South Florida Freight Advanced Traveler Information System Architecture and Implementation Options Summary Report | Final | 7/19/2013 |
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
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 | |||
Commercial Vehicle Administration Center | Transportation Information Center | commercial vehicle permit information | Moderate | Moderate | Moderate |
Indicates company and individual vehicle permitting information, which is competitive commercial data. Observation of this information could provide leverage or business advantage over a particular carrier. | If incorrect a vehicle or carrier may be misled about what permits it has or needs, resulting in a potential for being improperly permitted and penalized. MODERATE and not HIGH because the impact is likely to be limited and can likely be easily addressed. | If this flow is inconsistently available there is probably little harm. It may be required for real-time CVO checking action, but the effect will apply to only one or at most, a limited number of drivers at a given location. | |||
Commercial Vehicle Administration Center | Transportation Information Center | route restrictions | Low | Moderate | Low |
Should be public data, so no need for obfuscation. | Incorrect route restrictions data will not affect the TIC but will affect the eventual user, and may result in a commercial vehicle being in a place the vehicle is not permitted. | This information should not need to be updated often. | |||
Commercial Vehicle OBE | Fleet and Freight Management Center | driver to fleet request | High | Moderate | Moderate |
Contains trip and payment details that if disclosed would compromise the driver, load and carrier. | Payment details need to be correct or the vehicle may be delayed. Likely limited in scope to individual vehicles that suffer corrupted messages. | If this flow is not available the commercial vehicle in question will be delayed and/or misrouted, which will inconvenience that vehicle, costing time and money. | |||
Commercial Vehicle OBE | Intermodal Customer System | freight delivery status | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Commercial Vehicle OBE | 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 | |||
Emergency Management Center | Transportation Information Center | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. | A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TIC has received a message. | |||
Financial Center | Transportation Information Center | settlement | Moderate | Moderate | Moderate |
This may include PII and will include status information about a payment that could be used by a criminal for a variety of purposes, including identity theft, financial theft, or location-based activities, as the status is predictivie of what the account holder is doing and where they are doing it. | Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. | Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. | |||
Fleet and Freight Management Center | Commercial Vehicle OBE | fleet to driver update | High | Moderate | Moderate |
Contains PII, routing instructions and tasking, predictive of vehicle future, all of which if compromised would provide leverage over vehicle, driver and owner. | Contains a lot of information dedicated to the individual vehicle, any of which if incorrect or corrupted would negatively affect the vehicle and driver. | There is a great deal of informatino in this flow that would be challenging to assemble through other sources. A delay in receiving this information would negatively affect the vehicle and driver. | |||
Fleet and Freight Management Center | Freight Consolidation Station | container pickup confirmation | Moderate | Moderate | Moderate |
Container status information may be competitive but certainly is trackable data, and needs to be obfuscated to avoid such tracking or business-related espionage. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | |||
Fleet and Freight Management Center | Freight Distribution and Logistics Center | freight transportation status | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Fleet and Freight Management Center | Intermodal Customer System | booking status | Moderate | Moderate | Moderate |
Business and personal information included, which if disclosed would compromise the carrier whose information was affected, providing leverage over them to the 3rd party that acquired the information. | If this information is incorrect or corrupted freight trips may be delayed, which will cost time and money. | If this information is unavailable freight trips may be delayed, which will cost time and money. | |||
Fleet and Freight Management Center | Intermodal Customer System | freight transportation status | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Fleet and Freight Management Center | Intermodal Terminal | container pickup confirmation | Moderate | Moderate | Moderate |
Container status information may be competitive but certainly is trackable data, and needs to be obfuscated to avoid such tracking or business-related espionage. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | |||
Fleet and Freight Management Center | Intermodal Terminal | freight transportation status | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
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 | |||
Freight Consolidation Station | Fleet and Freight Management Center | container pickup request | Moderate | Moderate | Moderate |
Container status information may be competitive but certainly is trackable data, and needs to be obfuscated to avoid such tracking or business-related espionage. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | |||
Freight Distribution and Logistics Center | Intermodal Terminal | freight transportation status | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Freight Distribution and Logistics Center | Transportation Information Center | freight traveler information preferences | Moderate | Moderate | Low |
Includes identity of the freight traveler, which should be protected as it is 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. | |||
Intermodal Customer System | Fleet and Freight Management Center | freight transport booking | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Intermodal Customer System | Fleet and Freight Management Center | freight transportation status | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Intermodal Customer System | Transportation Information Center | freight traveler information preferences | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Intermodal Terminal | Fleet and Freight Management Center | container pickup request | Moderate | Moderate | Moderate |
Container status information may be competitive but certainly is trackable data, and needs to be obfuscated to avoid such tracking or business-related espionage. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | Container status information should be correct in real-time, or pickup, delivery and related activities will be confused and slowed, creating supply chain issues and mobility problems. | |||
Intermodal Terminal | Fleet and Freight Management Center | freight transportation status | Moderate | Moderate | Moderate |
Contains company information including load delivery specifics. While possibly not competitive, could be considered 'need-to-know', as anyone not providing transport services could have minimal legitimate use for this information. Possible abuses could leverage arrival and delivery information or transport operator locations. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | CVO decisions including job acceptance, routing and work planning are impacted by the quality of this data, so incorrect, unavailable or fraudulent data could have a significant financial impact. | |||
Intermodal Terminal | Transportation Information Center | intermodal terminal status | Low | Moderate | Moderate |
Information describing congestion at the terminal could be directly observed, and is also distributed via a TIC, and so observation of this flow is unlikely to have any serious effect. | Data needs to be correct as commercial operators will use this in decision making, and incorrect data may lead to financial impact. | If data is not available at the TIC, it may be available at other sources receiving the same flow (FFMC for example. While one instance of this flow could be LOW, between all they should be MODERATE. Establishing at MODERATE because it is likely that only one instance of the flow is created in any given region. | |||
Maint and Constr Management Center | Transportation Information Center | maint and constr work plans | Low | High | High |
This data is eventually intended for public dissemination, and is also shared with many centers. | If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to work zone impacts, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway). | If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to work zone impacts, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway). | |||
Maint and Constr Management Center | Transportation Information Center | roadway maintenance status | Low | Moderate | Moderate |
Roadway maintenance status data is distributed to a host of places including travelers, so there is no justification for obfuscation. | Road maintenance data is generally distributed to travelers through a TIC, so this needs to be accurate and available so that travelers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. | Road maintenance data is generally distributed to travelers through a TIC, so this needs to be accurate and available so that travelers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. | |||
Maint and Constr Management Center | Transportation Information Center | work zone information | Low | Moderate | Moderate |
Eventually intended for public distribution, so no need to obfuscate. | Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc.; DISC: WYO believes this to be HIGH. | Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc. | |||
Other Transportation Information Centers | Transportation Information Center | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. | Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. | |||
Other Transportation Information Centers | Transportation Information Center | parking information | Moderate | Moderate | Moderate |
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise. | |||
Other Transportation Information Centers | Transportation Information Center | road network conditions | Low | Moderate | Moderate |
No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW. | |||
Other Transportation Information Centers | Transportation Information Center | traffic image meta data | Low | Moderate | Moderate |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
Other Transportation Information Centers | Transportation Information Center | traffic images | Low | Moderate | Low |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Parking Management Center | Transportation Information Center | parking information | Moderate | Moderate | Moderate |
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise. | |||
Personal Information Device | 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 | |||
Traffic Management Center | Transportation Information Center | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Incident information will be used to make routing and other travel decisions. Corrupted information may have a significant impac t on travel plans and/or road network conditions. | Significant numbers of travelers serve as end users for the information in this flow; lack of availability has a significant effect on their travel decisions. | |||
Traffic Management Center | Transportation Information Center | road network conditions | Low | Moderate | Moderate |
No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW. | |||
Transportation Information Center | Commercial Vehicle OBE | 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 | Financial Center | payment request | Moderate | Moderate | Moderate |
Contains account and related information that is personal and if compromised could financially impact the owner of the account. | Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. | Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. | |||
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 | Freight Distribution and Logistics 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 | Intermodal Customer System | 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 | Other Transportation Information Centers | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. | Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. | |||
Transportation Information Center | Other Transportation Information Centers | parking information | Moderate | Moderate | Moderate |
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Transportation Information Center | Other Transportation Information Centers | road network conditions | Low | Moderate | Moderate |
No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | condition info should be timely and readily available so that TMCs are aware of current traffic info, conditions, restrictions, etc. but should not have severe/catastrophic consequences if not | |||
Transportation Information Center | Other Transportation Information Centers | traffic image meta data | Low | Moderate | Moderate |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
Transportation Information Center | Other Transportation Information Centers | traffic images | Low | Moderate | Low |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Transportation Information Center | Payment Administration Center | account updates | Moderate | Moderate | Moderate |
Contains an identifier that can be linked to an account which is in turn likely linked to a person, and thus PII that should be protected. | Payment charge and similar information should be correct or it could lead to abuse or incorrect charges. Impact limited to individual accounts however. | These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection. | |||
Transportation Information Center | Personal Information Device | 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. | |||
Weather Service System | Transportation Information Center | weather information | Low | Moderate | Moderate |
WYO believes this should be LOW or MODERATE depending on the application. | While there are many sources of weather information, some guarantee of correctness is justifiable to keep confidence in provided service. | There should be other sources of this data. It does need to be reliable however; weather can change quickly, and depending on the destination and its operational strategies, timely response may be important. |
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 provide route restrictions information, including hazmat restrictions, to other centers and agencies for distribution to commercial vehicle operators. These centers and agencies may include commercial fleet and freight management operators, traveler information centers, digital map update providers, and other commercial vehicle administration centers. | 01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. |
002 | The system shall collect freight shipment status including cargo movement logs, routing information, cargo ID's, current operation, information on incidents associated with the cargo, and identification of delays/penalties. | 01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. |
003 | The system shall receive specific traveler information customized for freight users. | 01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. |
004 | 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 information provided by traveler information systems. | 02 | Traveler Information needs to provide fleet and freight management with incident and road condition information to drivers and dispatchers so they can make route planning and navigation decisions internally in keeping with prevailing business practices in the industry. |
005 | The system shall send data to its commercial vehicles including dispatch, routing, trigger areas, and special instructions, including alerts and other advisories. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
006 | The system shall provide the interface with intermodal freight shippers to setup transportation for freight equipment. Inputs to this include information about the shipper, consignee, commodities, pick-up and drop-off locations for freight equipment. Outputs include information about the driver and commercial vehicle that will be transporting the freight. | 01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. |
007 | The system shall provide traveler information center information about vehicle trips including load information, location, speed, and routing. | 01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. |
008 | The system shall receive customized traveler information for freight users from traveler information center 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. | 03 | Traveler Information needs to provide freight-specific routing, travel timing, and scheduling for logistics intermediaries so they have a complete data packet for informed decision making. |
009 | The system shall provide traveler information centers with fleet-specific traveler information preferences including area covered by fleet/driver, types of freight managed (including special restrictions), preferred routes, and other travel preferences pertaining to trip costs or tolls. | 01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. |
010 | The system shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
011 | The system shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
012 | The system shall collect, process, and store parking information, including location, availability, and fees. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
013 | The system shall collect, process, and store current and forecast road conditions and surface weather conditions. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
014 | The system shall collect, process, and store freight specific traveler information. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
015 | The system shall collect road condition information for freeways, arterials, and secondary roads that are used as freight routes. | 02 | Traveler Information needs to provide fleet and freight management with incident and road condition information to drivers and dispatchers so they can make route planning and navigation decisions internally in keeping with prevailing business practices in the industry. |
016 | 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 road and weather conditions, parking information, and route plans. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
03 | Traveler Information needs to provide freight-specific routing, travel timing, and scheduling for logistics intermediaries so they have a complete data packet for informed decision making. | ||
017 | The system shall indicate the area covered by the freight traveler information service. | 02 | Traveler Information needs to provide fleet and freight management with incident and road condition information to drivers and dispatchers so they can make route planning and navigation decisions internally in keeping with prevailing business practices in the industry. |
018 | The system shall provide an interface to allow operators to identify roadway links as part of a key freight route. | 02 | Traveler Information needs to provide fleet and freight management with incident and road condition information to drivers and dispatchers so they can make route planning and navigation decisions internally in keeping with prevailing business practices in the industry. |
019 | The system shall provide traveler information for freight routes from source to destination, customized for freight users to indicate truck routes, truck stops, inspection stations, steep grades, etc. | 02 | Traveler Information needs to provide fleet and freight management with incident and road condition information to drivers and dispatchers so they can make route planning and navigation decisions internally in keeping with prevailing business practices in the industry. |
020 | The system shall collect metadata for road conditions information that includes the date and time when the information was generated. | 03 | Traveler Information needs to provide freight-specific routing, travel timing, and scheduling for logistics intermediaries so they have a complete data packet for informed decision making. |
021 | The system shall indicate when collected data is older than a prescribed threshold with respect to a current operation. | 03 | Traveler Information needs to provide freight-specific routing, travel timing, and scheduling for logistics intermediaries so they have a complete data packet for informed decision making. |
022 | The system shall support requests for traveler information and advanced payment for traveler services from commercial fleet operators. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
023 | The system shall disseminate customized freight information to travelers, including truck routes, permit information, truck stops, inspection stations, steep grades, high-profile vehicle advisories. Information provided includes freight-related road and weather conditions, parking information, and route plans. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
024 | The system shall provide status of a freight shipment; including cargo movement logs, routing information, and cargo ID's. | 01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. |
025 | The system shall provide transportation information centers with the status of the intermodal terminal including the current queue length/delay, current access requirements and restrictions (e.g., access restricted to appointments only). | 01 | Commercial Vehicle Fleet and Freight Management, including logistics suppliers need access to traveler information that covers the supply chain (from marine/rail terminal, to warehouse, to customers), so their dispatchers and managers can adequately plan and manage their assets. |
026 | The system shall provide the capability for a traveler to request and receive freight specific traveler information including 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. | 03 | Traveler Information needs to provide freight-specific routing, travel timing, and scheduling for logistics intermediaries so they have a complete data packet for informed decision making. |
027 | The system shall receive customized traveler information from traveler information centers 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. | 04 | Traveler Information needs to provide real-time information about required permits, locations and availability of truck rest areas or parking to drivers and dispatchers to improve routing, vehicle and driver safety, and compliance with hours of service rules. |
03 | Traveler Information needs to provide freight-specific routing, travel timing, and scheduling for logistics intermediaries so they have a complete data packet for informed decision making. |