1 / 13

Supply – Transportation Interface by Heidi Daverede

Defense Logistics Agency. Supply – Transportation Interface by Heidi Daverede. Briefing for : Supply PRC April 10, 2008. Background. USTRANSCOM Information Data Flow IPT (July 24-25, 2007) Identified several “air gaps” as systems hand off data to one another Problem:

khuyen
Download Presentation

Supply – Transportation Interface by Heidi Daverede

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Defense Logistics Agency Supply – Transportation InterfacebyHeidi Daverede Briefingfor: Supply PRC April 10, 2008

  2. Background • USTRANSCOM Information Data Flow IPT (July 24-25, 2007) • Identified several “air gaps” as systems hand off data to one another • Problem: • Manual processing by downstream system • Decrease data quality due to human intervention • Increase processing time due to manual work • Chartered Standard Transportation Interface sub-IPT to document gaps, identify standard transactions and propose “way ahead” • Standard Transportation Interface sub-IPT (August 2007) • Top priority gap: lack of seamless interface between retail supply and transportation systems at origin • Need two-way standard interface for supply receipt and acknowledgement • Pre-lodge release order (material, disposal, and lateral) data to transportation • Allow for supply follow-up requests and status responses • Allow for cancellation requests and associated acknowledgements • Provide material release acknowledgements to supply • Provide flexible solution set for legacy and DLMS compliant systems • No changes to legacy retail supply systems • Use existing transactions to maximum extent possible

  3. Project Participants

  4. Retail Supply Warehouse (e.g., DMLSS) Transportation Docks (e.g., CMOS) Virtual Warehouse

  5. DLMSO Approach • Two-phases: • Phase I: Stock transactions (e.g., DD1348-1A) • Phase II: Non-stock transactions (e.g., DD1149) • Initial focus is on Phase I • Commence Phase II analysis in Summer 2008

  6. Phase I Approach • Identify data requirements • MILSTRIP guidance • Interface agreements (general cargo, ammo, medical) • Identify candidate DLMS EDI/XML • Perform gap analysis • Develop near & long term courses of action (COA) • Near-term: Use DAAS to provide interim capability without impact to supply domain • Long-Term: Fill gaps via PDC/ADC and implement in Service ERPs and other DLMS-compliant systems

  7. 1. Release Order (DS 940R) DLSS A2_, A4_, A5_, A5J Retail Source of Supply AIS Retail TMO AIS 2. In-check/Hold Status (DS 945A) DLSS AE6 5. Shipment Notification (DS 945A) DLSS AR0, ARJ Functional CONOPS(Normal Process)

  8. Retail Source of Supply AIS Retail TMO AIS 3a. Status Inquiry (DS 940R) DLSS AF6, AFJ 3b. Status Response (DS 945A) DLSS AE6, AEJ Functional CONOPS(Status)

  9. 4a. Order Cancellation (DS 940R) DLSS AC6, ACJ Functional CONOPS(Cancellations) Retail Source of Supply AIS Retail TMO AIS 4b. Order Cancellation Response (DS 945A) DLSS AE6

  10. 1.Release Order (940R) Retail Source of Supply AIS Retail TMO AIS 2. In-check/Hold Status (945A) 3a. Status Inquiry (940R) 3b. Status Response (945A) 4b. Order Cancellation Response (945A) 4a. Order Cancellation (940R) 5. Shipment Notification (945A) Functional CONOPS(Overall) Designated transactions are still under review and are subject to change based on data requirements and gap analyses

  11. 1.Release Order (940R) Retail Source of Supply AIS Retail TMO AIS 2. In-check/Hold Status (945A) 3a. Status Inquiry (940R) 3b. Status Response (945A) 4b. Order Cancellation Response (945A) 4a. Order Cancellation (940R) 5. Shipment Notification (945A) Proposed COA(Near Term) Existing MILS, EDI, XML, flat file formats Standardized DLMS formats DAAS

  12. 1.Release Order (940R) Retail Source of Supply AIS Retail TMO AIS 2. In-check/Hold Status (945A) 3a. Status Inquiry (940R) 3b. Status Response (945A) 4b. Order Cancellation Response (945A) 4a. Order Cancellation (940R) 5. Shipment Notification (945A) Proposed COA(Long Term) Standardized DLMS formats DAAS

  13. Status • Identify data requirements • Identify candidate DLMS EDI/XML • Perform gap analysis • Develop near & long term courses of action (COA) • Deliverable to USTRANSCOM/DTEB (April 2008) • Conduct work group meeting with stakeholders to review analysis • Validate criticality of gaps • Finalize COA • Submit required Proposed DLMS Changes to DLMSO/Supply PRC to fill critical gaps

More Related