Defense Transportation Tracking System

Mr. Jeff Leitschuh 11 October 2017

2

Transportation University encourages a free flow of ideas. In the spirit of this academic setting, the views of the instructors and

participants are assumed to be their own and not those of NDTA, USTRANSCOM, or anybody's parent organization/company.

Disclaimer

Lesson Objectives

• Defense Transportation Tracking System (DTTS) – Understand the mission of DTTS– Review the capabilities of the Transportation Geospatial

Information System (TGIS) and how DTTS personnel use it to monitor transportation protective service (TPS) cargo

– Overview of DTTS Emergency Reporting procedures– Gain knowledge of issues and challenges impacting effective

TPS monitoring from origin to destination

3

DTTS Structure

4

Program Manager Jessica Snyder

Operations & Quality Branch Jeff Leitschuh

Program Analyst Ben Jensen

Policy & Tech Branch

Marco Boasso

Operations Analysts (9)

Transportation Assistants (3)

Duty Officers (6)

DTTS Mission

• Primary mission is to ensure the safe and secure transport of DoDArms, Ammunition, and Explosives (AA&E) and Other Sensitive Material (OSM) by commercial trucks and barges in North America using satellite/cellular technology and 24-hour oversight

– Facilitate rapid emergency response to in-transit accidents/incidents to minimize impact

– Monitor in-transit movement for security issues via programmed exception reporting

– Provide incident/emergency information for DoD senior leader awareness as required

5

Partners

• Military Services are primary partners, but other agencies receive DTTS tracking support

– Defense Contract Management Agency– Defense Logistics Agency– Nuclear Regulatory Commission– Canadian National Defense Forces– White House Communications Agency– German Air Force– Ministry of Defense (United Kingdom)

6

How DTTS Has Evolved

7

1984

1985

1986

1989

1994

2005

2008

---- Denver, CO – Navy Torpedo Accident

---- Checotah, OK – 2000 lb. Bomb Accident

---- Congressional hearings, NTSB investigations and Navy Commission recommends Navy establish explosives tracking capability

Naval Ordnance Transportation Tracking

System (NOTTS) established---

---- NOTTS expanded to all Services and renamed Defense Transportation Tracking System (DTTS)

USTRANSCOM added in-transit visibility function ----

DTTS mission transferred from Navy to SDDC ----

DTTS operation moves from Norfolk to Scott AFB ----

Critical Tasks

• Monitor shipments via in-transit exception reports• Respond to and validate panic button messages, sensor alerts, and emergency

calls• Notify local authorities (police/fire) if required, and Army Watch Cell (for

incidents involving munitions)• Capture/record pertinent information/data from carrier dispatch, driver, first

responders, shippers/receivers• Initiate incident reports to DoD leadership• Facilitate secure holding and safe haven• Capture shipper and carrier issues for further research/action by SDDC

staff/Service POCs

No tasking authority…relationships are key8

Data

• Typically track between 150-300 shipments per day

• Process nearly 3,000 messages per day

• Manage approximately 30 alert messages per day

• Up to 300 in/outbound phone calls per day resolving shipment issues/gathering data/clarifying responsibilities/monitoring status

• Track down approximately 700 shipments per month with no shipment data loaded in the system by the shipper

• Send out approximately 350 emergency reports per year

9

Roles & Responsibilities

10

Safety

TransportationSecurity

• DDESB• SDDC Safety• Installation Safety• DOD 6055.9-STD• DOD 4500.9-R Part II

Chapter 204• Individual service

regulations

• OSD TP• USTRANSCOM• Military Services• SDDC G3D• DTTS• DOD 4500.9-R Part

II Chapter 202• DOD 4500.9-R Part

II Chapter 205• MFTURP-1• Individual service

regulations

• OUSD(I)• Military Services• SDDC G2• Installation Security

Managers• DOD 4500.9-R Part

II Chapter 205• DOD 5100.76-M• DOD 5100.76-I• Individual service

regulations

TPS

Transportation Geospatial Information System (TGIS)

• Geospatial technology– Secure, web-based GIS data viewer, catalog, and services– Searchable repository of GIS products and services– Integrated mission management applications

• Near real-time information– Worldwide tracking, weather, traffic, and other near real-time information– CONUS tracking & response

• CONUS Mission management– Automated alerts (REPSHIPS, Geofencing, Weather, Panic Button, Lost Signal,

DO/UT on trailers, Movement/Stationary)– Emergency Response – Dashboarding

11

Report/Mapping Capabilities

12

Mapping Capabilities

13

Mapping Capabilities

14

Mapping Capabilities

15

GeoFence

16

DTTS Reports

17

DTTS Dashboard

18

Major Issues

• Advanced shipment planning

• Secure holding vs. safe haven

• Not-In-System (NIS) shipments

