GFM-A_Overview_Briefing_June_2016v1.pptx

Government Furnished Materiel - Accountability (GFM-A) Capability Initiative (CI) Overview Briefing Service Development and Delivery Process (SDDP)

Updated 16 June 2016

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Headquarters U.S. Air Force

Thank you and welcome to the status and way ahead briefing for the GFM-A SDDP Capability Initiative.

Agenda Problem Statement Business Process Reengineering Selected CoA AF APSR Overview PMO/CICP Actions Next Steps Q&A

Here is the agenda for today’s briefing. This slide deck will provide a brief overview of SDDP, talk about where we’ve been and where we’re going. And most importantly your support to make this a success!

GFM-A Step 1, PRM Problem Statement and Capability

Accountability Will provide property accountability / control of contractor managed and possessed government furnished materiel through implementation of standard and integrated AF logistics and contractor processes (from acceptance and receipt to disposition) IAW DoDM 4140.01, DODI 5000.64 and FIAR Guidance. This will establish and maintain accountable inventory records for GFM that reflects current quantity, status, location, condition & authorizing contract; establishing an audit trail to update and track end-to-end logistics and financial transactions. High

This slide contains the problem statement, justification and future capability desired – updated/approved Summer 2014

Selected CoA Approved by Functional Sponsor: 21 December 2015

8/3/2016 The Defense Property Accountability System (DPAS) program is administered by the Under Secretary of Defense for Acquisition, Technology and Logistics, a branch of the Office of the Secretary of Defense The DPAS software application is serving the logistical needs of three major military branches and a significant portion of the Department of Defense. Currently, over 2 million assets, in excess of 672 billion dollars, are being managed by DPAS Currently supports 3 Major Business Areas Property Accountability Maintenance/Utilization Warehouse/ICP DPAS Support Site: http://dpassupport.golearnportal.org

The United States Air Force currently utilizes DPAS for:

Non-Tactical Vehicle Mgmt IT Asset - Pilot

DPAS Overview

Dollars and quantities updated.

DPAS as AF GFM-A APSR PMO began design work: January 2016 IOC planned for First Quarter FY17 Pilot programs to test DPAS functionality Five programs to run for 90 days Assess pilot results for 30 days Adjust as required Begin a phased deployment after pilot program completion Team will work with remaining program offices to determine deployment sequencing

F-22 C-17 Predator/Reaper Launch Test Ranges

DC3GS

KC-10

How DPAS will Operate for CICPs with Interfacing Inventory Management Systems Contractors enter Receipt, Issue, Condition Code Changes, Physical Inventory, NSN Re-Identification, Logistics Reassignment transactions in their inventory management system (or DPAS Self-Service Module) Transactions route through DLA Transaction Services to DPAS DPAS receives, stores and processes transactions for inventory position -- should be a mirror image of CICPs Reconciliation Inventory valuation Aggregate all transactions for financial reporting DPAS sends all transactions/financial data to AF Financial System

Walk through process flow.

CICP Transactions

DLA Transaction Services

DPAS

AF Financial System

Functional View of Information Exchanges

How DPAS will Operate for CICPs without interfacing Inventory Management Systems Contractors enter Receipt, Issue, Condition Code Changes, Physical Inventory, NSN Re-Identification, Logistics Reassignment transactions in DPAS DPAS stores and processes transactions for inventory position -- should be a mirror image of CICPs Inventory valuation Aggregate all transactions for financial reporting DPAS sends all transactions/financial data to AF Financial System DPAS = Self-Service Module

Walk through process flow.

CICP enter transactions

DPAS

AF Financial System

DPAS User Roles (Proposed) AF DPAS PMO User Daily Task List Master Data Management Reports/Queries Transaction Notes/Attachments Request Physical Inventory AF DPAS CICP Delegate Master Data Management Reports/Queries Transaction Notes/Attachments AF DPAS PMO Supervisory Role Notification for untouched task list items AF DPAS Financial Mgmt User Read only access to financial transactions Reports/Queries AF DPAS Functional Owner Read only access Reports/Queries Request Physical Inventory

