1 / 14

Tuesday, August 31, 2010

BECCM COI Meeting. 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.

quynh
Download Presentation

Tuesday, August 31, 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BECCM COI Meeting 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 Tuesday, August 31, 2010

  2. 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 1

  3. Action Items 2

  4. Action Items 3

  5. FY10 FY11 Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb BECCM COI Road Map Official Initiatives Tech Phase Approval Functional Approval WG to brief business case Establish Address WG Assess Topic Address Information Plan Update: Address Conference Planned Initiatives Escalation: Program BEA Workshops Comments Due “Deep Dive” on Methodology and P2P Results Heat Map Published BEA Workshops Comments Due Standards Content Review Informational Discussions and General Business Heat Map Published [TBD] H2R Planning Summit Informational Brief: APUID EP&I to brief on BEA 8.0 BIPS HRM CHRIS brief EP&I brief on CBM COI architecture meetings Today Legend Actual BECCM Escalation Actual BECCM Exit Associated Action Item Milestone Estimated BECCM Exit Estimated BECCM Escalation 4

  6. BEA 8.0 BIPs 5

  7. BIP Alignment to End to Ends EI BEA 8.0 EI End-to-End Business Process Alignment P2P, H2R, O2C FM BEA Maintenance P2P, H2R, O2C, B2R, A2R BEA 8.0 FM FM Materiel Weaknesses P2P, O2C, B2R BEA 8.0 FM Joint Enterprise Military Pay Requirements H2R, B2R BEA 8.0 HRM Enterprise Standards H2R BEA 7.1/8.0 HRM HRM Wounded Warrior H2R BEA 7.1/8.0 BEA 7.1 HRM Readiness Assessment H2R BEA 8.0 HRM Defense Enterprise Hiring Solution H2R BEA 8.0 HRM EIW Enterprise System Designation H2R BEA 8.0 HRM Policy Interaction Depictions H2R BEA 8.0 HRM VIPS SOA Solutions H2R BEA 8.0 6 HRM Hire-to-Retire (E2E) H2R

  8. MSSM BEA 8.0 PDS I P2P BIP Alignment to End to Ends (cont’d) BEA 8.0 PDS II P2P BEA 8.0 MSSM EDA Operational Activity Change P2P BEA 8.0 MSSM Order-to-Cash O2C RPILM BEA 8.0 RPILM OmniClass A2R BEA 8.0 RPILM RP Data A2R BEA 8.0 RPILM PHD EL, A2R BEA 8.0 RPIM in the BEA P2P, B2R, A2R WSLM BEA 8.0 WSSLM SPOT D2RR BEA 8.0 WSSLM AT&L SOA A2R 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]

More Related