GFP Management Update Mr. Samuel Perez Headquarters, U.S. Marine Corps, LPC-2

1. GFP Management UpdateMr. Samuel PerezHeadquarters, U.S. Marine Corps, LPC-2 2 February 2011

2. Situation • OSD changed policy for definition, accountability, and reporting of GFP • Policies are inconsistent – Being addressed at all levels. • Engaged with OSD DPAP, SYSCOM, LOGCOM

3. GFP Management • Goal: Integrated Finance – Logistics – Acquisition Data to effectively track all GFP throughout the enterprise

4. Simplified USMC GFP OV1

5. Current GFP Processes Manual disconnected process with NO enterprise visibility

6. Gaps in Process • Enterprise visibility or control – DoD/USMC • Manual operations required to transfer GFP • “Hidden Stores” – • Inconsistent handling of GFP • Acquisitions Visibility – Contract Language

7. Changes in USMC GFP Policy • Will require equipment to be resident within DPAS/GCSS-MC and serially tracked to be selected to transfer to Contractor • Requires that contract information under which the property was purchased. • Require NSN and Serial Number/IUID on all GFP transfer transactions • All GFP transfers will be initiated and receipted for within WAWF • Contractor Logistics Support items will be tracked under GFP

8. Future GFP Transfer 856 856 856 856 856

9. Future State of GFP Transfer • Utilize DPAS to manage GFP • Until GFP capability within GCSS-MC (Increment 2 delivery – FY 2012) • Initiate property transfer for GFP in Wide Area Work Flow (WAWF) • Upon receipt by Contractor • Automatically updates DPAS to show GFP • Automatically updates DOD IUID Registry • DoDAAD key to this process • Initiate property transfer back to Government in WAWF • Show latest GFP equipment accountability status in the Enterprise Asset Posture tool (TLCM-OST)

10. New Acquisition

11. New Acquisitions • Capturing DLMS transactions to show visibility of “Due In” quantity in legacy and Enterprise Asset Posture (TLCM-OST) tools: • Mapping 856 ASN from WAWF to capture pending shipment status • Mapping 861 Acceptance from WAWF to show updated asset status • WAWF data feed is completed for 856/861 • Working to capture Procurement Data Standard (PDS)/DLMS) from SPS into USMC MDR/GCSS-MC • Building visibility into Legacy apps and TLCM-OST tool • Automatic update of • DPAS • IUID Registry

12. GFP Transfer • Received CAMS-ME export • Created DPAS load file from the following Marine Corps systems/fields: • Total Force Structure Management System • Item Exit Date • Program Office • Manufacture • Cage Code • Part Number • Model Number • Temporary Data Storage (TDS) • UII • SASSY/Stock Control System (SCS) • Marine Corps Serial Number • SABRS • Fund Code • DPAS Load Dates • August 25, 2010 - To DPAS test environment • File has been sent to DPAS • October 1, 2010 – To DPAS production • Load gives the Marine Corps the ability • to perform GFP transfers in WAWF for items with an IUID • To track/report GFP in DPAS • NGEN (C4) • Widest application will be utilized

13. Proof Of Concept • Demonstrate GFP transfer using WAWF and DPAS • Contractor will acknowledge receipt of item in WAWF • Contractor will transfer item back to Government using WAWF • Government will acknowledge receipt of item in WAWF • DPAS will identify item location: NSN, Serial Number, IUID, DoDAAC and allow for enterprise reconciliation and validation of GFP.

14. Proof of Concept • Selected 59 Radar Contract • AN/TPS-59 • M67854-10-D-2200 DODAAC L03538 • Coordination with contractor • Pending final DPAS data lay down.

15. PEI LUE Steps (1) • MARCORSYSCOM PM notifying MARCORLOGCOM MCA that a piece of government property will need to be transferred to Lockheed Martin, Syracuse(Contract Number M67854-10-D-2200) • The notification will take place via an email from the PM or designee • The MCA will review the contract to determine if the piece of property is identified within the contract • The MCA will approve the transfer, and initiate the property transfer using WAWF Web Interface • LM Syracuse will receive a property transfer notification from WAWF that the property is to be transferred • A Due In will be established in SCS for the item being transferred. • DLA Albany will ship the GFP to LM Syracuse

16. PEI LUE Steps (2) • Upon receipt of the property , the property person at LM Syracuse will acknowledge receipt of the property using the WAWF Web interface • Acknowledgement in WAWF updates the DPAS record with the contractor DODAAC based on the WAWF property transfer notice and ship to DODAAC • The acknowledgement will also notify LOGCOM of acceptance of the GFP so that a receipt can be ran to close out the shipment • The contractor will initiate a property transfer within WAWF and ship equipment back to LOGCOM (DODAAC MMSA01) • LOGCOM will be notified of shipment via email from WAWF • Upon receipt of equipment at LOGCOM, LOGCOM will induct a receipt transaction in MOWASP • Increments equipment QTY count in inventory • Closes the due in with in SCS • LOGCOM will accept equipment within WAWF to close GFP xfer • Contractor will be notified via email from WAWF that acceptance occurred

17. Lifecycle Posture Visibility

18. Recommendations • Continue with LUE tracking Secondary Repairable • Draft MCBUL to support adding Secondary Repairable as GFP • Draft policy for addressing GFP that is classified (example: EPLRS radios) • Investigate process and conduct LUE for tracking warranty information when GFP is sent for repair • Display GFP data in enterprise wide application • Continue coordination with OSDDPAP.

19. Questions ?