AF DPAS PMO CO

Read only access Reports/Queries DPAS System Administrator Access Requests Mass data uploads

These are based on current ITFRs, Day in the Life and are notional at this point

Contractor Requirements IT Requirements Defense Logistics Management Standards (DLMS) transactions Interfaces (inbound and outbound) – Establish/Update ICD with DLA Transaction Services Process and Procedures for:

Physical inventory requests Inventory adjustment requests Asset disposal requests Daily/Monthly reconciliation In-transit management Asset valuation

Team will provide document with Requirements and Procedures

PMO Requirements Contract modifications Process and Procedures for Oversight and Control of:

Master data management Physical inventory requests Inventory adjustment requests Asset disposal requests Daily/Monthly reconciliation In-transit management Asset valuation Team will provide document with Requirements and Procedures

PMO/CICP Actions Request to become a CICP (with HAF/A4LR and AFMC/A4R) Get DoDAAC/RIC/SoS codes for contractor Determine and notify HAF/A4LR and HAF/A4PT of decision:

CICP’s Inventory Management System (IMS) will interface to DPAS or CICP will use DPAS as their IMS Work with HAF/A4LR and HAF/A4PT to determine implementation date Begin pre-implementation activities Establish Interface Control Agreement (ICA) with DLA Transaction Services Identify DPAS users and complete training Update IMS to process DLMS Transactions Master data management Physical Inventory Manual CFO Reporting

Next Steps/Way Ahead HAF/A4LR requesting programs to volunteer for Phase 1 Implementation Outreach with Programs and Contractors (July – Aug) Including PMOs, CICPs (and CICP IMS POCs) CSWS Working Group Meeting – 22-26 Aug 2016 @ Andrews AFB

Future Gov’t SME involvement:

Design Questions / Requirements Support – now thru Aug 2016 System Testing – Fall 2016 Phase 1 Implementation – 1st Quarter FY17

Q&A

QUESTIONS

Contact Information Colquitt "Quitty" Lawrence GFM-A Functional Lead

HAF/A4LR

colquitt.lawrence.civ@mail.mil

VOICE: DSN 612.4220 COMM (240) 612.4220

JACK DILLON, PMP, Contractor SDDP CI Lead – GFM-A and ESCAPE Logistics Transformation and Execution Office, HQ USAF/A4PT Directorate of Resource Integration, HAF/A4P DCS/Logistics, Installations & Mission Support john.dillon.2.ctr@us.af.mil

VOICE: DSN 674.0815 COMM (937) 904.0815

FAX: DSN 674.0898 COMM (937) 904.0898

GFM-A Step 2, BRM As-Is Root Cause Analysis

SMEs identified problems with the current processes and areas where they believed improvement was possible during the As-Is architecture development.

To-Be Processes were re-engineered to address the pain points

During the Subject Matter Expert (SME) working sessions to develop the As-Is architecture for GFM-A’s business processes, SMEs were asked to identify problems with the current processes and areas where they believed improvement was possible. These pain points were documented across GFM-A’s business processes to support the Root Cause Analysis (RCA). The pain points’ probable resolution actions were categorized into required Doctrine, Organization, Training, Materiel, Leadership & Education, Personnel, Facilities and Policy (DOTMLPF-P) capabilities. Pain points that had more than one DOTMLPF-P category were placed in all corresponding categories. Many pain points were found to be at least partially resolved through some form of materiel solution. This information was used to support root-cause analysis to help determine the nature of the solution. In summary, the root cause analysis indicates that although the majority of end-user pain points reference deficiencies in the current materiel solution, numerous other DOT_LPF-P actions will be required to fully resolve the problem. These are documented in the DOTMLPF-P Implementation Plan (in next two slides).

