Acquisition Domain Overview Presented to the Federal Acquisition Conference June 13 th & 18 th , 2003

1. Acquisition Domain Overview Presented to the Federal Acquisition Conference June 13th & 18th, 2003

2. Points of Interest • Role of the Acquisition Domain • Governance Structure • Acquisition Domain Actions • Success Stories • Future Actions

3. Goals Impacting the Acquisition Domain DOD Transformation Goals • Protect the U.S. homeland and critical bases of operation; • Deny enemies sanctuary; • Protect and sustain power in access-denied areas; • Leverage information technology to connect troops and their operations; • Improve and protect information networks from attack; and • Enhance space operations. E-Government Act of 2002 • To provide effective leadership of Federal Government efforts to develop and promote electronic Government services and processes by establishing an Administrator of a new Office of Electronic Government within the Office of Management and Budget • To promote the use of the Internet and other information technologies to provide increased opportunities for citizen participation in Government • To promote interagency collaboration in proving electronic Government services, where this collaboration would improve the service to citizens by integrating related functions, and in the use of internal electronic Government processes, where this collaboration would improve the efficiency and effectiveness of the processes • To improve the ability of the Government to achieve agency missions and program performance goals • To promote the use of the Internet and emerging technologies within and across Government agencies to provide citizen-centric Government information and services • To reduce costs and burdens for businesses and other Government entities • To promote better informed decision making by policy makers • To promote access to high quality Government information and services across multiple channels • To make the Federal Government more transparent and accountable • To transform agency operations by utilizing, where appropriate, best practices from public and private sector organizations • To provide enhanced access to Government information and services in a manner consistent with laws regarding protection of personal privacy, national security, records retention, access for person with disabilities, and other relevant laws AT&L Goals • Modular solution sets • Performance improvements • Reduce current and future maintenance costs • Minimize lines of code investment • Enterprise data sharing • Formless • Reuse of technology investment • Competition, where possible DPAP Goals • 80% reuse of technology • Using Incr. 2 Adapter • Seamless data integration • Supports single baseline goal • ROI supportable • Fits within spiral development concept • Sustainment reduction • Core capability across P/C/S, MWS, and ICPs • Adaptable to business/technology insertions DPAP(EB) Goals • Reduce Leverage technology to provide the best possible tools for the workforce • Have fewer, more capable, and integrated systems • Promote the use of best practices to have better information for decision making • Reduce the cost of business operations • Work closely with other domains to streamline our department processes

4. The Acquisition Community is Composed of People, Process, and Technology; All are Configured in the Context of Strategically Driven Policy The Previous DPAP Relationship with Acquisition Community • Historically, the focus has been on the technology component of the Acquisition Community. • The objective is to fully integrate the acquisition workforce with streamlined acquisition processes and standard technologies. People Policy & Regulation Policy & Regulation Process Technology

5. Moving Forward, Our Role Will Be To Integrate People, Process, and Technology The DPAP Relationship with the Acquisition Community • The Acquisition Domain will design and implement a modern acquisition environment that is consistent with policy and integrates enterprise technologies with best practice processes for use by trained personnel. Policy &Regulation Policy & Regulation Process Technology EB People Policy& Regulation

6. Assistant Secretary of Defense Network Information Integration Business Management Enterprise Architecture Office of Undersecretary Defense, Comptroller Global Information Grid Governance Structure for Acquisition eBusiness Office of Management and Budget D DPAP Acquisition Governance Board D DPAP D DPAP Acquisition Innovation Forum Program Executive Office Joint Acquisition E-Business Oversight Board (JAEBOB) [Defense Procurement &Acquisition Policy (E-Business)* (DPAP (EB)), Services and Agencies] Program Joint Requirements Boards Procurement CONOPS Defense Acquisition Business Process Purchase Card CONOPS Program Execution Etc. PCARD JPMO Service & Agency Portfolios SPS JPMO CCR JPMO Service Programs Defense Acquisition System Inventory Acquisition/ Procurement CONOPS *Chair

7. Acquisition Governance Board in Federal Context Office of Management & Budget Internal Effectiveness And Efficiency Council (IEEC) (Quad Council) CFO Council CIO Council Federal Acquisition Council HR Council D,DP&AP Technology Committee DP&AP(EB) DoD Acquisition Governance

9. Notional Federal Acquisition Governance • Federally coordinated requirements • IAE responsible for portfolio execution • ACE provides functional input through IAE to components • System Owners responsible for project implementation • Result: Alignment of requirements and funding Quad Council Office of Electronic Government Federal Acquisition Council(FAC) OMB/Resource Mgmt. Offices Acquisition Committee for Excellence (ACE) Senior Agency Representatives 300 Submission Agency CIO Integrated Acquisition Environment Requirements JRBBPN JRBeStandards JRBFPDG-NG JRBIGOTS JRBeCatalog Agency Level TeDS ICD IGTP WDOL EPLS FBO ESRS BPN

