1. Wednesday, September 29, 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  Action Item Review  BECCM COI Road Map Review  “Address” Topic Status Update  “Program” Topic Discussion –WSLM Update on Acquisition Program –HRM Update on Program  UoM Business Case Update  UoM Technical Syntax Phase Status Update

3. 2 Action Items August 31, 2010 1. HRM will escalate the Program Topic to BECCM COI when their CBM process is complete. Open 2. DPAP representatives will submit comments on Heat Map and P2P by Wednesday, September 8, 2010. Closed 3. Jerry Cole will prioritize the most critical comments received in regards to the UoM Business Case before the September 14 th meeting. Closed 4. Jerry Cole is to identify technical SMEs for the Technical Phase Working Group by Friday, September 3rd. Closed

4. 3 Action Items July 29, 2010 5. BECCM COI Staff is to split the heat map lane into several lanes in the BECCM COI Road Map: one for each heat map. Heat Map iterations are to be broken out on the road map. Closed 6. Jerry Cole will host a meeting for a “Standards Content Review” for O2C. Closed 7. CBM COIs are to designate a representative to participate in the “Standards Content Review” for O2C. Closed 8. John Garbarino is to release the UoM Business Case to the BECCM COI membership for comments/coordination. Closed 9. BECCM COI Members are to respond with comments to the UoM Business Case by August 20, 2010 to Jerry Cole. Closed

5. 4 Action Items June 24, 2010 10. WSLM is to present APUID and Milestone B at the September BECCM COI meeting as an information update only. Open May 24, 2010 11. “Address” Escalation: Craig Adams will brief the BECCM COI at the August meeting on the URISA conference. Closed 12. “Address” Escalation: Kick off an Address Working Group in September. Open RPILM will brief BECCM COI in October on the pending Federal standard; escalation to BECCM planned for November. March 29, 2010 13. BEA is to cross-reference 8.0 BIPs with 15 E2Es.Closed

6. Assess Topic 5 BECCM COI Road Map FY10 AprMayJunJulAugSepNovDecJanFebOct TopicLeadDescription Unit of Measure DCMOStandard for describing the way something is measured Address RP&ILMStandard for setting and formatting an address Program HRMStandard for establishing the meaning of program Heat Map 2: P2P DCMO1) Develop methodology and criteria for assessing BEA standards content from an E2E perspective; 2) Assess P2P Minimum Data Standard Heat Map 3: O2C DCMOAssess O2C BEA standards content from an E2E perspective Heat Map 4: H2R DCMOAssess H2R BEA standards content from an E2E perspective Ad-Hoc Action Items BECCM COI Members & Attendees Action items assigned during the course or BECCM COI meetings FY11 Today EP&I brief on CBM COI architecture meetings Update: Address Conference Establish Address WG WG to brief business case EP&I to brief on BEA 8.0 BIPS Address Information Plan HRM CHRIS brief Legend IFA Assessment Completion Functional Approval Heat Map Briefing H2R Planning Summit Official Initiatives Planned Initiatives Informational Discussions and General Business Actual BECCM Escalation Estimated BECCM Escalation Milestone Actual BECCM Exit Estimated BECCM Exit Associated Action Item Heat Map Methodology Defined Comments Due BEA Workshops O2C Deep Dive Workshop w/DLMSO Informational Brief: APUID Status Update Brief Federal Standard Sub-Milestone Tech Syntax Phase Approval P2P Deep Dive BEA Workshops Comments Due H2R Workshop

7. “Address” Topic Update for the BECCM COI 29 Sept 2010 6

8. Current Status Numerous applications have been identified that use various address related attributes Purpose is to identify all DoD Communities of Interest (COIs) with a major stake in address standards Holding introductory discussions with those COIs identified as having a major stake in address standards e.g., Military Postal Service Agency, Distribution Data COI, Emergency Services COI, etc. Developing draft working group documents 7

9. Next Steps Schedule the leader of the draft FGDC standard workgroup to brief the BECCM COI in October Continue preparation to formally present topic to the BECCM COI in November BECCM COI to decide whether to establish a working group or not Initial drafts of the following will be presented for comment and review Working group creation memo Problem statement Proposed objectives 8