so sofw fwer erx j4 4 gl glo supp o supply ly ch chai ain
play

SO SOFW FWER ERX J4 4 GL GLO Supp O Supply ly Ch Chai ain n - PowerPoint PPT Presentation

SO SOFW FWER ERX J4 4 GL GLO Supp O Supply ly Ch Chai ain n CC CCE E So Solution lution Sl Slid ides es 19-20 March GROUP 1 SLIDES Received 3 votes Path Forward (Group #1) Initial S t e p s : (select f i v e or more critical


  1. SO SOFW FWER ERX J4 4 GL GLO Supp O Supply ly Ch Chai ain n CC CCE E So Solution lution Sl Slid ides es 19-20 March

  2. GROUP 1 SLIDES Received 3 votes

  3. Path Forward (Group #1) Initial S t e p s : (select f i v e or more critical limitations to overcome or opportunities to leverage) CDRSOCOM requests SecDef sign memorandum to data owners (Program O f c e s ) directing • opening access to data sources via publicly available web service. Programs that do not support web service are directed to implement web service capability within 180 days. • CDRSOCOM requests support for this efort from the other CCMDs, Services, an d CSAs. Solution Approach: (describe major solution steps to completion) Develop mission/commodity d e m an d matrix (LEW, OPLOG, Planner) • Determine list of commodity/movement databases a n d get authorizations to connect to • the databases Logistic Support Analysis GUIDevelopment • - GUI to enter commodity d e m an d s, pre-flled with information from f i r s t bullet • Build (or connect) to Transport Feasibility Analysis Capability Develop the Concept of Support • Display • Tool Should Ask for: Mission Type, PAX, Location, Preferred Movement Mode, Commodity • Demands, Begin/End Dates/Times, Equipment Required, Berthing Tool should query d atabased to check for availability a n d cost of identifed mission • requirements Tool returns various options to meet requirements or f n d s no solution a n d forces • a m o d i f e d input. If its G2G, user c a n press approve a n d kick o f approval processes a n d m a ke reservations

  4. Path Forward (Cont.) High Level Timeline (w/milestones) SOFWERX r e a ch e s out to CCMDs, CSAs, a n d S e r v i ce s ( D + 3 0 d a y s ) Identify d a t a • sources a n d g a i n a c c e s s to utilize ( D + 6 0 d a y s ) • B e g i n Building the Tools ( D + 1 8 0 d a y s ) Deliver initial capability ( D + 3 6 0 d a y s ) • End State Description – • Initial functioning application that is able to plan and reserve movement (air, land, • sea) and input requirements (Classes 1-9) into appropriate systems (DLA, USTRANSCOM, etc). Application should be platform agnostic. • System provides feedback to user on feasibility, cost, and timelines. Also provides • approval mechanism.

  5. GROUP 2 SLIDES Received 7 votes

  6. Path Forward > SOF-FIT Initial Steps Acquire direction, guidance and funding from OSD Need buy-in and full participation across the spectrum of stakeholders/JLENT Complete understanding of capabilities and tools used today, with process maps for each (C) Establish data layer for cross-domain access, to include CLASS, UNCLASS and commercial High Level Timeline Detailed requirements document > C+2 months Initial prototype/pilot > C+6 months Completed application > C+12 months  

  7. SOF-FIT Identify Universe of Data Assumptions: ML/AI Authority Determine best Populate Historic Info/Data Funding • Options based Actuals for Consumption • on Parameters Direction Future Planning Factors • of Operation Joint Pubs ML/AI • Application Layer (Front End, User Interface) Analyze Feedback External Partner Concept of (i.e. DLA,USTRANSCOM , Retail) Support Conducts supportability analysis, Risks, etc. Action: Approve action Demand signal Alternative action Revise parameters

  8. GROUP 3 SLIDES Received 8 votes

  9. Path Forward Group # : 3 • Initial Steps: • (select f v e or more critical limitations to overcome or opportunities to leverage) 1. Build a visualization and planning tool on top of existing processes 2. Existing functions are efective but SOCOM has no ability to use them a s a planning tool. 3. Utilize a program like Sofwerx to rapidly prototype an application which captures movement and required supply items. 4. Select a specifc subclass of supply for the prototype 5. Interface with other systems to geospacial display supply type with stocking levels, sourcing options, allow the user select and build list of requirements 6. Submit that list of requirements to an AI function which will provide prioritized options for distribution that the planner can pick from 7. System produces a COS Shell that can be edited (shopping cart) and submitted for ultimate sourcing.

  10. Path Forward (Cont.)

  11. Path Forward High Level Timeline (w/milestones) • 15 d ay s develop initial project request • 15 d ay s SOFWERX finalizes program participation 15 d ay s soliciation period • 30 d ay s prototype development • 15 d ay s initial feedback/protoype adjustments final presentation of prototypes End State Description – Ultimately, the SOCOM planner will enter an application which looks and feels like Expedia. They will enter funding information, a s well a s people a n d material movement requirements (from/to, when, where, etc.). The system will interface with TRANSCOM systems to develop a n initial movement plan. • The SOCOM Planner would then be able to review a layered m a p of relevant supply available in the destination area with the ability to develop a pick list or “bill of materials”. The application will then develop a set of recomendations/options for distribution of that material through TRANSCOM systems, a s well a s a n initial COS (with linkages to previous submissions to locations in the area). The initial COS would be editable a n d once completed by the planner would be submitted to a g e n c y POC’s for processing with relevant contact information .

Recommend


More recommend