MichaelFiliaggi TSA presentation HTSP 10 24 06

Department of Homeland SecurityTransportation Security AdministrationHAZMAT Truck Security Pilot Commercial Vehicle and Freight Mobility Forum BriefingOctober 24, 2006: 

Department of Homeland Security Transportation Security Administration HAZMAT Truck Security Pilot Commercial Vehicle and Freight Mobility Forum Briefing October 24, 2006

Pilot Overview: 

Pilot Overview The HAZMAT Truck Security Pilot is a congressionally mandated pilot project to design and build a centralized truck tracking center capability.  TSA is developing a set of protocols capable of interfacing with existing truck tracking systems, government intelligence centers, and first responders.

Pilot Goals: 

Pilot Goals The desired outcome is to provide TSA with a tested and established truck tracking center that will allow TSA to “continually” track truck locations and HAZMAT load types in all 50 states and to receive exception based events.

General Overview: 

General Overview The purposes of the HAZMAT Truck Security Pilot are: Test and evaluate commercial truck tracking and identification systems capabilities in all 50 states Test and evaluate theft detection and alert systems (examples) Unexpected change in weight of the cargo. Failure of a shipment to arrive within a specific period around the estimated time of arrival. Unexpected separation of a trailer from its tractor Deviation of a shipment from its expected route Driver declared emergency Develop and demonstrate a prototype for a centralized truck tracking center track shipments of interest truck locations and load types in all 50 states coordinate response between the truck tracking center and first responders Develop and demonstrate a non-proprietary universal interface system a set of protocols that will allow cargo information, alerts and tracking information to be transmitted from all commercially available tracking systems to the prototype truck tracking center.

TTC Key Components: 

The elements of the HAZMAT Truck Security Pilot are: A certified emergency dispatch center manning the Truck Tracking Center to coordinate response to a Transportation Security Incident (TSI) The Universal Communications interface based on web services and the IEEE 1512 XML message set, implemented using the Intelligent Information Integration Broker (I3B). The Transportation Event Acquisition and Management System (TEAMS) software application used to obtain, organize, and display information associated with a Transportation Security Incident (TSI) using the Universal Data Interface and made available to users (dispatchers, first responders, government agencies at all levels and carrier dispatch) through a browser-based interface. The FreightDesk Technologies’ FDfolio™ software application used to manage/retrieve data associated with cargos, standard response for hazardous materials, and supply chain management relevant to an incident. TTC Key Components

Prototype centralized truck tracking center: 

Prototype centralized truck tracking center The prototype Trucking Tracking Center operations will be conducted out of an accredited emergency dispatch center to coordinate public safety responses to TSIs Rural/Metro Medical Services headquartered in Buffalo, New York, has 520+ employees servicing 22 hospitals, over 100 nursing homes and health care facilities as well as the one million residents who reside in Western New York. Fully redundant self-sustaining emergency communications center A commitment to excellence in the field of EMS has resulted in the Western New York operation achieving the highest standard in the ambulance industry. Since 1994, the Commission of Accreditation of Ambulance Services (CAAS) has recognized the operation as one that meets or exceeds the industry's strict standards. Only 1% of all ambulance services nationwide achieve this standard. TTCP dispatchers will provide the "single point of contact to evaluate and coordinate, in conjunction with DHS/TSA and other law enforcement agencies” a response to a an event/incident.

Universal Communications Interface: 

Universal Communications Interface Web Services – open systems software designed to support interoperable machine-to-machine interaction over a network IEEE1512 XML - Institute of Electrical and Electronics Engineers, Standard for Common Incident Management Message Sets for Use by Emergency Management Centers Endorsed by USDOT (used in programs that share data between TMC and Public Safety CAD Systems) Compliant with Global Justice XML Data Model (USDOJ) Compliant with National Incident Management System (NIMS) Intelligent Information Integration Bus (I3B) – middle-ware bridging disparate systems data exchange ANSIx12 / EDI standards – electronic data interchange standards for the trucking industry Develop and demonstrate a non-proprietary universal interface system or set of protocols that will allow alerts and tracking information to be transmitted from all commercially available tracking systems to a prototype truck tracking center:

Data Use and Security: 

Data Use and Security Data collected is used exclusively by TSA for monitoring hazmat transport and security Data is considered Sensitive Security Information (SSI) per 49 CFR 1520 Only TSA vetted personnel have access to data Data may be shared with public safety responders on a need-to-know basis (event/incident alert/response) Data is collected using internet security tools (encryption, firewalls, VPN, etc.) Data is stored on secure servers operating within the scope of the Truck Security Pilot only Data is not released outside scope of the program Data security refers to the trusted relationship between TSA and the data provider/owner and their expectation of privacy in the collection, use and sharing of provided data.

Carrier Participation: 

Carrier Participation Willing to share telematics and manifest data with TSA Sign TSA Memorandum of Agreement An interface to telematics data is available, inform telematics provider that you agree to participate in the program Assistance in collecting manifest data by one or more of the following: If you have electronic manifest data: Technical assistance to implement your existing application programming interface (API), we will make it work with the UCI Develop a standards based interface within your system to the UCI If you do not have electronic manifest data: Manually entering key manifest data into a browser based application for every hazmat shipment (i.e. UN/NA Material ID number, quantity, origin, destination, truck ID, truck description-make, color, plate) Provide a 24/7 emergency contact number for a carrier representative to report a TSI (716-332-1222)