10. Acquisition Technology & Logistics (AT&L)Domain Owners Executive Board Mr. Wynne USD(C)/CFO Component FMs/Lead Agent* Finance,Accounting Operations & Financial Management $$ USD(C)/CFO Component FMs/Lead Agent* Programming Budget & Funds Control $$ Steering Committee Mr. Wynne & Ms. Morales FMMP Working Group CIO Adv.Council USD(P&R) Component M&Rs/Lead Agent* Human Resource Management $$ ASD(C3I)/CIO Component CIOs/Lead Agent* Technical Infrastructure $$ Business Modernization and Systems Integration (BMSI) Enterprise Architecture Development, Sustainment, Budget $$ Control Functional integration across AT&L USD(AT&L) [DPAP] Component Acq/Lead Agent Acquisition/Procurement $$ Ms. Lee USD(AT&L) [L&MR] Component ILs/Lead Agent Logistics $$ Ms. Morales USD(AT&L) [I&E] Component ILs/Lead Agent Real Property and Environmental Liabilities $$ Mr. DuBois

11. Acquisition Domain – Roles and Responsibilities • Business Management Modernization Program (BMMP) Steering Committee Established and Approved Domain Owner Roles and Responsibilities 27 Feb 03 • The roles and responsibilities for the Acquisition Domain are to: • Build and maintain Global Information Grid (GIG) compliant architecture products, data strategy, and transition plans that are consistent with FMEA • Review domain portfolio and enforce compliance with architecture, data strategy and transition plans. • Develop scorecard metrics. • Review and approve program funding. • Develop legacy system phase-out strategy and prioritization. • Develop domain strategy for new acquisitions. • Select and designate executive agents to plan and implement transformation initiatives within and across the domains. • Manage and represent domain needs during development of enterprise transition priorities and resourcing.

12. May 2003 2004 2005 2006 2007 2008 Stand Up DPAP(EB) Office Standup AGB, JAEBOB, & Governance Structure Develop Procurement Process CONOPS Support FMMP Architecture Development Acquisition/Procurement Domain Enterprise Plan Program Support and Compliance Extend and Maintain Architecture Transition Support BMMP Pilots Additional Implementation Develop FMEA Phase 1 – Develop FMEA Phase 2 – Extend FMEA Accept FMEA DPAP Federal Acquisition Integrated Acquisition Environment Baseline Current Acquisition Environment Identify & Implement Incremental Improvements Develop Enterprise Procurement Modern. Environment Designate Lead Agents Monitor Segment Acquisition & Implementation Identify and Monitor Pilots DPAP DoD Governance Structure Develop Acquisition Domain Strategy Transition Planning Sustainment and Ongoing Operations Plan and Conduct Procurement AOA Services & Agencies Support DPAP in Enterprise Procurement Modernization Efforts Implement Pilots Standup Service Governance Structure Support Procurement Process CONOPS Support FMMP Architecture Development Acquire & Implement Segments Transition Planning

13. April February March May June July August Stand-up Governance Structure Develop Governance CONOPS Commence Developing MOAs Initiate Performance Management Plan Stand Up DPAP(EB) Office Standup AGB, JAEBOB, & Governance Structure Develop Procurement Process CONOPS Support FMMP Architecture Development Baseline Current Acquisition Environment Analyze Legacy Systems Develop Baseline Views DPAP EB Six Month Enterprise Plan INITIATION Develop Acquisition Domain Strategy Conduct One-on-One Interviews Conduct Domain Leadership Offsite Develop Change Mgt/ Communications Plan Finalize Domain Strategy Initiate Performance Management Plan Develop Enterprise Procurement Modernization Environment Develop Domain Pilot Strategy Develop Enterprise Procurement Modernization Views Develop Acquisition Procurement CONOPS Analyze FMEA Architecture Develop Transition Plan Conduct Gap Analysis Sequence Segments Refine Segments Review FMMP Transition Plan ONGOING OPERATIONS Program Management Commence Legacy Program Plan Reviews Commence SPS AoA Conduct Resource Planning POM Recurring Board Meetings Recurring Board Meetings Recurring Board Meetings Recurring Board Meetings Recurring Board Meetings Recurring Board Meetings

14. Success Stories • Transition from DODBusOpps to FedBizOpps • The web presence of DoDBusOpps will be shut down on 1 July 2003 • All transactions are being routed to FedBizOpps • Transition from DoDTeDS to FedTeDS • DoDTeDS shutdown is complete • FedTeDS now fully functional and training is ongoing • First steps taken to move EDA from document repository to data collection • Transformation will allow pre-population of downstream systems

15. Acquisition Domain Future Plans • Create a more detailed mapping of Acquisition processes as part of the BEA Architecture • Design a transition plan for integrating FPDS-NG within the Domain • Perform a systems inventory analysis to determine redundancies throughout the Domain • Enact the Data Management Approach for the Domain

16. Output The Acquisition Domain Transformation Framework BEA Acquisition Domain BEA Inputs Services/ Defense Agencies End State Transformation

17. System 1 Services Vendors System 2 Defense Agencies Customers System 3 System 4 Evolving Towards a Streamlined Set of Enterprise Solutions that Create Efficiencies and Enable a Knowledge Based Workforce Enterprise Procurement Modernization Environment Existing EB Acquisition Environment Transformation Vendors Services Enterprise Solutions Customers Defense Agencies DPAP • Enterprise solutions include a combination of Service/Agency specific systems, enterprise level processes and systems and Federal processes and systems

18. Summary • There is a long road ahead, but a longer road behind • Governance is in place • Actions are being taken • Roles are being further defined • Outcomes are being delivered • The Acquisition stovepipe is dissolved • The Acquisition Domain is an influencer, not a reactor