1 / 9

Integrating PBL into DoD Supply Chain Management

Logistics Data & IT Solutions. Defense Logistics Information Service. PBL NSN IPT. Hart-Dole-Inouye Federal Center 74 Washington Ave N Suite 7 Battle Creek, MI 49017-3084 www.dla.mil/dlis. (269) 961- DSN 661- FAX (269) 961- EMAIL: @dla.mil.

rosetta-ardill
Download Presentation

Integrating PBL into DoD Supply Chain Management

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. Logistics Data & IT Solutions Defense Logistics Information Service PBL NSN IPT Hart-Dole-Inouye Federal Center 74 Washington Ave N Suite 7 Battle Creek, MI 49017-3084 www.dla.mil/dlis (269) 961- DSN 661- FAX (269) 961- EMAIL: @dla.mil Integrating PBL into DoD Supply Chain Management

  2. PBL Challenges • Changing Acquisition Environment • Existing DoD Supply Chain Management Systems and eventual implementation of ERP solutions • Joint-service PBL programs • Multi-national involvement in purchase and production • Ensure interoperability, integration and integrity of data NOTE: Common items are any item which will be managed by both DoD and a PBL contractor

  3. Multiple Source of Supply (SOS) - Services order through existing systems and processes and information is in place to allow DAAS to automatically route requisitions to appropriate SOS Multiple NSN - Assign NSNs to PBL managed Items of Supply separately from existing DOD managed items NOTE: Common items are any item which will be managed by both DoD and a PBL contractor Alternative Approaches

  4. Routing requisitions Issues / ImpactsM-SOS M-NSN 1 – finite # of MOE Codes; recurring need to program each new MOE/act code 2 – recurring need to identify/define new SOS codes

  5. NSN Maintenance over Life Cycle Issues / ImpactsM-SOS M-NSN

  6. Other Issues? Issues / ImpactsM-SOS M-NSN

  7. Possible Solution in FLISMultiple SOS • Develop decode SOS table • New coding i.e., MOE code, LOA, SOS, etc. • Design new Total Item Record segment(s) to hold data for each PBL on the single NSN DLIS assessment of impact • Major effort: time, money, expertise Military Service / downstream system impacts • ???

  8. Possible Solution in FLISMultiple NSN • Develop decode SOS table • New coding i.e., MOE code, LOA, SOS, etc. • Develop cross-reference table to link / track NSNs • Develop business rules to control procedures • Obtain OSD approval for multiple NSNs DLIS assessment of impact • Low to Medium level of effort Military Service / downstream system impacts • Customize FLIS output to applicable agency only • ???

  9. Charting the Way Ahead Comments From Services: • Multiple Source of Supply • AF? • Navy? • MC? • Army? • Multiple NSN • AF? • Navy? • MC? • Army? • Other Options Other Options YOU ARE HERE Multi SOS Multi NSN

More Related