1. Wednesday, December 8, 2010 Dennis Wisnosky DoD Business Mission Area Chief Technical Officer & Chief Architect in the Office of the Deputy Chief Management Officer Kim Pisall Director, Transformation Priorities & Requirements, Supply Chain Management, Business Transformation Agency BECCM COI Meeting

2. 1 Agenda BECCM COI Road Map Review Procure to Pay (P2P) Heat Map Update Address Status Update HRM Program Status Update Unit of Measure (UoM) Update Action Item Review

3. Address topic assigned to WG BECCM Roadmap OctNovDecJanFebAprMayJunJulMar TopicLead/DomainCurrent Status Unit of Measure Jerry Cole, John Garbarino (DCMO) Developed Final Functional Requirements / Recommendations, Data Analysis & Technical Recommendations; Requirements Package due 30 Dec 2010 Address Jerry Cole, Zack Waltz (RP&ILM) Summary view prepared for FGDC Standard. Coordinated with SCI Program Jerry Cole, Brian Jackson ( HRM/WSLM/ FM ) HRM to present Program definition/recommendation at December BECCM. HRM still holding WGs. FM COI request to be involved with Program initiative Heat Map 2: P2P Jerry Cole, Mark King (DCMO) Weekly workshops for P2P Process Models Heat Map 3: O2C Jerry Cole, John Garbarino (DCMO) Coordinating with SCI and DLA J3/J8 for final O2C scope and minimum essential data elements Heat Map 4: H2R Jerry Cole, Amy Anda (DCMO) Ongoing WG’s between P&RIM, DCMO, BTA addressing Level 1 & 2 Processes Ad-Hoc Action Items N/A Currently no action items IFA Assessment Completion Official Initiatives Planned Initiatives Informational Discussions and General Business BEA Workshops Workshop w/DLA / DLMSO Brief Federal Standard Finalize Minimum Data Standard H2R Workshops Aug BEA 7.2 Content Lockdown BEA 8.0 Update Tech Syntax Phase Approval Approval of Enterprise Data Solution Complete Requirements Package HRM Program WG Stakeholder Review Workshops Q1 FY11 Sep Q3 FY11 Q4 FY11 HRM Definition H2R Workshops O2C BEA 8.1 Pre-Workshops Final Stakeholder Review H2R Workshops UoM BEA 8.1 Pre- Workshops Legend Actual BECCM Escalation Estimated BECCM Escalation Milestone Actual BECCM Exit Estimated BECCM Exit Associated Action Item Sub-Milestone Q2 FY11 UoM BEA 8.1 Workshops UoM BEA 8.1 Update UoM BEA 8.1 Workshops UoM BEA 8.1 Update Status Update UoM Update HRM Program Status Update 2 Approval of Functional Approach HRM Program Informational Brief Informational Brief: Acquisition Program Approval of Enterprise Data Solution Business Vocabulary Alignment Draft Intended Use Cases Draft Technical Results

4. Mr. Jerry Cole BTA Enterprise Standards, Transformation Priorities and Requirements Supply Chain Management Address Status Informational Update 3 Dec 8, 2010

5. 4 Agenda Address Problem Statement - Draft Overview of Federal Geographic Data Committee (FGDC) United States Thoroughfare, Landmark, and Postal Address Data Standard Next Steps

6. Address Problem Statement - DRAFT Government entities define address differently resulting in lack of interoperability Address lacks an enterprise wide data Governance process in DoD Address is a master data concept that should be shared across the DoD enterprise 5 5

7. FGDC Data Standard Overview The Federal Geographic Data Committee (FGDC) United States Thoroughfare, Landmark, and Postal Address Data Standard provides DoD the raw materials that the Functional Requirements will use to build out exchange solutions The FGDC Data Standard will become a Federal Data Standard in February 2011 Currently known adoptees U.S Census Bureau Environmental Protection Agency (EPA) The intent is not to require all systems to store data in the same format. Instead, the intent is to enable each system to exchange information in a common vocabulary This Federal Standard enables the normal BECCM Process to be accelerated 6 6

8. 7 7 Completion Date Milestone 12/08/10 Assign Address to a Working Group 12/14/10Identify SMEs 12/22/10Agreed to Problem Statement and Problem Scope 12/31/10Business vocabulary alignment 01/10/11Proposed Functional Approach 01/18/11Revised Functional Approach 01/31/11Approval of Functional Approach 02/28/11Draft intended use cases 03/31/11Draft technical results 04/14/11Finalize documentation 04/29/11Approval of Enterprise Data Solution Address – Next Steps