Distribution Management Tool Status Update 12/05/12

• Initial focus on distribution network model (group cuts across multiple pillars)

• Primary personnel working so far– TC Falls, MW Farthing, AM Hines, MA Cowan, JL

Hensley• Starting to engage Stuart, Walker on Mobile

Device side

Overview

Purpose: Develop intelligent tools that efficiently schedule,

redirect, and track delivery of shipments from theater distribution hubs to forward units in austere and remote environments

Results: Support for prioritization of onward movement that

leverages and optimizes all conveyance modes, ensures timely delivery, and allows gaining unit to predict arrival

Visibility of shipments between multiple transit nodes irrespective of command level and class of supply

Payoff: Improved capability to tactically transport and reliably

deliver shipments to Forward Operating Bases (FOBs) and smaller satellite bases in remote, dispersed, austere locations

Optimized utilization of Transport Assets and Personnel. Reduced supplier and equipment risk, including improved

efficient and safe methods for equipment retrograde operations

Milestone Schedule and Cost

Milestone FY13 ($K)

FY14 ($K)

FY15 ($K)

FY16 ($K)

FY17 ($K)

Distribution Management Tool

Distribution Modeling

Web/Mobile-Based Tools

Distribution Analytics

Systems Integration

6.2 T40 1143 2628 2700 2600 2000

6.2 T42 355 349

6.3 T08 600 439 436 400 500

Total 2098 3416 3136 3000 2500

Distribution Management Tool

3

63

64

6

ERDC Total$14.1M

54

4 6

Distribution Modeling Pillar

• Technical Lead - Matthew Farthing (50%)• Work Units:

– Distribution Network Model (DNM)• Team Members – Mark Cowan (50%) Jeff Hensley (25%), Amanda Hines (25%)• Product(s) - Distribution Network Model

– Distribution Hub Model • Lead – ITL (100%)• Team Member – ITL (50%)• Product(s) – Yard Tool

• Funding: DNM funded through Dec 31 – Year 350K, Funded 66K, Obligated $33K, Dispersed $33K

• Demo T08: $576K, Funded $87K, $32K, Dispersed $32K

Distribution Modeling Pillar

Distribution Network Model goal is to build discrete network model to simulate logistics distribution network • Integrate dynamic changes in network state given uncertain

environmental conditions, transportation infrastructure, and security conditions

• Calculate optimal routes, distribution schedules given user-specified priorities and objectives

• Predict arrival times and simulate second and third-order effects due to changes in network conditions like route availability

Distribution Hub Model effort will focuses on essentially intra-node distribution processes in order to better predict their impact on transit times and network state• Management of Convoy/Vehicle Manifest data• Load planning/optimization• In-yard spatial location

Distribution Modeling Task List

Initial task list for FY 13-14

Prototyping DNM

• Network Datastructure built on boost graph library– Widely supported template-based, OO, C++, has

parallel (distributed) version• Visual Representation through KML– Logical network – Physical routes– Shipment locations and “trajectories”– Using file-based IO first (databases later)

• Initial test scenarios based on ESC Scenarios

MSRs and Distances Beginning of Phase II

MLS 2.0 IX Corps CONOPS BriefAttica

Messenia

Elis

Laconia

LSA TACOMA

N

FOB MOUNTAIN

MSR GREEN

FOB SALTLAKE

MSR GREEN

MSR GREEN

MSR WHITE

MSR RED

FOB PETERSONFOB

HILL

27 July 2012 MLS 1.0 & 2.0 30 ESC CONOPS Brief

TAA ANZIO

TAA SICILY

TAA NORMANDY

Distances = Road Distance (KM)

819

MSR BLUE

209 745

335348

211

396

10 April 2008 0 100 200 300 400 500 km

500 KMN

Network Model Visibility

Logical network

Physical route shown as more resolution requested

Database Boost Graph Representation KML

Prototyping DNM

• Route, Shipment Optimization via PuLP– Python based library for linear programming, part of COIN-

OR framework – Initial test formulations based on “transshipment problem”

(equilibrium network flow with static edge capacities) • Network Simulation using Simpy

– Discrete event simulator written in python– Simple interface, allows for lag times based on wide range

of statistical distributions– Communicating with Network Representation Using file-

based IO

Prototyping DNM

• Tools for collaboration– Wiki http://134.164.48.118/index.php/LogisticsMantis - – Mantis bug/feature trackerhttp

://134.164.48.118/mantis/login_page.php– Sage server for python based prototyping mathematical

models– https://proteus.usace.army.mil/sage

• Biggest challenge: Translating actual logistics problems and scenarios to properly formulated optimization problems

Distribution Analytics Pillar

• Technical Lead - Matthew Farthing (50%)• Work Units:

– Network-scale Environmental Analytics• Team Members – Mike Follum (50%), McKinley (25%)• Product(s) – Environment Tool (Network-Scale)

– Local-scale Environmental Analytics • Team Member -- Stacy Howington (30%) Jeff Hensley (25%), Nawa Pradhan (50%),

McKinley (25%)• Product(s) – Environment Tool (Route-small unit scale)

• Funding: Network-scale funding will start in Jan 13. Local scale effort will start in FY 14. Hensley and Farthing funded through this unit although focus is on Network Model– Year 300K, Funded 66K, Obligated $28K, Dispersed $28K

Distribution Analytics Pillar

Provide the DNM with accurate estimates for the impact of environmental conditions (weather, hydrology, terrain state, threat) on surface and air transportation routes. – Using combination of remotely sensed data and

modeling– network-scale effort will focus on the effects of weather

and flood potential at the scale of the full logistics network

– Local-scale effort will focus on traffic-ability at finer (small-unit, local crossing) scales

Distribution Analytics Task ListHave an initial task list established for FY 13-14

Distribution Analytics Task List

Decision Support Pillar

• Technical Lead – TC Falls (40%)• Work Units:– Web-Based Planning, Assessment, & Reporting

• Team Member – Benjamin Web (100%) • Product(s) – Visibility Tool (web-interface)

– Mobile-Based Planning, Assessment, & Reporting• Lead – David Stuart (50%)• Team Member - ITL programmer (100%)?• Product(s) – Visiblity Tool (mobile interface)

• Funding: Current Funding for Falls, Stuart• Year 200K, Funded 51K, Obligated $27K, Dispersed $27K

Decision Support Pillar

Focus on user interfaces for the output of the distribution management tool.

• map-based spatially distributed views of the network state with parcel status

• mobile applications suitable for handheld devices, • provide the capability to push logistical information to soldiers

at the squad level operating on the tactical network • Visibility Tool:

– Network Status– Shipment Status– Delivery Reporter– Asset Status

Systems Integration Pillar

• Technical Lead – T.C. Falls (40%)• Work Units:• Systems Integration

– Lead - – Team Member – Mobility Branch (100%), Mark Cowan (50%)– Product(s) – software API document, database schemas,

automated process management tools, common software tools to implement inter-process APIs, software interfaces with external systems and NGWC mesh tags, network data feed simulation tool.

• Funding: Current Funding for Falls, Cowan, Hines– Year 247K, Funded 51K, Obligated $23K, Dispersed $21K

Systems Integration Pillar

Focus on internal– System Architecture, documented APIs, database

schemas

and external integration – TC AIMS-II, NGWC, STAMIS, and SASS

Distribution Network Products

Distribution Network Products

Distribution Analytics Products