CVO12: HAZMAT Management
This service package integrates incident management capabilities with commercial vehicle tracking to assure effective treatment of HAZMAT material transport, including response to incidents. HAZMAT tracking is performed by the Fleet and Freight Management Center. The Emergency Management Center is notified by the Commercial Vehicle and the Fleet and Freight Management Center of the HAZMAT vehicle location and information about the HAZMAT load. If an incident occurs, the Emergency Management Center can use the information to coordinate the response. The response is tailored based on information that is provided as part of the original incident notification or derived from supplemental information provided by the Fleet and Freight Management Center. The latter information can be provided prior to the beginning of the trip, during the trip, or gathered following the incident depending on the selected policy and implementation.
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 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 | Emergency Management Center Maintainer | Maintenance Data Exchange Agreement |
| Commercial Vehicle OBE Owner | Emergency Management Center Owner | Expectation of Data Provision |
| Commercial Vehicle OBE Owner | Emergency Management Center User | Service Usage 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 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 | Fleet and Freight Management Center Maintainer | Maintenance Data Exchange Agreement |
| Emergency Management Center Owner | Fleet and Freight Management Center Owner | Information Exchange Agreement |
| Emergency Management Center Owner | Fleet and Freight Management Center User | Service Usage Agreement |
| Emergency Management Center Supplier | Emergency Management 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 | Emergency Management Center Maintainer | Maintenance Data Exchange Agreement |
| Fleet and Freight Management Center Owner | Emergency Management Center Owner | Information Exchange Agreement |
| Fleet and Freight Management Center Owner | Emergency Management Center 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 Supplier | Fleet and Freight Management Center Owner | Warranty |
| Freight Equipment Maintainer | Freight Equipment | Maintains |
| Freight Equipment Manager | Freight Equipment | Manages |
| Freight Equipment Owner | Commercial Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
| Freight Equipment Owner | Commercial Vehicle OBE Owner | Expectation of Data Provision |
| Freight Equipment Owner | Commercial Vehicle OBE User | Service Usage Agreement |
| Freight Equipment Owner | Fleet and Freight Management Center Maintainer | Maintenance Data Exchange Agreement |
| Freight Equipment Owner | Fleet and Freight Management Center Owner | Expectation of Data Provision |
| Freight Equipment Owner | Fleet and Freight Management Center User | Service Usage Agreement |
| Freight Equipment Owner | Freight Equipment Maintainer | System Maintenance Agreement |
| Freight Equipment Owner | Freight Equipment Manager | Operations Agreement |
| Freight Equipment Supplier | Freight Equipment 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 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. |
| 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 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. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| CV On-Board Cargo Monitoring | 'CV On-Board Cargo Monitoring' monitors the location and status of the commercial vehicle and its cargo. It sends the collected data to appropriate centers and roadside facilities, including emergency management in the case of HAZMAT incidents. Depending on the nature of the cargo, it may include sensors that measure temperature, pressure, load leveling, acceleration, and other attributes of the cargo. | Commercial Vehicle OBE |
| Emergency Commercial Vehicle Response | 'Emergency Commercial Vehicle Response' identifies and initiates a response to commercial vehicle and freight equipment related emergencies. These emergencies may include incidents involving hazardous materials as well as the detection of non-permitted transport of security sensitive hazmat. It identifies the location of the vehicle, the nature of the incident, the route information, and information concerning the freight itself. The information supports the determination of the response and identifies the responding agencies to notify. | Emergency 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 |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| commercial vehicle location data | Current vehicle location and related operational conditions data provided by a commercial vehicle. |
| 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. |
| hazmat information | Information about a particular hazmat load including nature of the load and unloading instructions. May also include hazmat vehicle route and route update information. |
| hazmat information request | Request for information about a particular hazmat load. |
| hazmat notification | Information provided to emergency response organizations regarding a hazmat load including when cargo sensors detect an issue with the load such as a release of hazardous material. This information will include sensor information, vehicle identification, and carrier identification. |
Goals and Objectives
Associated Planning Factors and Goals
| Planning Factor | Goal |
|---|---|
| B. Increase the safety of the transportation system for motorized and nonmotorized users; | Reduce fatalities and injuries |
| C. Increase the security of the transportation system for motorized and nonmotorized users; | Improve security |
| F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; | Enhance integration and connectivity |
| G. Promote efficient system management and operation; | Improve efficiency |
Associated Objective Categories 
| Objective Category |
|---|
| Emergency/Incident Management: Incident Duration |
| Emergency/Incident Management: Inter-Agency Coordination |
| Security: Terrorism, Natural Disasters, and Hazardous Material Incidents |
Associated Objectives and Performance Measures
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.
Needs and Requirements
| Need | Functional Object | Requirement | ||
|---|---|---|---|---|
| 01 | Fleet and Freight Management needs to monitor the status of its freight, including the drivers, vehicles, and the cargo in order to determine if an issue involving hazardous materials occurs and where it is. | CV On-Board Cargo Monitoring | 03 | The commercial vehicle shall monitor information concerning the freight equipment including cargo type, HAZMAT designation (if any) for the cargo, cargo weight, the type of container in which the cargo is held, safety condition of the cargo. |
| 04 | The commercial vehicle shall forward information concerning the freight equipment on to its fleet and freight management center as well as the roadside check facility. | |||
| Freight Administration and Management | 01 | The center shall collect data from the commercial vehicles carrying freight or from the freight equipment itself. Data includes container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal number/type, door open/close status, chassis bare/covered status, tethered/untethered status, bill of lading, and sensor status. | ||
| Freight Equipment Monitoring | 03 | The onboard freight device shall provide freight equipment location and status of the freight, container, or chassis equipment. | ||
| 06 | The onboard freight device shall provide status of the freight to the attached commercial vehicle or fleet and freight management, indicating the internal temperature, humidity, power and battery levels. | |||
| 02 | Fleet and Freight Management needs to provide the status, location, and specific contents of loads that have hazardous materials (HAZMAT) or dangerous goods to the appropriate emergency management when they are involved in an incident in order to ensure the safety of the public and the responders. | CV On-Board Cargo Monitoring | 06 | The commercial vehicle shall send notification of a hazmat spill to and share them with the arriving public safety vehicles, including the information from cargo sensors, vehicle location, and the carrier identification. |
| Freight Administration and Management | 10 | The center shall provide emergency management information about a particular hazmat load including nature of the load and unloading instructions. May also include hazmat vehicle route and route update information. | ||
| 03 | Emergency Management needs to collect information from Fleet and Freight Management or directly from equipped vehicles in order determine the status, location, and specific contents of loads with hazardous materials (HAZMAT) when they are involved in an incident in order to protect the public's safety and ensure the safety of its responders. | CV On-Board Cargo Monitoring | 05 | The commercial vehicle shall send notification of a hazmat spill to the appropriate emergency management center in case of an incident including the information from cargo sensors, vehicle location, and the carrier identification. |
| Emergency Commercial Vehicle Response | 02 | The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations, or commercial fleet operators and present the possible incident information to the emergency system operator. This may include detection of non-permitted transport of security sensitive hazmat, hazardous cargo spills, etc. | ||
| 03 | The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for incidents involving potential hazardous materials. | |||
| 04 | The center shall forward the verified emergency information to the responding agency based on the location and nature of the emergency. | |||
| Freight Administration and Management | 01 | The center shall collect data from the commercial vehicles carrying freight or from the freight equipment itself. Data includes container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal number/type, door open/close status, chassis bare/covered status, tethered/untethered status, bill of lading, and sensor status. | ||
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
| Physical Object Security | ||||
|---|---|---|---|---|
| Physical Object | Confidentiality | Integrity | Availability | Security Class |
| Commercial Vehicle OBE | High | High | High | Class 5 |
| Emergency Management Center | High | High | High | Class 5 |
| Fleet and Freight Management Center | High | High | High | Class 5 |
| Freight Equipment | Moderate | Moderate | Moderate | Class 2 |
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 OBE | Emergency Management Center | commercial vehicle location data | Moderate | Moderate | Moderate |
| If observed, could be used by a criminal in the performance of a crime related to a commercial vehicle. May include PII, or pseudonomous information associated with PII. | Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. | Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. Location data is dynamic, so probably needs to be updated frequently. | |||
| Commercial Vehicle OBE | Emergency Management Center | hazmat notification | Moderate | High | High |
| Includes PII which should be protected. If not practical to protect, a simpler message without the PII should be distributed. | Hazmat spill notification has a time-critical and life-saving and property saving component. | Hazmat spill notification has a time-critical and life-saving and property saving component. Set HIGH because the potential consequences are very severe. | |||
| Commercial Vehicle OBE | Fleet and Freight Management Center | commercial vehicle location data | Moderate | Moderate | Moderate |
| If observed, could be used by a criminal in the performance of a crime related to a commercial vehicle. May include PII, or pseudonomous information associated with PII. | Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. | Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. Location data is dynamic, so probably needs to be updated frequently. | |||
| Commercial Vehicle OBE | Fleet and Freight Management Center | freight equipment information | Moderate | Moderate | Moderate |
| Will include proprietary and/or competitive information that should be disclosed only when necessary and to those with a need for the information. | Information must be accurate in order to be properly acted upon in support of screening or commercial vehicle safety processes. | Information must be timely in order to be properly acted upon in support of screening or commercial vehicle safety processes, though some of the information contained has alternative delivery mechanisms. | |||
| Commercial Vehicle OBE | Fleet and Freight Management Center | hazmat notification | High | High | High |
| This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. Since hazardous material is by nature very dangerous, access to the routing, and load nature information could lead to a dangerous event. As such this information needs to be well protected. | If this is compromised, the EMC may not react properly to a hazmat incident, and thus assign inappropriate assets (too many, wrong type, not enough), leading to a longer or more damaging incident. | A delay in reporting this may cause a delay in getting the appropriate assets to the incident, or an over-commitment of assets. While the EMC may react to avoid the former by committing more assets than may be necessary, this in turn will create risk by making those assets unavailable to respond to incidents where they are truly needed. Such delays may be catastrophic for hazmat incidents. | |||
| Emergency Management Center | Fleet and Freight Management Center | hazmat information request | Moderate | Moderate | Moderate |
| Related to the contents of a load, which implies the business a particular operator or even driver is doing. This is competitive and may include PII. | If the request is malformed or corrupted then the response data descirbing the HAZMAT load will not be provided or be incorrect. | If the request is not received then the management of HAZMAT operations will be compromised. Availability may be LOW if this type of request is quite rare, but given the potential impacts of HAZMAT incidents this should probably always be at least MODERATE. | |||
| Fleet and Freight Management Center | Commercial Vehicle OBE | hazmat information | High | High | High |
| This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. Since hazardous material is by nature very dangerous, access to the routing, and load nature information could lead to a dangerous event. As such this information needs to be well protected. | If this is compromised, the EMC may not react properly to a hazmat incident, and thus assign inappropriate assets (too many, wrong type, not enough), leading to a longer or more damaging incident. | A delay in reporting this may cause a delay in getting the appropriate assets to the incident, or an over-commitment of assets. While the EMC may react to avoid the former by committing more assets than may be necessary, this in turn will create risk by making those assets unavailable to respond to incidents where they are truly needed. Such delays may be catastrophic for hazmat incidents. | |||
| Fleet and Freight Management Center | Emergency Management Center | commercial vehicle location data | Moderate | Moderate | Moderate |
| If observed, could be used by a criminal in the performance of a crime related to a commercial vehicle. May include PII, or pseudonomous information associated with PII. | Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. | Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. Location data is dynamic, so probably needs to be updated frequently. | |||
| Fleet and Freight Management Center | Emergency Management Center | hazmat information | High | High | High |
| This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. Since hazardous material is by nature very dangerous, access to the routing, and load nature information could lead to a dangerous event. As such this information needs to be well protected. | If this is compromised, the EMC may not react properly to a hazmat incident, and thus assign inappropriate assets (too many, wrong type, not enough), leading to a longer or more damaging incident. | A delay in reporting this may cause a delay in getting the appropriate assets to the incident, or an over-commitment of assets. While the EMC may react to avoid the former by committing more assets than may be necessary, this in turn will create risk by making those assets unavailable to respond to incidents where they are truly needed. Such delays may be catastrophic for hazmat incidents. | |||
| Fleet and Freight Management Center | Emergency Management Center | hazmat notification | High | High | High |
| This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. Since hazardous material is by nature very dangerous, access to the routing, and load nature information could lead to a dangerous event. As such this information needs to be well protected. | If this is compromised, the EMC may not react properly to a hazmat incident, and thus assign inappropriate assets (too many, wrong type, not enough), leading to a longer or more damaging incident. | A delay in reporting this may cause a delay in getting the appropriate assets to the incident, or an over-commitment of assets. While the EMC may react to avoid the former by committing more assets than may be necessary, this in turn will create risk by making those assets unavailable to respond to incidents where they are truly needed. Such delays may be catastrophic for hazmat incidents. | |||
| Freight Equipment | Commercial Vehicle OBE | freight equipment information | Moderate | Moderate | Moderate |
| Cargo status information, though internal to the vehicle, should probably be protected as part of a sound defense-in-depth strategy against malicious hacking. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | Cargo status information, though internal to the vehicle, should probably be protected as part of a sound defense-in-depth strategy against malicious hacking. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | On-board data exchanges, should be at least MODERATE so that on-board systems can fulfill their functions. Freight Vehicle to CV OBE is considered on-board when the vehicle and freight are mated, so the same logic holds. | |||
| Freight Equipment | Fleet and Freight Management Center | freight equipment information | Moderate | Moderate | Moderate |
| Will include proprietary and/or competitive information that should be disclosed only when necessary and to those with a need for the information. | Information must be accurate in order to be properly acted upon in support of screening or commercial vehicle safety processes. | Information must be timely in order to be properly acted upon in support of screening or commercial vehicle safety processes, though some of the information contained has alternative delivery mechanisms. | |||
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 receive emergency notification information from commercial vehicles, commercial vehicle check stations, or commercial fleet operators and present the possible incident information to the emergency system operator. This may include detection of non-permitted transport of security sensitive hazmat, hazardous cargo spills, etc. | 03 | Emergency Management needs to collect information from Fleet and Freight Management or directly from equipped vehicles in order determine the status, location, and specific contents of loads with hazardous materials (HAZMAT) when they are involved in an incident in order to protect the public's safety and ensure the safety of its responders. |
| 002 | The system shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for incidents involving potential hazardous materials. | 03 | Emergency Management needs to collect information from Fleet and Freight Management or directly from equipped vehicles in order determine the status, location, and specific contents of loads with hazardous materials (HAZMAT) when they are involved in an incident in order to protect the public's safety and ensure the safety of its responders. |
| 003 | The system shall collect data from the commercial vehicles carrying freight or from the freight equipment itself. Data includes container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal number/type, door open/close status, chassis bare/covered status, tethered/untethered status, bill of lading, and sensor status. | 03 | Emergency Management needs to collect information from Fleet and Freight Management or directly from equipped vehicles in order determine the status, location, and specific contents of loads with hazardous materials (HAZMAT) when they are involved in an incident in order to protect the public's safety and ensure the safety of its responders. |
| 01 | Fleet and Freight Management needs to monitor the status of its freight, including the drivers, vehicles, and the cargo in order to determine if an issue involving hazardous materials occurs and where it is. | ||
| 004 | The system shall provide emergency management information about a particular hazmat load including nature of the load and unloading instructions. May also include hazmat vehicle route and route update information. | 02 | Fleet and Freight Management needs to provide the status, location, and specific contents of loads that have hazardous materials (HAZMAT) or dangerous goods to the appropriate emergency management when they are involved in an incident in order to ensure the safety of the public and the responders. |
| 005 | The system shall monitor information concerning the freight equipment including cargo type, HAZMAT designation (if any) for the cargo, cargo weight, the type of container in which the cargo is held, safety condition of the cargo. | 01 | Fleet and Freight Management needs to monitor the status of its freight, including the drivers, vehicles, and the cargo in order to determine if an issue involving hazardous materials occurs and where it is. |
| 006 | The system shall forward information concerning the freight equipment on to its fleet and freight management center as well as the roadside check facility. | 01 | Fleet and Freight Management needs to monitor the status of its freight, including the drivers, vehicles, and the cargo in order to determine if an issue involving hazardous materials occurs and where it is. |
| 007 | The system shall send notification of a hazmat spill to the appropriate emergency management center in case of an incident including the information from cargo sensors, vehicle location, and the carrier identification. | 03 | Emergency Management needs to collect information from Fleet and Freight Management or directly from equipped vehicles in order determine the status, location, and specific contents of loads with hazardous materials (HAZMAT) when they are involved in an incident in order to protect the public's safety and ensure the safety of its responders. |
| 008 | The system shall send notification of a hazmat spill to and share them with the arriving public safety vehicles, including the information from cargo sensors, vehicle location, and the carrier identification. | 02 | Fleet and Freight Management needs to provide the status, location, and specific contents of loads that have hazardous materials (HAZMAT) or dangerous goods to the appropriate emergency management when they are involved in an incident in order to ensure the safety of the public and the responders. |
| 009 | The system shall provide freight equipment location and status of the freight, container, or chassis equipment. | 01 | Fleet and Freight Management needs to monitor the status of its freight, including the drivers, vehicles, and the cargo in order to determine if an issue involving hazardous materials occurs and where it is. |
| 010 | The system shall provide status of the freight to the attached commercial vehicle or fleet and freight management, indicating the internal temperature, humidity, power and battery levels. | 01 | Fleet and Freight Management needs to monitor the status of its freight, including the drivers, vehicles, and the cargo in order to determine if an issue involving hazardous materials occurs and where it is. |