Type: Mobility
Groups:- Freight Advanced Traveler Information Systems
Freight Drayage Optimization
The Freight Drayage Optimization application covers the information exchanges between all intermodal parties to provide current drayage truck load matching and container availability and appointment scheduling at railroad and steamship line terminals. The application includes a link from drivers and freight management systems dispatchers to an intermodal terminal reservation system and integrates an appointment function with Terminal Queue Status and Load Matching. The application set provides information to the dispatcher and driver concerning the availability status for pickup of a container at an intermodal terminal. The application bundle also provides drivers and dispatchers with both intermodal terminal queue length, and estimated time from the back of the queue to the gate.
Enterprise
This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The enterprise diagram can be viewed in SVG or PNG format and the current format is SVG. SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification
Business Interaction Matrix:
| Freight Drayage Optimization Operations Stage | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Roadway Owner | RSE Owner | RSE Operator | Fleet-Freight Manager | Freight Distribution and Logistics Provider | Intermodal Terminal Operator | Commercial Vehicle Owner | Freight Equipment Owner | Commercial Vehicle Driver | Intermodal Customer | RSE Intermodal Terminal Management Provider | Other Freight Distribution and Logistics Provider | CV On-Board Drayage Support Provider | |
| Roadway Owner | Service Delivery Agreement | ||||||||||||
| RSE Owner | Service Delivery Agreement | Operations Agreement | Application Usage Agreement | ||||||||||
| RSE Operator | Operations Agreement | Information Exchange and Action Agreement | Expectation of Information Provision | Expectation of Information Provision | |||||||||
| Fleet-Freight Manager | Information Exchange and Action Agreement | Information Exchange and Action Agreement | Information Exchange and Action Agreement | Expectation of Information Provision | Information Exchange and Action Agreement | ||||||||
| Freight Distribution and Logistics Provider | Information Exchange and Action Agreement | Information Exchange and Action Agreement | Information Exchange and Action Agreement | Information Exchange and Action Agreement | |||||||||
| Intermodal Terminal Operator | Information Exchange and Action Agreement | Information Exchange and Action Agreement | Information Exchange and Action Agreement | ||||||||||
| Commercial Vehicle Owner | Expectation of Information Provision | Information Exchange and Action Agreement | Expectation of Information Provision | Vehicle Operating Agreement | Application Usage Agreement | ||||||||
| Freight Equipment Owner | Expectation of Information Provision | Expectation of Information Provision | Expectation of Information Provision | ||||||||||
| Commercial Vehicle Driver | Vehicle Operating Agreement | ||||||||||||
| Intermodal Customer | Information Exchange and Action Agreement | Information Exchange and Action Agreement | |||||||||||
| RSE Intermodal Terminal Management Provider | Application Usage Agreement | ||||||||||||
| Other Freight Distribution and Logistics Provider | Information Exchange and Action Agreement | ||||||||||||
| CV On-Board Drayage Support Provider | Application Usage Agreement | ||||||||||||
Includes Enterprise Objects:
| Enterprise Object | Description |
|---|---|
| Application Certification Entity | The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications. |
| Commercial Vehicle Driver | The 'Commercial Vehicle Driver' represents the people that operate vehicles transporting goods, including both long haul trucks and local pick-up and delivery vans. This physical object is complementary to the Driver physical object in that it represents those interactions which are unique to Commercial Vehicle Operations. Information flowing from the Commercial Vehicle Driver includes those system inputs specific to Commercial Vehicle Operations. |
| Commercial Vehicle Manufacturer | The entity which builds commercial vehicles, including long haul trucks and local pick up and delivery vehicles. This entity is complementary to the Vehicle Manufacturer entity in that it represents those aspects of vehicle manufacture which are unique to commercial vehicles. |
| Commercial Vehicle OBE Manufacturer | The Commercial Vehicle OBE Manufacturer is the provider of the commercial vehicle on-board equipment. This entity may design and build the OBE, or may integrate other components to form the OBE, or may use some combination of approaches to provide the on-board equipment. Since the OBE could be aftermarket, retrofit, built-in or nomadic, this entity is the one that builds whatever that-is. In some cases it may be a smart phone manufacturer, or in others a top tier parts supplier, or any other entity in the production chain, depending on the device and commercial vehicle in question. |
| Commercial Vehicle Owner | The entity that owns the commercial vehicle. This entity is complementary to the Vehicle Owner in that it represents those aspects of ownership which are unique to commercial vehicles. |
| CV On-Board Drayage Support Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| CV On-Board Drayage Support Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| CV On-Board Drayage Support Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Device Certification Entity | The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type. |
| Drayage Operations Optimization Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Drayage Operations Optimization Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Drayage Operations Optimization Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Federal Regulatory | Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation. |
| Fleet Administration Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Fleet Administration Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Fleet Administration Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Fleet-Freight Manager | The 'Fleet-Freight Manager' represents the people that are responsible for the dispatching and management of Commercial Vehicle fleets (e.g. traditional Fleet Managers) and Freight Equipment assets. It may be many people in a large tracking organization or a single person (owner driver) in the case of single vehicle fleets. The Fleet-Freight Manager provides instructions and coordination for Commercial Vehicles and Freight Equipment and receives the status of the vehicles and freight equipment in the fleet that they manage. |
| Freight Administration and Management Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Freight Administration and Management Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Freight Administration and Management Provider | The developer and distributor of center systems that monitor and track the movement of freight containers, facilitates intermodal transfers and border crossings. |
| Freight Distribution and Logistics Provider | The owner and operator of the Freight Distribution and Logistics Center, ultimately responsible for the functionality that center provides. |
| Freight Equipment Manufacturer | The entity that builds freight equipment. |
| Freight Equipment Owner | The entity that owns freight equipment such as a freight container, intermodal chassis or trailer. |
| Intermodal Customer | The "Intermodal Customer" represents organizations that engage in the shipment of freight, either originator (consigner or shipper) or recipient of the cargo shipment. They enable ITS to move goods on routes that require the use of other modes of transportation such as heavy rail, air, sea, etc. This physical object interfaces with Fleet-Freight Managers to transfer cargo from one mode to another. This definition includes those responsible for the movement of freight across international borders. |
| Intermodal Terminal Operator | The entity that operates the intermodal terminal, the point of exchange where freight is moved from one mode to another. |
| ITS Certification Entity | The body that determines whether an ITS device or application may be deployed and operated in the transportation environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device and application type. Typically not a formal body, assigned on a project-by-project basis depending on the type of infrastructure involved. Since ITS projects are locally-focused (typically state or smaller), the entities that are part of this body are typically those with operational jurisdiction where the ITS is installed (e.g., state or local DOTs, state or local maintenance managers etc.) |
| Other Freight Distribution and Logistics Provider | The owner and operator of another Freight Distribution and Logistics Center, ultimately responsible for the functionality that center provides. |
| Roadway Owner | The owner of the roadway proximate to which roadside equipment will be/is installed. |
| RSE Deployer | The entity responsible for the deployment, operations and maintenance of roadside equipment. |
| RSE Intermodal Terminal Management Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| RSE Intermodal Terminal Management Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| RSE Intermodal Terminal Management Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| RSE Operator | The entity that operates roadside equipment in the transportation environment. |
| RSE Owner | The owner of roadside equipment. |
| RSE Provider | The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research. |
| State Regulatory | State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies. |
| Terminal Management Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Terminal Management Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Terminal Management Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
Includes Resources:
| Resource | Description |
|---|---|
| Application Component Certification Requirements | The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE. |
| Backoffice Service Development System | The systems used to develop backoffice (center) hardware and software components of applications. |
| Backoffice Service Installation System | The systems used to install and configure backoffice (center) hardware and software components. |
| Backoffice Service Maintenance System | The systems used to maintain and upgrade backoffice (center) hardware and software components. |
| Commercial Vehicle | The commercial vehicle includes the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It includes two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials, and provides HAZMAT response teams with timely and accurate cargo contents information after a vehicle incident. It can collect and process vehicle, cargo information from the attached freight equipment, and driver safety data and status and alert the driver whenever there is a potential safety or security problem. Basic identification, security and safety status data are supplied to inspection facilities at mainline speeds. In addition, it can automatically collect and record mileage, fuel usage, and border crossings. |
| Commercial Vehicle Databus | The 'Commercial Vehicle Databus' represents the interface to the heavy vehicle databus that connects on-board systems included in the commercial vehicle. This vehicle is used to transport goods, is operated by a professional driver and typically administered as part of a larger fleet. Commercial Vehicle classification applies to all goods transport vehicles ranging from small panel vans used in local pick-up and delivery services to large, multi-axle tractor-trailer rigs operating on long haul routes. It is a specialized and extended form of the Vehicle Databus that may be subject to different vehicle databus standards and connect with a broad range of components that are specific to commercial vehicles including the systems that are used to monitor, secure, and maintain freight while enroute. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. |
| Commercial Vehicle OBE | 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. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general capabilities with capabilities that are specific to commercial vehicles. |
| CV On-Board Drayage Support | "CV On-Board Drayage Support" communicates with the Intermodal Terminal, Fleet and Freight Management (dispatch), and third party services to support efficient drayage operations. This application provides information to the commercial vehicle driver identifying loads and efficient schedules and routes for transport to avoid terminal congestion and minimize bobtail/dry runs. It provides information to dispatch on current truck/equipment/load status. |
| Device Certification Requirements | The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment. |
| Drayage Operations Optimization Service | The "Drayage Operations Optimization Service" provides a portal for shippers and receivers to post their loads in need of transport and provide an opportunity for commercial vehicles to find a load to haul on their trip back to/from an intermodal facility. It connects load matching services with container and chassis/equipment availability information and appointment/reservations services from the intermodal terminals to provide an optimized, regionally integrated view of intermodal container transport for drayage operators. |
| Field Component Development System | The system used in a backoffice environment to develop and test the field component of the application. |
| Field Component Installation System | The system used to install a field component of a connected vehicle application. |
| Field Component Maintenance System | The system used to install and configure changes and updates to the field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance. |
| Fleet Administration | "Fleet Administration" provides vehicle tracking, dispatch, and reporting capabilities to fleet management center personnel. It gathers current road conditions and traffic 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 | 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 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. |
| Freight Distribution and Logistics 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. |
| Freight Equipment | 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment. |
| Freight Equipment Monitoring | "Freight Equipment Monitoring" includes the on-board devices used to monitor intermodal freight equipment. These devices provide freight equipment location and status of the freight, container, or chassis equipment. |
| Intermodal Customer System | 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 | 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. |
| ITS Certification Requirements | The requirements that define the functionality, performance and operational environment of an ITS device or ITS application. Applicability varies with jurisdictions, but typically devices and applications must meet pre-defined acceptance criteria prior to usage in the transportation environment. |
| ITS Field Component Development System | The system used in a backoffice environment to develop and test the ITS field component of the application. |
| ITS Field Component Installation System | The system used to install a field component of a connected vehicle application. |
| ITS Field Component Maintenance System | The system used to install and configure changes and updates to the ITS field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance. |
| Mobile Component Development System | The system used in a backoffice environment to develop and test the mobile component of the application. |
| Mobile Component Installation System | The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application. |
| Mobile Component Maintenance System | The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance. |
| Other Freight Distribution and Logistics Centers | Representing another Freight Distribution and Logistics Center, 'Other Freight Distribution and Logistics Center ' provides a source and destination for information exchange between peer centers. It enables sharing of intermodal logistics support information between centers. |
| Roadside Equipment | 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
| RSE Development System | The system used in a backoffice environment to develop and test the roadside equipment. |
| RSE Installation System | The system used to install and configure the roadside equipment. |
| RSE Intermodal Terminal Management | "RSE Intermodal Terminal Management" manages communications with commercial vehicles on behalf of an Intermodal Terminal. This application object manages entry to and exit from the facility and supports identification of entering vehicles and associated freight equipment, including containers. It also supports identification and tracking of containers within the terminal and identifies container pickup and drop-off locations, including optional routing instructions within the terminal. |
| RSE Maintenance System | The system used to configure changes and updates to the roadside equipment. This system is capable of acquiring and reporting diagnostic information about the RSE's configuration and performance. |
| 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. |
Includes Roles:
| Role | Description |
|---|---|
| Certifies | An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements. |
| Constrains | A Resource or Enterprise applies requirements, constraints and associated tests to another Resource. |
| Installs | An Enterprise performs the initial delivery, integration and configuration of the target Resource. |
| Maintains | An Enterprise administers the hardware and software that comprise the target Resource. |
| Member | An Enterprise is part of another larger, target Enterprise. |
| Operates | An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible. |
| Owns | An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable. |
Includes Coordination:
| Coordination | Type | Description |
|---|---|---|
| Application Installation Data | Information Sharing | Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow. |
| Application Interface Specification | Agreement | The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
| Application Maintenance Data | Information Sharing | Data used to facilitate the upgrade, patching and general health maintenance of an application component. |
| Application Performance Data | Information Sharing | Data used to characterize application performance, including such measures as availability, known errors and known uses. |
| Application Procurement Agreement | Agreement | An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process. |
| Application Usage Agreement | Agreement | An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
| Backoffice Component Installation Agreement | Agreement | An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party. |
| Backoffice Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the backoffice component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
| Device Placement and Operations Agreement | Agreement | An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity. |
| Expectation of Information Provision | Expectation | An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient. |
| Field Component Installation Agreement | Agreement | An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party. |
| Field Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the field component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
| Includes | Includes | Indicates that one component is entirely contained within another component. |
| Information Exchange and Action Agreement | Agreement | An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information. |
| Installation Agreement | Agreement | An agreement whereupon one entity installs an application component on a device controlled by another entity. |
| Interface Description | Agreement | Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator. |
| Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of a system under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
| Maintenance Data Exchange Agreement | Agreement | An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
| Mobile Component Installation Agreement | Agreement | An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application. |
| Mobile Component License Agreement | Agreement | An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question. |
| Mobile Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the mobile component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
| Operations Agreement | Agreement | An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
| RSE Deployment Agreement | Agreement | Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions. |
| RSE Installation Data | Information Sharing | Data necessary to configure and make RSE operational. Uni-directional. |
| RSE Maintenance Data | Information Sharing | Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional. |
| RSE Performance Data | Information Sharing | Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures. |
| RSE Procurement Agreement | Agreement | An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process. |
| Service Delivery Agreement | Agreement | A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications. |
| Vehicle Data Access Agreement | Agreement | An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data. |
| Vehicle Operating Agreement | Agreement | An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle. |
| Vehicle Procurement Agreement | Agreement | The exchange of a vehicle for compensation. One entity purchases the vehicle from the other. |
| Warranty | Agreement | A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component. |
Functional
Includes Processes:
Includes Data Flows:
Physical
This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
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 Databus | Vehicle | The 'Commercial Vehicle Databus' represents the interface to the heavy vehicle databus that connects on-board systems included in the commercial vehicle. This vehicle is used to transport goods, is operated by a professional driver and typically administered as part of a larger fleet. Commercial Vehicle classification applies to all goods transport vehicles ranging from small panel vans used in local pick-up and delivery services to large, multi-axle tractor-trailer rigs operating on long haul routes. It is a specialized and extended form of the Vehicle Databus that may be subject to different vehicle databus standards and connect with a broad range of components that are specific to commercial vehicles including the systems that are used to monitor, secure, and maintain freight while enroute. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. |
| Commercial Vehicle Driver | Vehicle | The 'Commercial Vehicle Driver' represents the people that operate vehicles transporting goods, including both long haul trucks and local pick-up and delivery vans. This physical object is complementary to the Driver physical object in that it represents those interactions which are unique to Commercial Vehicle Operations. Information flowing from the Commercial Vehicle Driver includes those system inputs specific to Commercial Vehicle Operations. |
| 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. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general capabilities with capabilities that are specific to commercial vehicles. |
| 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. |
| Fleet-Freight Manager | Center | The 'Fleet-Freight Manager' represents the people that are responsible for the dispatching and management of Commercial Vehicle fleets (e.g. traditional Fleet Managers) and Freight Equipment assets. It may be many people in a large tracking organization or a single person (owner driver) in the case of single vehicle fleets. The Fleet-Freight Manager provides instructions and coordination for Commercial Vehicles and Freight Equipment and receives the status of the vehicles and freight equipment in the fleet that they manage. |
| 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. |
| Freight Equipment | Vehicle | 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment. |
| 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. |
| Other Freight Distribution and Logistics Centers | Center | Representing another Freight Distribution and Logistics Center, 'Other Freight Distribution and Logistics Center ' provides a source and destination for information exchange between peer centers. It enables sharing of intermodal logistics support information between centers. |
| Roadside Equipment | Field | 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
Includes Application Objects:
| Application Object | Description | Physical Object |
|---|---|---|
| CV On-Board Drayage Support | "CV On-Board Drayage Support" communicates with the Intermodal Terminal, Fleet and Freight Management (dispatch), and third party services to support efficient drayage operations. This application provides information to the commercial vehicle driver identifying loads and efficient schedules and routes for transport to avoid terminal congestion and minimize bobtail/dry runs. It provides information to dispatch on current truck/equipment/load status. | Commercial Vehicle OBE |
| Drayage Operations Optimization Service | The "Drayage Operations Optimization Service" provides a portal for shippers and receivers to post their loads in need of transport and provide an opportunity for commercial vehicles to find a load to haul on their trip back to/from an intermodal facility. It connects load matching services with container and chassis/equipment availability information and appointment/reservations services from the intermodal terminals to provide an optimized, regionally integrated view of intermodal container transport for drayage operators. | Freight Distribution and Logistics Center |
| Fleet Administration | "Fleet Administration" provides vehicle tracking, dispatch, and reporting capabilities to fleet management center personnel. It gathers current road conditions and traffic 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 |
| Freight Equipment Monitoring | "Freight Equipment Monitoring" includes the on-board devices used to monitor intermodal freight equipment. These devices provide freight equipment location and status of the freight, container, or chassis equipment. | Freight Equipment |
| RSE Intermodal Terminal Management | "RSE Intermodal Terminal Management" manages communications with commercial vehicles on behalf of an Intermodal Terminal. This application object manages entry to and exit from the facility and supports identification of entering vehicles and associated freight equipment, including containers. It also supports identification and tracking of containers within the terminal and identifies container pickup and drop-off locations, including optional routing instructions within the terminal. | Roadside Equipment |
| 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 |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| available loads | Request from a shipper (consignor) for services to handle shipping of a container or freight load. Aggregated, this information represents the available loads to be shipped from intermodal customer locations in the region. |
| available truck capacity | An indication of available truck (power), equipment (chassis), and container capacity for use in load matching. |
| 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. |
| container availability request | Request for information on the availability of a container at an Intermodal Terminal. |
| container availability status | Information regarding the availability of a container at an Intermodal Terminal. |
| container delivery confirmation | Notice confirming the arrival and transfer of control of a container at a container handling facility, for example an intermodal terminal. |
| container delivery request | Request for permission to deliver a container to an intermodal facility. |
| container identification | A unique identification of a container that can be used to associate the container with a manifest and other important data. |
| container identification request | Request to a container to provide its identification information; may require the requestor to authenticate their identity. |
| container location | The location of a container, to sufficient accuracy to allow efficient container management. |
| 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. |
| container transfer location | Location within an intermodal facility that a container is to be received at or delivered to; may include guidance as well as location. |
| container transfer location request | Request for the location within an intermodal facility for the transfer of a container. |
| container transport assignment | Instructions to a commercial vehicle for the transportation of a container. |
| CVO driver initialization | This flow represents the tactile or auditory interface with ITS equipment containing the commercial vehicle driver and vehicle information. This flow contains inquiries to the commercial vehicle managing system, interaction with on-board equipment including setup, configuration, and initiation of self tests, and entry of carrier, driver, vehicle, and route information. |
| driver log | A daily log showing hours in service for the current driver. The query flow is not explicitly shown. |
| fleet manager inquiry | This flow represents the tactile or auditory interface with ITS equipment containing an inquiry from fleet manager requesting data from commercial vehicle management system. |
| fleet status | This flow represents the visual or auditory interface with ITS equipment containing fleet status information including enrollment status, safety status including inspection summaries, detailed inspection reports, and safety ratings, routing information, current vehicle information, and emergency information. |
| fleet to driver update | Updated instructions to the driver including dispatch, routing, and special instructions. |
| freight equipment information | Container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal #, seal type, door open/close status, chassis bare/covered status, tethered / untethered status, temperature, humidity, power, battery levels, brake wear data, and bill of lading/information regarding the cargo/content. |
| freight monitoring parameters | Parameters to configure the Freight Equipment for event reporting and keep alive functions. |
| 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. |
| host commercial vehicle status | Information provided to the Connected Vehicle on-board equipment from other systems on the Commercial Vehicle Platform. |
| intermodal dispatch info | Directions for dispatch for pickup or delivery of an intermodal load. |
| 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). |
| load appointment status | Information about the status of load appointments made through the drayage appointment system including any exceptions or changes that are needed by the freight company. |
| load matching info | Identification of available loads that match available truck capacity. |
| load matching systems coordination | Coordination of intermodal load-matching information between peer systems. |
| on-board vehicle data | Information about the commercial vehicle stored on-board (for maintenance purposes, gate access, cargo status, lock status, etc.). |
| terminal reservation | A reservation for container pick-up/drop-off at an intermodal terminal. |
| terminal reservation request | Request for a reservation to pick-up/drop-off containers. The request would define the pick-up/drop-off and identify an acceptable time window |
Application Interconnect Diagram
This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The application interconnect diagram can be viewed in SVG or PNG format and the current format is SVG. SVG Diagram
PNG Diagram
Application Triples
Requirements
| Need | Requirement | ||
|---|---|---|---|
| N2.073 | Freight Drayage Optimization needs to provide performance measures to public agencies for use in transportation planning and management as an incentive for public sector participation as a data provider and to promote better transportation planning and policy. | 2.170 | Freight Drayage Optimization shall make freight performance monitoring data available to authorized public sector systems. |
| N2.075 | Freight Drayage Optimization needs to provide support for intermodal drayage operations optimization services. | 2.176 | Freight Drayage Optimization shall provide an intermodal drayage operations optimization service to match loads with qualified carriers. |
| 2.176a | Freight Drayage Optimization shall interact with load-matching systems to support load-matching of empty containers. | ||
| N2.076 | Freight Drayage Optimization needs to link to systems that support load matching for empty containers and chassis in order to maximize Congestion avoidance, air quality, and efficiency benefits. | 2.177 | Freight Drayage Optimization shall provide an interface for chassis operators to provide their schedule information for a load-matching service. |
| 2.178 | Freight Drayage Optimization shall provide an interface for intermodal shippers to provide pick-up information for a load-matching service. | ||
| 2.179 | Freight Drayage Optimization shall provide load-matching data to chassis operators to pick-up available containers. | ||
| 2.180 | Freight Drayage Optimization shall provide scheduled pick-up times at intermodal depots corresponding with the load-matching performance parameters. | ||
| 2.181 | Freight Drayage Optimization shall provide a load-matching service that optimizes container and chassis transportation in criteria such as location, traffic, environmental, emissions, air quality data, travel costs, depot or distribution center schedules. | ||
| N2.079 | Freight Drayage Optimization needs to link to existing dispatch software platforms to provide a seamless integration with existing dispatch/routing procedures. | 2.184 | Freight Drayage Optimization shall provide freight-specific traveler information to fleet and freight management dispatch systems. |
Related Sources
- Freight Advanced Traveler Information System (FRATIS) ConOps, Final, 4/20/2012
Security
In order to participate in this application, each physical object should meet or exceed the following security levels.
| Physical Object Security | ||||
|---|---|---|---|---|
| Physical Object | Confidentiality | Integrity | Availability | Security Class |
| Security levels have not been defined yet. | ||||
In order to participate in this application, 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 | |||
| Security levels have not been defined yet. | |||||