1. Tuesday, August 31, 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  BEA 8.0 BIPs  Urban and Regional Information Systems Association (URISA) Conference Review  UoM Business Case Status

3. 2 Action Items July 29, 2010 1. 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. Open 2. Jerry Cole will host a meeting for a “Standards Content Review” for O2C. Closed Meeting held August 10 th 3. CBM COIs are to designate a representative to participate in the “Standards Content Review” for O2C. Closed 4. John Garbarino is to release the UoM Business Case to the BECCM COI membership for comments/coordination. Closed 5. BECCM COI Members are to respond with comments to the UoM Business Case by August 20, 2010 to Jerry Cole. Closed

4. 3 Action Items June 24, 2010 6. BECCM COI staff to confirm with WSLM the status of APUID as an escalation or activity on the BECCM COI Road Map. Closed 7. WSLM is to present APUID and Milestone B at the September BECCM COI meeting as an information update only. Open 8. BECCM COI staff will present Heat Map III: Order to Cash at the July BECCM COI meeting. Closed May 24, 2010 9. “Address” Escalation: Craig Adams will brief the BECCM COI at the August meeting on the URISA conference. Open 10. “Address” Escalation: Kick off an Address Working Group in September. Open March 29, 2010 11. BEA is to cross-reference 8.0 BIPs with 15 E2Es.Open. Pending approval of BEA 8.0 BIPs.

5. Assess Topic 4 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 Escalation: Program HRM CHRIS brief Legend Tech Phase Approval Functional Approval Heat Map Published 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 “Deep Dive” on Methodology and P2P Results [TBD] Comments Due BEA Workshops Standards Content Review Comments Due BEA Workshops Informational Brief: APUID

6. 5 BEA 8.0 BIPs 5

7. 6 BIP Alignment to End to Ends 6

8. 7 BIP Alignment to End to Ends (cont’d) 7

9. Urban and Regional Information Systems Association (URISA) Conference Review 8

10. URISA Conference Review Agenda Background/History Address Problem Current Status Next Steps 9

11. Background/History Dec 2001: DoD Manual 4525.8, “DoD Official Mail Manual” The DoD installation is responsible for assigning city-style, street addresses on the installation. Street addresses shall be assigned and used even though a DoD activity may deliver the mail to the addressee. Nov 2004: BEA release 2.3 ADDRESS entity was added. This structure allowed for addresses of places or organizations, not just for persons. Street address was decomposed into its four component parts. Dec 2004: Department of Defense Directive (DoDD) 8320.2, “Data Sharing in a Net-Centric Environment” “Data interoperability shall be supported by making data assets understandable and by enabling business and mission processes to be reused where possible.” Aug 2006: Real Property Information Model version 1.1 released Included the four component parts of the BEA address Mar 2007: DoDD 8320.03, “UID Standards for a Net-Centric Department of Defense” “Develop and promulgate policy guidance for defining, implementing, and maintaining location UID standards…” Aug 2010 Address elevated to the BECCM COI 10

12. Address Problem Lack of A Common Address Standard Impedes: Obtaining reduction in United States Postal Service (USPS) mailing costs Automated validation of addresses Identification and correction of poor quality address data Exchange of address data across DoD communities Effective integration of addresses into GIS data 11

13. Current Status URISA/NENA Addressing Conference Federal Geographic Data Committee (FGDC) draft standard expected to be approved by Dec 2010 It will then be a federal standard that will facilitate the collaboration of the GIS, emergency services, postal, logistics, and related communities regarding address data 12

14. Next Steps BECCM COI Governance Process Assess Topic Formulate Scope & Guidance Functional Requirements/DRAFT Recommendations Approval of Functional Approach 13 [BECCM COI Governance Process continued]