GFM-A Step 3:

Define the Solution

Doctrine The way we fight, e.g., emphasizing maneuver warfare combined air-ground campaigns.

Materiel All the “stuff” necessary to equip our forces, that is, weapons, spares, etc. so they can operate effectively.

Contextual Model Web Service Reqmnts COTS/GOTS Reqmnts Compliance Reqmnts Onboarding Reqmnts Onboarding Compliance

Bounded user requirement that includes definition of the materiel solution, information & data sources, & implementation plan Sponsor commitment Approval by AF corporate structure Step 3 Outcome

SRM

COI Charter Information Assets Vocabulary Package Reusable COI Artifacts

DRM

DOTMLPF-P Implementation Plan M-Implementation Plan WBS, RTM, Cost Estimate, CM Plan, Governance, Onboarding Plan, Resourcing Organization How we organize to fight; divisions, air wings, Marine-Air Ground Task Forces (MAGTFs), etc.

Leadership & Education How we prepare our leaders to lead the fight from squad leader to 4-star general; professional development.

Personnel Availability of qualified people for peacetime, wartime, and various contingency operations.

Facilities Real property; installations and industrial facilities (e.g. government owned ammunition production facilities) that support our forces.

Policy Common approaches and procedures..

Training How we prepare to fight tactically; basic training to advanced individual training, various types of unit training, joint exercises, etc.

Completed January 2016

STEP OUTCOMES

Sponsor commitment to implement selected Materiel Solution Approval by Air Force corporate structure to fund / execute the implementation of Materiel Solution Early involvement of platform engineering, network operations to align the infrastructure capabilities with the Materiel Solution requirements Ensure reusability of existing Materiel Solution Capabilities

PRODUCT OUTCOMES

The bounded user requirement that includes definition of the materiel solution, information and data sources, and implementation plan

COI- Community of Interest

Why DLMS and not MILS Demand for information has grown exponentially - inflexible fixed length MILS transactional messages cannot satisfy current requirements.

Senior DOD logistics leadership - modernize information exchange process and formally mandated the dissolution of MILS by 2019 Defense Logistics Management System (DLMS) is the replacement Based on mature American National Standards Institute (ANSI) Accredited Standards Committee (ASC X12) A key enterprise standards in the DOD Business Enterprise Architecture.

DLMS subsumed all the functional capabilities of the MILS and introduced new capabilities not previously possible.

DOD Logistics’ highest priorities depend upon DLMS implementation Financial Improvement and Audit Readiness (FIAR) Supported by the Standard Financial Information Structure (SFIS) and Standard Line of Accounting (SLOA), Strategic Network Optimization (SNO), Item Unique Identification (IUID), Government Furnished Property (GFP), and passive Radio Frequency Identification (pRFID).

Future communications will be in DLMS format by 2019

Built on commercial standards

Post SDDP Step 3 Activities Design review and testing Requirements refinement/evolution Develop implementation schedule for CICPs To include pre-, during and post- implementation activities CICP requirements (next slide) DIP Actions Policy Contracts Leadership Communication/Training Personnel

Day in the Life of a DPAS User

GFM-A DLMS Transactions

Here are the DLMS transactions associated with GFM-A CI

NSN Re-Identification DLMS 832N is used when the entire set of assets are re-identified. Ex. NC or ND number has been assigned NSN.

DLMS 947I is used when only one or some of the assets are re-identified. Ex. NSN 1 is modified and becomes NSN 2.

Users “home-page” will provide notifications for action Provide oversight of CICP activities Day in the Life of a DPAS User

Walk through development of this exhibit and purpose – different lens

Resulted in new and edited ITFRs

System access at DPAS PMO level Master Data management at WS PMO level Day in the Life of a DPAS User

Walk through development of this exhibit and purpose – different lens

Resulted in new and edited ITFRs image2.png image3.emf image4.jpeg image5.wmf image6.wmf image1.png