What is IEEE-1512: 

What is IEEE-1512 The Institute of Electrical and Electronics Engineers, Inc. (IEEE) Standard for Common Incident Management Message Sets for Use by Emergency Management Centers Sponsor: IEEE Standards Coordinating Committee 32 on ITS. Participants: American Association of State Highway and Transportation Officials (AASHTO), Institute of Transportation Engineers (ITE), Association of Public Communications Officials (APCO) A Family of XML based Center-to-Center Incident Management Messaging Standards 1512.0 Base Standard 1512.1 Traffic Incident Management 1512.2 Public Safety Incident Management 1512.3 Hazardous Materials Incident Management IEEE-1512 Standard Committee collaborates with other standards bodies: ITE-TMDD – Traffic Management Data Dictionary IEEE-ATIS – Advanced Traveler Information Systems IEEE-ITIS – International Traveler Information Systems GJXDM – Global Justice XML Data Model

IEEE-1512 Sample Message Types: 

IEEE-1512 Sample Message Types Messages consist of Sub Messages, Data Frames and Data Elements Always contains one or more sub messages Incident Description (IDX) Incident Id Event Type - International Traveler Information System (ITIS) Event Location - Location Referencing Message Specification Close Incident Event (CIE) Indicates that the event is closed from the perspective of the sending center Key Data Elements: Incident Id, Timestamp Other message types: Request Information (RIN) Merge / Split incident event (MIE)

IEEE-1512 IDX Sub Messages: 

IEEE-1512 IDX Sub Messages Cargo Vehicle - Description of cargo carrying vehicle and/or cargo container message data: Summary gross type and condition of a vehicle placard or warning data Power Units details about cargo hauling vehicle Cargo Units links vehicle to cargo units Cargo Units - Provides data about the type of cargo units being carried and their condition message data: Condition Condition of the cargo unit Contains Details about contents of a cargo unit Cargo Documents - Provides a summary of cargo shipping papers and manifest data message data: Vehicle Unit ID – links cargo to vehicle Shipping Header Replicates shipping manifest data Shipping Entry Key data from shipping documents

Transportation Event Acquisition and Management System: 

Transportation Event Acquisition and Management System Software application to support monitoring transportation events and coordinating emergency response Data communication interface to collect data from other transportation management systems Personnel notification (email, cell phone, pager) of new events based on geographic location and event data Responder identification and notification based on geographic location of event Correlation of disparate data from multiple sources (filtering) Browser based interface for remote access GIS visualization of event information Secure access control HTTPS and user id / password Access restrictions (authorization, geographic location, data, time)

Universal Communications Interface Data Flow Model: 

Tracking System Three Tracking System Two Tracking System One Carrier Y Carrier X Manifest Shipper B Bill of Lading Shipper A Bill of Lading TTC FDfolio VPN or https First Responder Dispatch https Gov’t Intel Sys TTC Dispatch Voice Telephone TSOC Voice Telephone Cargo A Truck 1 https or VPN VPN (or https) VPN (or https) VPN or https Tracking System to carrier data (not part of TSP) 06/25/2006 Truck Tracking Center Manifest links Truck 1 with Cargo A Reporting location and status of Truck 1 Reporting Manifest Data UCI Universal Communications Interface Universal Communications Interface Data Flow Model Manual Entry TEAMS May require a unique interface to the UCI

Concept of Operations: 

Concept of Operations Collaborative Transportation Security Incident (TSI) decision process In conference with a TSA watch officer, local public safety and carrier representative, provide and evaluate information to assist the TSA watch officer in making a response decision. Assistance in facilitating the appropriate response When an alert / event is received by the TTC, the dispatcher will contact a TSA watch officer Conference in a carrier representative – verify the event Conference in the appropriate Public Safety Answering Point (PSAP) for the geographic location of the event. Collaborative response/TSI decision process. Assist all parties in managing their response. Initiate a fax of critical information, including a map display to the PSAP. Conference in other response representatives (subject matter expert support) if required. Give the PSAP limited access to this incident through TEAMS. The TTC dispatcher will remain in contact with a TSA representative, carrier representative and/or first responder dispatcher until it is agreed that the all pertinent information has been successfully transferred and there are no further actions required of the TTC. The TTC dispatcher will provide all contacted parties with a call-back number in the event more information or assistance is needed. 24/7 Assistance to the carrier Provide a call in number to assist carriers as required 716) 332-1222.

ACTD: 

ACTD Advanced Concept Technology Demonstration Commercial Vehicle Safety Alliance Volvo Trucks North America Mack Truck

ACTD: 

ACTD Interface one Mack and one Volvo truck with the HAZMAT Truck Security Pilot Truck Tracking Center Vehicle disabling capability based on government-identified critical infrastructure embedded in the vehicle Vehicle wirelessly communicate simulated TWIC data, VIN#, CDL#, USDOT#, HAZMAT material being carried

Other Activities: 

Other Activities Real-Time Vehicle Identification Project License Plate Readers & Weight in Motion Testing Dulles Airport Access Road