Hybrid Cargo Security and Inventory Management Systems (HCSIMS)

1. Hybrid Cargo Security and Inventory Management Systems(HCSIMS) SPAWAR Systems Center - San Diego Technical POC: Mr. Russ Clement Phone 619-553-5433 russ.clement@navy.mil Code 55430

2. Introduction • Deployment and Sustainment of US Forces through Commercial Shipping/Transportation (85-95%) • DoD Contracts with Carriers • DoD implements ITV as shipper. • Department of Homeland Security has Regulatory Authority over commercial shipping to/from US • Inspection of goods at CSI Ports (Container Security Initiative) • Security at US POAs • Customs Fees, Tariffs, Import Levies on goods entering • C-TPAT Agreements (Customs-Trade Partnership Against Terrorism)

3. Impetus for Automated Cargo Security • US Congress has mandated inspection of all Container Cargo • Commercial and Military Cargo Container Visibility • The Department of Homeland Security (DHS) has released the Requirements for Automated Cargo Security - Dec 2007 . (http://www1.fbo.gov/spg/DHS/USCS/PDDC20229/Reference-Number-RFICSD/SynopsisR.html ) • All shippers and carriers will be subject to these requirements. The intent to deploy an open standard device-based network that will provide visibility on all shipments; from point-of-stuffing to point-of-deconsolidation. • Applicability of Current Technology: • Commercially available security devices that meet the requirements will be used to track containers, monitor container security and provide the shippers access to container information. • Secure automated information exchange from the container to the user can be achieved using 128-bit data encryption (significant upgrade over current SOA) • SPAWAR proposes to use this technology for DoD HCSIMS applications.

4. Definition of Terms • Cargo Security – The ability to detect the introduction and/or removal of items into or from a container/conveyance that are not included in the cargo manifest throughout the supply chain. • Weapons of Mass Destruction (Nuc, Chem, Bio) • Contraband (Drugs, firearms, etc…) • Pilferage/damage location/responsibility • Point-of-Stuffing to Point-of-Deconsolidation • Regulated service provided by carrier or container owner • Inventory Management – The ability monitor the presence of items that appear in the cargo manifest and to their movement through all or portions of the supply chain. • Items are usually “tagged” by shipper (Walmart, DoD Etc…) • DoD heavily invested in ISO 18000-7 (active RFID) • Moving to passive RFID • Service provided by shipper

5. DHS-Regulatory Authority Department Roles and Needs • Both organizations address their functional needs using tailored communications and identification technologies. • These technologies can be in conflict in operational requirements, functionality and specification. • HCSIMS provides a solution to these conflicts. DoD - Commercial Shipper Commercial Carrier

6. Dual Development Paths to HCSIMS DHS • ACSD/CSD Requirements • Standards Based • Non-proprietary • IEEE 802.15.4 Comms • Field Validations on-going • Add-on Sensor Bus • Cargo Health • Inventory Management • Certified Vendor’s List • Functionality • Environmental • Read Team DoD • RFID III • Standards-based • Proprietary (license-able) • ISO 18000-7 • Security Device RFP (2008) using DoD Requirements • Functionality • Environmental • Read Team CONFLICT CONFLICT

7. Dual Path Conflicts • Standards-based Non-proprietary Hardware – No License Required. • Security Message Handling • Must contain data fields identified by DHS • Security message cannot be changed by altered by service provider • End-to-end Acknowledgements • DHS Wireless Frequencies • 2.4 Giga Hertz - maximum global availability of trade partners • On-container devices must operate in unlicensed ISM band. • Data Rich Logs not supported by RFID III • DHS Encryption Requirements • 128-bit AES • Application Layer Encryption • User Authentication • DHS Intrusion Detection Requirements • Both Doors - Six Sides • Submit to DHS Validation Testing

8. DHS ACSD Network Automated Cargo Security System

9. US Policy and Mandates • One of DHS highest priorities is to secure the global supply chain. Securing the integrity of cargo as it moves through the global supply chain is vital to our nation’s security. • The ACSD Requirements ensure full integration into the current shipping infrastructure without impacting cargo operations. The ACSD Requirements are consistent with the CBP polices and procedures in place such as: the (CSI) Container Security Initiative, In-bond polices, etc. • The purpose of the ACSD is: to monitor for, in-transit container breach, and to support shipping security from the point of arming – point of stuffing - to destination. • The ACSD target is the ISO 688 dry freight containers used for maritime transit.

10. Impact of Policy and Mandates • DHS policies and requirements will have a universal effect across all shipping lanes and US trade routes. Global application expected with CTPAT trade partners. • ACSD Requirements based on open commercial standards and are a result of collaboration with multiple Federal Agencies (Commerce, Justice and Department of State) and industry trade groups. • ACSD strategy is based on value-added component to shippers and customers including commercial options for security, tracking, health monitoring and inventory management. • Open standard approach expected to result in higher degree of competition – lower costs and better service.

11. ACSD Network Overview • Components to the ACSD System • ACSD • Network Access Device • Data Center - gateway to the CBP (Customs Border Protection) servers. • ACSD Device (on-container) • Intrusion Detection Device (both doors, sides, ceiling and floor). • Bi-direction communications device • Add-on Sensor Bus • Network Access Device (Fixed and Handheld) • ACSD wireless connectivity via IEEE 802.15.4, Cellular and Satellite • Data Center connectivity over untrusted networks (IP, Cell) • Stores ACSD Data, records alerts, directs DHS to suspicious containers • Maintains end-to-end encryption (128-bit AES).

12. Data Center (DC) or DCP Terrestrial or satellite LAN/WLAN s with connectivity to Data Center(s), optionally via a local/regional DCP/gateway. Encrypted secure messages are forwarded verbatim to the host nation’s security center, and vice-versa. Data Centers may interoperate to collaborate. NAD NAD NAD NAD Container Container Container Container Container Container Container Container Container Public Network Extension to Battery-powered Nodes Each Container is a Battery Operated Node NAD = Network Access Device

13. ACSD Deployment • DHS Approved Vendor’s List • Evaluate availability of commercial devices to meet requirements • Describe process for operational readiness testing. • Test Phases • Technical Review, • Technical Evaluation & Laboratory Testing, • Operational Testing, • Large-scale Operational Field Testing. • Testing • Supply chain scenario truck transit into US Port • West Coast In transit maritime In-bound via Transportation & Exportation, • East Coast In transit maritime In-bound via Transportation & Exportation • Maritime scenario from Secure Freight Initiative port

14. Device Tracking and Hierarchy for HCSIMS Concept

15. Denotes Shipper Responsibility Tracking DoD Containers. Premium Intermodal Tracking Services -Provided by Vendor via Satellite, Cellular and/or ’15.4 Links Additional services for added cost Base LineIntermodal Tracking Services - Required by DHS via RF-IP Link for all containers, for all shippers

16. Commercial Container Management SystemViews from a common Web Browser. Domestic container tracking history Container information indicates commodity as “Fish” Status sensor spike and location of alarm

17. Shipping Command and Control Spiral II Add DoD Command & Control for tracking and monitoring Spiral I Commercial Web Browser for tracking and monitoring Advanced Field Artillery Tactical Data System (AFATDS) C2PC with Effects Management Tool (EMT) SSC-SD Asset (Container) Visualization & Data Management System RFID: MSL-UID Global Command and Control System

18. Current Tracking Compatibility In Transit Visibility via the Electronic Data Interchange (EDI) “Cloud”: Point of Deconsolidation Point of Stuffing “Warehouse” US Army Logistics Other Gov Logistics US Navy Logistics US Air Force Logistics Other Supplier Vender US Marine Corps Logistics Commercial Manufacturer • DHS Tracking: • Tracked to last gate, or continuous • Need to carry the MSL data sets • Security options 128-bit (+) encryption • Need ability to display tracking data in Service Specific formats Other Service Component Federal Supply Center

19. Google vs. C2PC Commercial Web Browser for tracking and monitoring Add DoD Command & Control for tracking and monitoring

20. Event Log Event Records - Event # , Event Type, Event Data , CSD Status Message Time , Date , CSD ID, CSD Status • CSD Status Change • CSD Status • Self Test Findings • Fault Code • Reader Command • Reader ID Unrestricted Status , Restricted Status • Failure • Fault Code • Configuration Id • Manufacturer, Hardware#, Trip Information , Operating Mode Firmware# Container ID , Mech Seal ID, Manifest ID, CSI, POA, ATC Deactivated/Armed Alarm Status, Door Status Legend – Blue Text Unsecured Data (i.e. Unencrypted) No Alarm/Alarmed – Red Text Secure Data (i.e. Encrypted) No Underline – Entries Door Open/Door Closed Underline – Collection of Entries Levels of Security • 128-bit AES Encryption Key for DHS Security Data • Commercial Services Data Can be Encrypted as Needed • Premium Services Option, increased Security to 256-bit encryption, (a non-exportable technology option)

21. Leveraging RFID Investment • Development and deployment of ACSD Network will change cargo security and inventory management for all shippers. • ACSD network based on non-proprietary commercial technologies. • Options to levels of above basic security as cost-based services • Compatible and complementary with existing logistics models • Asset tracking visibility through Google (or others) or existing Command and Control Systems. • SSC Goals in Working with both DHS and DoD • Develop technology path to leverage DoD RFID Investment over ACSD Network. • Establish platform and requirements for AIT/ACSD integration • Identify friction points between commercial model and military requirements.

22. ATS Gateway Reader ATS Meeting Expeditionary Requirements FY09 ACSD Technology Transfer under RDCMS – Munitions Storage and Transport Railcar or Bunker/magazine Munitions Storage Facility Command Center Secure Area Geo Fence Coverage Non- Secure Area • ACSD to Monitor Railcar Security • ACSD Comms/Network for Chain of Custody and Inventory Management • IATT for Network Security • NOSSA/HERO Testing Public Rail or Roadway

23. ACSD On-Container Devices • ACSD Sensor • ACSD Comms Module • Location determination - GPS • IEEE 802.15.4 @ 2.4 GHz • Cellular Communications • Add-on Sensor Interface • Application Layer Encryption (128-AES) Port or Ship Gateway • Communications between Tags and Operations Centers • Ethernet, Cellular, Satellite Options • Long-range (1-2 Kilometers) Data Distribution Node (DDN) • Web and database server • Open interfaces for data fusion • Display data, event notification • Remote commanding - Geofence Add ACSD Here Enabling Technologies

24. SPAWAR Role in HCSIMS Development • SPAWAR is a technology lead supporting development of open international standards for container and cargo security for DHS. • SPAWAR provides technology and system development oversight that includes near real time container tracking in support of Maritime Domain Awareness. • SPAWAR is a technology lead in development of existing tactical data and C2 systems for the Marine Corps and Navy. • SPAWAR is the system developer for RDCMS field and operational demo supporting Naval Infrastructure Command.

25. Summary • DHS continues to conduct demonstrations proceeding to deployment of ACSD network for Automated Cargo Security • The ACSD Network is designed to be used as a HCSIMS. • DoD is developing its own HCSIMS under RFIDIII/CSD • ACSD Network and DoD RFID III HCSIMS concepts are currently not compatible. • DHS Solution must be Standards-based and Non-proprietary for global application.