Management Control Activity Process for the Army

1. Management Control Activity Process for the Army February 2011 Kerrie Washington

2. Purpose To brief GFP Working Group on updates to Army Management Control Activity (MCA) procedures within the Logistics Modernization Program (LMP)

3. AGENDA • MCA Organizational POCs • Purpose and Objectives of MCA • Key Gaps • MCA GFM • MCA Functionality • LMP MCA Process Flow • Summary

4. Management Control Activity Organizational Points of Contact • Program Design Responsible Officers: • HQ DA: Kenneth Deans (Commercial 703-692-9834) • HQ AMC: Renee Mosher (Commercial 703-806-8894) • Supply Business Team Lead: Ms. Carmen Hess (Commercial 256-955-7130) • Supply Business Area Lead: Ms. Maxine Townsend (Commercial 256-313-4250)

5. Purpose and Objectives of MCA

6. LMP MCA Key Gaps • No automated MCA process exists for Class V items within the Logistics Modernization Program • Mandatory quarterly reports cannot be produced • LMP does not obligate or commit AWCF funded requisitions • LMP cannot capture AWCF expenditures for forecasting and budgeting for MCA requirements

7. LMP MCA Government Furnished Materiel • LimitedMCA operations are performed within the Logistics Modernization Program (LMP) which resides at the U.S. Army Aviation and Missile Command (AMCOM), U. S. Army Tank and Automotive Command (TACOM) and U. S. Army Communications and Electronics Command (CECOM). • Effort is underway to establish ammunition community on an automatic MCA process. The current functionality in our LMP platform for the Joint Munitions and Lethality Command (JM&LC) and other Class V items is validated manually. • We have deployed LMP to all of our Commands. Some of the functionality being used is: • MCA process in SAP can handle validations • MCA table is set up in SAP for all GFM requirement details by contract • Obligation and commitment of SOMARDS funded requisitions

8. LMP MCA Functionality • An MCA table was built in LMP and is designed to provide management data, visibility and validation against wholesale inventories by contractor DoDAACs for authorized material, quantities and funding data of GFM in support of commercial contracts. • Creation of MCA table, X88 header, begins with the receipt of the DoDAAC data from LOGSA. However, this capability is not working correctly in LMP and a trouble ticket has been submitted. • Some of the fields populated on the MCA table are: • DoDAAC • Commercial and Government entity (CAGE) code • Contract /delivery order number and effective date • Contract/delivery order expiration date • An authorized user can create, change, or delete authorized data for a contract • that includes GFM. • A customer order is not deliverable or billable until validation is complete. Its • purpose is to run the MCA validation against the MCA table and return the status • to the SOS.

9. LMP MCA Process Flow DAASC LMP Reject A0A on 16th Day if no Funding available A X 2 Sales order-A0A Sales order-AX1 A X 2 MCA NOT on LMP MCA Validations/Command Checks A X 1 FAILED PASSED AX2 COMMAND/SOS CHECK BLOCK / REJECT A X 1 Internal MCA RIC <> SOS External EXTERNAL MCA RIC not equal to any SOS on LMP MCA RIC = SOS & both on LMP MCA RIC <> SOS & both on LMP FUNDING BLOCK FUNDING BLOCK ZZ BLOCK NO FUNDING BLOCK PR/PO PR/PO A0A DELIVERY & no BILLING DELIVERY & BILLING AWCF/SOMARDS AWCF/SOMARDS SOS REMOVE FUNDING BLOCK REMOVE FUNDING BLOCK DELIVERY & BILLING DELIVERY & no BILLING Specifically Negotiated License Rights (SNLR)

10. Summary • Army continues to update MCA capability within the Logistics Modernization Program • Several gaps have been identified within the LMP MCA process and trouble tickets have been submitted to correct those issues • LMP effort is underway to establish the ammunition and other Class V communities on an automated MCA process