4.5 Hazardous Material Security And Incident Response (User Service*)

The Hazardous Materials Security and Incident Response user service provides emergency personnel at the scene of a hazardous materials incident immediate information on the types and quantities of hazardous materials present in order to facilitate a quick and appropriate response. The service includes tracking of security sensitive hazardous materials shipments, notification of security sensitive HAZMAT unauthorized activity, notification of unauthorized security sensitive HAZMAT driver, and roadside security sensitive HAZMAT monitoring.


User Service Requirements*:
4.5.0 ITS shall include a Hazardous Materials (HAZMAT) Security and Incident Response (HSIR) service.
PSpecs*: 1.3.4.5 , 10 , 10 , 2.1.1.2 , 2.1.1.3 , 2.1.1.4 , 2.1.1.5 , 2.1.1.6 , 2.1.1.7 , 2.1.2 , 2.1.6 , 2.3.2.2 , 2.3.4 , 2.4.3 , 2.4.7 , 2.4.9 , 5.1.1.1 , 5.1.1.2 , 5.1.1.3 , 5.1.2 , 5.1.4 , 5.3.2 , 5.3.7
4.5.1 HSIR shall include a HAZMAT Incident Notification (HIN) function.
PSpecs*: 2.1.1.4 , 2.4.3 , 5.1.1.1 , 5.1.1.2
4.5.1.1 HIN shall include the capability to provide enforcement and HAZMAT response teams with timely and accurate information on cargo contents when the vehicle is involved in an incident.
PSpecs*: 2.4.3 , 5.1.1.1 , 5.1.1.2
4.5.1.2 HIN shall be capable of providing the following Information :
PSpecs*: 2.1.1.4 , 2.4.3 , 5.1.1.1 , 5.1.1.2
4.5.1.2(a) Time of incident.
PSpecs*: 2.4.3 , 5.1.1.1 , 5.1.1.2
4.5.1.2(b) Location of the incident.
PSpecs*: 2.4.3 , 5.1.1.1 , 5.1.1.2
4.5.1.2(c) The material(s) involved.
PSpecs*: 2.1.1.4 , 2.4.3 , 5.1.1.1 , 5.1.1.2
4.5.2 HSIR shall provide an Operation Focal Point (OFP) for initiating appropriate responses.
PSpecs*: 2.1.1.4 , 5.1.4
4.5.2.1 OFP shall be capable of being implemented as either a centralized dispatch or several de-centralized dispatch units or vehicles.
PSpecs*: 5.1.4
4.5.2.2 OFP shall provide the capability for existing dispatch centers to receive the calls, determine response requirements, and route distress calls to predesignated responding agencies.
PSpecs*: 5.1.4
4.5.2.3 OFP shall provide the capability for operators to coordinate with other agencies and response services to include, but not be limited to, the following:
PSpecs*: 2.1.1.4 , 5.1.4
4.5.2.3(a) State and/or local transportation officials.
PSpecs*: 5.1.4
4.5.2.3(b) Police departments.
PSpecs*: 5.1.4
4.5.2.3(c) Highway patrol.
PSpecs*: 5.1.4
4.5.2.3(e) Emergency medical services.
PSpecs*: 5.1.4
4.5.2.3(f) Environmental protection agencies.
PSpecs*: 5.1.4
4.5.2.3(g) HAZMAT teams.
PSpecs*: 5.1.4
4.5.2.3(h) Towing and other "courtesy" services.
PSpecs*: 5.1.4
4.5.3 HSIR shall include a Communications (COMM) function.
PSpecs*: 10 , 10 , 5.1.1.1 , 5.1.1.2 , 5.1.1.3 , 5.1.4 , 5.3.2 , 5.3.7
4.5.3.1 COMM shall provide the capability for distress signals to be sent to a focal point.
PSpecs*: 5.1.1.1 , 5.1.1.2 , 5.1.1.3
4.5.3.2 COMM shall provide the capability for relay of distress information to response units in real-time.
PSpecs*: 5.3.2 , 5.3.7
4.5.3.3 COMM shall provide the capability for data to be sent from any location covering all areas of the contiguous United States.
PSpecs*: 5.1.4
4.5.3.4 COMM shall provide the capability for linkages/interfaces with various existing networks.
PSpecs*: 5.1.4
4.5.3.5 COMM shall provide the capability for the motorist to travel from region to region without performing manual adjustment of equipment.
PSpecs*: 10 , 10
4.5.4 HSIR shall include a HAZMAT Security (HS) function.
PSpecs*: 1.3.4.5 , 2.1.1.2 , 2.1.1.3 , 2.1.1.5 , 2.1.1.6 , 2.1.1.7 , 2.1.2 , 2.1.6 , 2.3.2.2 , 2.3.4 , 2.4.3 , 2.4.7 , 2.4.9 , 5.1.1.1 , 5.1.1.2 , 5.1.2 , 5.1.4
4.5.4.1 HS shall include a security sensitive HAZMAT shipment tracking function (HSTF).
PSpecs*: 2.1.1.2 , 2.1.1.3 , 2.1.1.5 , 2.1.1.6 , 2.1.2 , 2.1.6 , 5.1.1.1 , 5.1.1.2
4.5.4.1.1 HSTF shall allow tracking of the location of a vehicle with a security sensitive HAZMAT shipment by the vehicle’s dispatch function.
PSpecs*: 2.1.1.6 , 2.1.2
4.5.4.1.2 HSTF shall include the capability to store the planned route of the vehicle carrying the security sensitive HAZMAT shipment.
PSpecs*: 2.1.1.2
4.5.4.1.3 HSTF shall identify when the security sensitive HAZMAT shipment has deviated from the planned route.
PSpecs*: 2.1.1.6
4.5.4.1.4 HSTF shall have the capability of identifying sensitive (or geofenced) geographic areas.
PSpecs*: 2.1.1.3 , 2.1.1.5
4.5.4.1.5 HSTF shall identify when the security sensitive HAZMAT shipment has entered a sensitive geographic area.
PSpecs*: 2.1.1.6
4.5.4.1.6 HSTF shall include the capability to notify public safety agencies, including those having jurisdiction over the location, when a significant security sensitive HAZMAT route deviation has been detected and verified.
PSpecs*: 2.1.6 , 5.1.1.2
4.5.4.1.7 HSTF shall include the capability to notify traffic management agencies when a significant security sensitive HAZMAT route deviation has been detected and verified.
PSpecs*: 2.1.6 , 5.1.1.1 , 5.1.1.2
4.5.4.2 HS shall provide a roadside security sensitive HAZMAT security (RHS) function.
PSpecs*: 2.3.2.2 , 2.3.4 , 5.1.1.1 , 5.1.1.2 , 5.1.2 , 5.1.4
4.5.4.2.1 RHS shall include the capability for detection of security sensitive HAZMAT shipments.
PSpecs*: 2.3.4
4.5.4.2.2 RHS shall include the capability for classification of security sensitive HAZMAT shipments.
PSpecs*: 2.3.4
4.5.4.2.3 RHS shall provide the capability to correlate a security sensitive HAZMAT vehicle detection with its authorized activity.
PSpecs*: 2.3.2.2
4.5.4.2.4 RHS shall include the capability to notify public safety agencies, including those having jurisdiction over the location, when unauthorized security sensitive HAZMAT activity has been detected and verified.
PSpecs*: 2.3.2.2
4.5.4.2.5 RHS shall include the capability to notify traffic management agencies when unauthorized security sensitive HAZMAT activity has been detected and verified.
PSpecs*: 2.3.2.2 , 5.1.1.1 , 5.1.1.2 , 5.1.2 , 5.1.4
4.5.4.3 HS shall include a Driver Authentication function (DA)
PSpecs*: 1.3.4.5 , 2.1.1.7 , 2.1.6 , 2.4.3 , 2.4.7 , 2.4.9 , 5.1.1.1 , 5.1.1.2 , 5.1.2 , 5.1.4
4.5.4.3.1 DA shall include the capability to store the identities of authorized drivers for a specific trip or set of trips or class of trips.
PSpecs*: 2.4.9
4.5.4.3.2 DA shall include the capability to determine the identity of a driver.
PSpecs*: 2.4.9
4.5.4.3.3 DA shall include the capability to notify the vehicles dispatch function if an unauthorized driver attempts to operate the vehicle.
PSpecs*: 2.4.3
4.5.4.3.4 DA shall include the capability to safely disable a vehicle if an unauthorized driver attempts to operate the vehicle.
PSpecs*: 2.4.3
4.5.4.3.5 DA shall include the capability to allow a vehicles dispatch function to safely disable the vehicle.
PSpecs*: 2.4.3
4.5.4.3.6 DA shall include the capability to notify public safety if an unauthorized driver attempts to operate the vehicle.
PSpecs*: 2.1.1.7 , 2.1.6 , 2.4.7 , 5.1.1.2
4.5.4.3.7 DA shall include the capability to notify traffic management if an unauthorized driver attempts to operate the vehicle.
PSpecs*: 1.3.4.5 , 2.1.1.7 , 2.1.6 , 2.4.7 , 5.1.1.1 , 5.1.1.2 , 5.1.2 , 5.1.4