Integrating PBL into DoD Supply Chain Management

9
Integrating PBL into DoD Supply Chain Management Logistics Data & IT Solutions 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 Defense Logistics Information Service

description

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. - PowerPoint PPT Presentation

Transcript of Integrating PBL into DoD Supply Chain Management

Page 1: Integrating PBL into DoD Supply Chain Management

Integrating PBL into DoD Supply Chain Management

Logistics Data & IT Solutions

PBL NSN IPT

Hart-Dole-Inouye Federal Center74 Washington Ave N Suite 7Battle Creek, MI 49017-3084www.dla.mil/dlis

(269) 961-DSN 661-

FAX (269) 961-EMAIL: @dla.mil

Defense Logistics Information Service

Page 2: 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

Page 3: Integrating PBL into DoD Supply Chain Management

3

Alternative Approaches

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

Page 4: Integrating PBL into DoD Supply Chain Management

4

Routing requisitions

Routing decode table; FLIS, DAAS, or legacy

New MOE Rule, MOE Code, activity code, SOS codes 1,2 2

Alter or create new Level of Authority; FLIS, legacy

Weapon System (or PBL) indicator code N/A

Issues / Impacts M-SOS M-NSN

1 – finite # of MOE Codes; recurring need to program each new MOE/act code2 – recurring need to identify/define new SOS codes

Page 5: Integrating PBL into DoD Supply Chain Management

5

NSN Maintenance over Life Cycle

Data incompatibilities:

- Reference data control / changes

- Other: reparability, characteristics, CSI, source control,...

N/A

Segregation of management data by platform/service (multi-CMD)

N/A

Control/tracking of Items of Supply N/A

Policy change (Multiple NSNs) N/A

Issues / Impacts M-SOS M-NSN

Page 6: Integrating PBL into DoD Supply Chain Management

6

Other Issues?

Receipt/storage/disposal of property

(inadvertent mixing stock, Due Out Release, FOB,

DEMIL …)

Issues / Impacts M-SOS M-NSN

Page 7: Integrating PBL into DoD Supply Chain Management

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• ???

Page 8: Integrating PBL into DoD Supply Chain Management

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• ???

Page 9: Integrating PBL into DoD Supply Chain Management

9

Charting the Way Ahead

Comments From Services:• Multiple Source of Supply

– AF?– Navy?– MC?– Army?

• Multiple NSN– AF?– Navy?– MC?– Army?

• Other Options

Multi SOS

Multi NSN

Other Options

YOU ARE

HERE