• Correct DODAAC/SPLCs

• Confirm operational status of DTTS prior to departure

• Required Delivery Date (RDD) are unrealistic/not used/or not coordinated with destination

19

Advanced Shipment Planning• BLUF – Shipment planning causes TPS shipments to be in the public domain for an excessive

amount of time• Background

– Shippers do not coordinate the delivery of TPS shipments with consignees– Shipments sit in the public domain longer than necessary due to

weekends/holidays/installation closures • Business Practices

– Transportation Officers do not ensure required information is complete/current– Consignor fails to review/comply with the consignee's Transportation Facility Guide (TFG)

special instructions– RDDs are not consistent with standard transit times or no RDD identified– The consignee is not contacted to confirm the ability to receive the shipment– Coordination is not done between the consignee, consignor and the TSP to meet RDD,

destination operating hours, and delivery restrictions• Reference

– DTR CH 205 Para C.2

20

Transportation Facilities Guide (TFG)

21

Secure Holding

Tab

Information can include hours, entry requirements, contact information, and any other

special requirements or instructions

TFG Secure Holding Tab

22

Not In System (NIS)• BLUF – Without shipment information, DTTS cannot provide information crucial to emergency

responders which could impact efforts to protect the public, property and first responders

• Background– An NIS is created when a departure message is received and no bill of lading (BOL) is in

the DTTS system– Policies and business practices may conflict with timely BOL transmission to DTTS– Continued contact with the shippers is VERY time consuming and has minimal impact– NIS numbers continue to increase: 2% of total shipments in 2012 to 16% in 2016, and

already 17% for 2017 as of 28 Aug

• Reference– DTR CH 205 Para O.5.c.

23

DODAAC/SPLC

• BLUF – Some shippers are using invalid DODAAC/SPLC codes when entering shipment information into their respective system causing shipment to be unknown

• Background– Shippers are using generic or invalid codes

• Business Practices– DTTS sees codes such as XXXXXX, installation/unit names in the respective

fields– DLA-Transaction Services updates information in the Defense Automatic

Addressing System Center (DAASC) Inquiry System, shippers do not always verify prior to shipment. DTTS has to manually verify each unknown DODAAC in TGIS

24

Inoperable Satellite Motor Surveillance Service/Trailer Tracking Service (SNS/DCS)

equipment• BLUF – Some TSPs are arriving at pick-up locations with broken/inop equipment. TSPs are often

having issues maintaining 24 hours uninterrupted service.• Background

– TSPs experience a failure while en route and DTTS places drivers on two hour check calls and deregisters the truck

– Some drivers, and shippers believe they can do two hour check calls at origin– SNS systems are often not inspected by shippers– TSP changes SNS system and does not register it with DTTS– The SNS unit is incorrectly wired to truck which causes it to be disabled when the ignition is

turned off– Some TSPs program their SNS to “fall asleep” if truck has not moved in a set amount of time

• References– MFTURP-1, Section B, Item 105, 107– DTR 205 C.2.b.3

25

Required Delivery Date (RDD) & Transit Time

• BLUF – Shippers do not always identify a valid RDD for shipments. Carriers do not always adhere to the RDD, or to the standard transit time, whichever is shorter. This increases public exposure to potentially dangerous materials.

• Background– Shipment planning is often neglected by shippers when planning TPS shipments– Many RDDs are not aligned with published standard transit times– At times, carriers are not adhering to RDDs or transit time– Many RDDs get changed prior to delivery and shippers do not update systems– Shipments must meet the RDD or the standard transit time, whichever is shorter

• References– DTR 202 Tables 202-3 and 202-4– DTR 205 C.2.a and b.– MFTURP Item 5, Figures 5.1 and 5.2

26

Points of Contact• SDDC G3 Freight Routing Team

– usarmy.scott.sddc.mbx.g3-domestic-freight-services-branch@mail.mil– 618-220-6359

• SDDC DTTS– usarmy.scott.sddc.mbx.dtts@mail.mil– 1-800-826-0794

• TGIS Helpdesk– usarmy.scott.sddc.mbx.G6-SRC-TGIS-HD@mail.mil– 1-800-462-2176

• TGIS Accounts– usarmy.scott.sddc.mbx.dtts@mail.mil– 618-220-5305

27

Conclusion

• Defense Transportation Tracking System (DTTS)

– Discussed the background and critical tasks of DTTS– Reviewed the capabilities of TGIS and how DTTS personnel use it to monitor

transportation protective service cargo– Briefly covered DTTS Emergency Reporting procedures– Gained knowledge of issues and challenges impacting effective TPS

monitoring from origin to destination

28

Defense Transportation Tracking System (DTTS)

QUESTIONS?

29

M I L I T A R Y S U R F A C E D E P L O Y M E N T & D I S T R I B U T I O N C O M M A N D