Defense Acquisition Data Management Presented to the COI Forum

1. Defense Acquisition Data Management Presented to the COI Forum July 9, 2008 Mark E. Krzysko Business Transformation Office of the Under Secretary of Defense for Acquisition, Technology and Logistics (703) 681-5929 mark.krzysko@osd.mil

2. Table of Contents • Acquisition Data Management Background • Applying SOA to Defense Acquisition Oversight • AT&L AV SOA Demo • AT&L AV SOA Pilot • AT&L SOA Governance • Conclusions

3. Acquisition Data Management Background • Multiple GAO reports note • Perceived deficiencies in Acquisition Management • Perceived complexity, overlaps, and lack of standardization in the DoD systems environment that supports business functions • The presence of numerous systems managing acquisition data without integration has created a management challenge for OSD leadership • Major Defense Acquisition Programs (MDAPs) breach their baselines with little advance notice to OSD • Management is reactive, not proactive • Past issues related to the authoritative nature of data used by OSD Leadership have emerged during reviews with senior Defense leaders

4. Acquisition Data Management Background (cont’d) • DoD leadership initiated a number of data and information sharing activities to address the data management situation. • Institutional Reform and Governance – Task 3.1.3 Integrated Management Information Plan to support senior leadership decision-making • AT&L 2007 Strategic Plan – 6.3.1 Transparent acquisition management information/data capability • AT&L 2007 Strategic Plan – 6.3.2 Analytical tool kit using earned value and work breakdown structure data • AT&L 2007 Strategic Plan – 6.3.3 Service Oriented Architecture (SOA) and authoritative data • AT&L 2008 Strategic Plan – Initiative 1.2.10 – SOA demonstration for the acquisition domain • AT&L Source Document – Transparency, openness and collaboration

5. Acquisition Data Management Background(cont’d) • To address these issues, the ADUSD (BT) and Dep Dir (EI & OSD Studies) entered into a strategic partnership to create a capability that would provide OSD timely access to accurate, authoritative, and reliable information supporting acquisition oversight, accountability, and decision making • Initial steps • Mapped the systems that support the management of Acquisition Oversight across the broader Defense Acquisition framework • Developed a strategy for achieving Acquisition Visibility (AV) within AT&L using a Service-Oriented Architecture (SOA)

6. SOA Services Defense Acquisition Decision Making Data Governance Business Tools Business Applications Web UserInterfaces Definition of key data elements Assignment of responsibility for the authoritative copy of the specified data elements Provision of access to governed data Data Exposure Data Exposure D a t a G o v e r n a n c e SOA Infrastructure BTA Hosted SOA Infrastructure BTA Hosted Data VirtualizationAllows users to access various sourcesof disparately located data without knowing or caring where the data actually reside Data Pull Authoritative Data D a t a G o v e r n a n c e Army Air Force Navy DoD Federal Other SOA Separates Data From Application and Tools Applying SOA to Defense Acquisition Oversight

7. AT&L AV SOA Demo

8. AT&L AV SOA Demo – Memorandum • Establishes a short-term project (OCT 07 – MAR 08) • To demonstrate the utility and applicability (or not) of fundamentally altering the way in which Defense acquisition data is gathered and distributed • Uses sixty or so common data elements that are already provided to the DAMIR or Kaleidoscope systems • Straightforward approach for pulling MDAP data from Services’ source systems • Each Service to nominate four MDAPs • Being conducted by AT&L(ARA) in coordination with AT&L(BT) • Key component of the September 2007 Enterprise Transition Plan (ETP) report to Congress

9. What the SOA Demo Is Not About….. • Imposing any uniform business process throughout the Defense acquisition community • Establishing a Central Data Repository • Replacing DAMIR, Kaleidoscope, AIM, Smart, ….etc, or any other particular software application or tool currently in use within the Department • An IT solution or fix to solve a problem

10. What the SOA Demo Is About….. • Getting authoritative data more quickly into our respective management systems so that it may contribute to better, faster decisions • Demonstrate the feasibility of managing our acquisition data infrastructure separately from our systems or tools • Feasibility of establishing a formal data governance institution within the Defense acquisition community

11. AT&L AV SOA Demo – Overview • Goal • 12 Major Defense Acquisition Programs (MDAPs) • 61 data elements • The Services identified • 4 MDAPs from each Service • The authoritative Service and OSD sources for the 61 data elements • Published the data via a SOA • Displayed the data in selected AT&L business systems/tools • DAMIR • Kaleidoscope • Secure Web Page

12. Army AIM Navy Access DB 1/23/08 Navy Dashboard DAMIR Spreadsheet 1/17/08 AT&L AV SOA Demo – Accomplishments Authoritative Data Available Data System Manager and Location Data System and Location Tools Used Displays Published Program SOA Other Black Hawk Upgrade (UH-60M) EXCALIBUR FBCB2 GMLRS SOA Technology Army WS PEO EIS Ft. Belvior, Virginia 30 State 6 Extrapolated Radford Army Ammunition Plant Radford, Virginia K-Scope EV Components Nunn-McCurdy Other 13 Accounting Identity (calculated from pulled authoritative data) DAU Lab Ft. Belvoir, Virginia DDG 1000 EA-18G MUOS SM-6 ASNRD&A (Management & Budget) Arlington, Virginia NMCI Navy Annex, Arlington, Virginia 30 State 3 Extrapolated DAMIR AT&L WS All 61 data elements B-2 EHF JDAM MP RTIP Minuteman III PRP Air Force SMART AF WS Accounting Identity elements calculated if not available from source: 754th ELSGHanscom AFB Massachusetts AT&L Arlington, Virginia 754th ELSGMaxwell-Gunter AFB Montgomery, Alabama 30 State 4 Extrapolated Web Page Navy – 4 Air Force – 3 Selected data elements DAMIR WS AT&L Arlington, Virginia BTA Server Arlington, Virginia BTA Headquarters Arlington, Virginia 6 State (Current APB) All of the Above OSD/ARA DAMIR AT&L Arlington, Virginia AT&L Arlington, Virginia Data Source Data Display 6 State (Original APB)

13. AT&L AV SOA Demo – Products • Proof of technology applicability to delivery of authoritative acquisition data (trial license) • Strategy to solidify the technological requirements and approach • Strategy to mature governance

14. AT&L AV SOA Pilot

15. AT&L AV SOA Pilot – Expected Sept 08 State • Based on Demo success, a pilot was initiated in April 2008 • Pilot goals • Have 75% of MDAP FYDP Investment $ systems reporting data through SOA services • One source for authoritative data for these programs and data elements • K-scope, commercial BI, and desktop analytic tools will have immediate visibility to this data for authorized users • A functioning data governance mechanism will give stakeholders one place to go for arbitrating Defense acquisition data issues • Ongoing Phase 2 SOA effort will draft a SOA services RFP and be well down the road to establishing sustainable SOA governance and infrastructure

16. AT&L AV SOA Pilot – Next Steps and Observations • Implementation requires a two-phased approach to deliver SOA capability by Sept 08 • Phase 1 Pilot (IOC) is initial SOA implementation with approximately 24 MDAPs • Phase 2 (FOC) is concurrent with phase 1; includes source selection methodology and implementation of “final” acquisition-domain SOA architecture/capability • Parallel operation of SOA and existing management tools needed • “Big Bang” movement of all of DAMIR and K-scope simultaneously probably infeasible • Some MDAPs will lag others in movement to SOA • Each MDAP will have its own path to SOA • A wide variety of feasible initial SOA sources across Services and MDAPs • Even the crudest “spread sheet” SOA source is a step forward

17. AT&L AV SOA Governance

18. AT&L AV SOA Governance – Pilot Data • Data brought under governance for the pilot include ~ 140 elements in the following major categories • EV Data – Elements used in the Demo, plus additional contract elements included in DAMIR’s “Contract Data Point” and/or reported on the Contract Performance Report (CPR) • Nunn-McCurdy Unit Cost – Current Estimate, Current Acquisition Program Baseline (APB) and Original APB Unit Cost data reported at the total-appropriation level (i.e., RDT&E, Procurement, MILCON, O&M). Current Estimate data will also be broken out by fiscal year for comparison with budget submission data. • Budget Submission – Last President’s Budget and POM/BES submission by appropriation and fiscal year to provide a reference point for POM 10 analysis • Milestone – Program milestones as agreed upon in the Acquisition Program Baseline • Science & Technology – Key Performance Parameters, thresholds, objectives and current measurement

19. AT&L AV SOA Governance – Elements

20. AT&L SOA Governance Approach – Structure WSLM CBM* Defense Acquisition Management Senior Steering Group Led by Dr. Nancy Spruill Acquisition Institutions AT&L DOT&E Other OSD Services Agencies Transformational Institutions BTA NII CIOs Services Agencies Core Business Management Group Led by Mr. Phil Rodgers Acquisition Issues Led by Mr. Gary Bliss IT Issues Led by Mr. Mark Krzysko * Weapon Systems Lifecycle Management (WSLM) Core Business Mission (CBM)

21. AT&L AV SOA Governance – Who Is Involved WSLM CBM Senior Steering Group Established OCT 2007

22. AT&L SOA – Relationship to Other Communities • The WSLM Core Business Management Group includes representation from other communities, e.g., systems engineering, test & evaluation, contract management, etc. • AT&L data needs may conflict with those of other groups • We do not expect to be able to achieve consistency among groups’ definitions of particular data elements in the short term • We will begin working with other groups to try to align data they pass to us with our definitions • Our primary goal is to make major weapons systems data consistent across DoD for all MDAPs

23. WSLM CBM* Defense Acquisition Management Senior Steering Group Led by Dr. Nancy Spruill Core Business Management Group Led by Mr. Phil Rodgers Acquisition Issues Led by Mr. Gary Bliss IT Issues Led by Mr. Mark Krzysko AT&L AV SOA Governance – Products Acquisition Institutions AT&L DOT&E Other OSD Services Agencies Transformational Institutions BTA NII CIOs Services Agencies Technical Implementation Standard Data Element Package Information Requirements Indicator Requirements Process Supported Process Owner Data Sources Implementation Requirements Standards & Guidelines Transition Plans Schedule * Weapon Systems Lifecycle Management (WSLM) Core Business Mission (CBM)

24. AT&L AV SOA Governance Goal – Data Packages • WSLM Core Business Management Group (CBMG) will develop and maintain the Data Packages for individual programs • The package is a set of instructions telling actors in the acquisition system exactly how to comply with SOA governance guidelines • The package will be electronic and amenable to constant revision, as well as easy and transparent incorporation by reference • A tailored package for each system will resolve and specify the governance decisions in the three key governance areas: data definitions; technical standards; and authoritative assignment/ • The WSLM CBMG will have three distinct process for altering the content of Data Packages: • Initial package creation, which occurs when a system enters the SOA governance • Sequential refinement/modification of plans as system matures • Global alteration of all plans when new policies are to be promulgated

25. AT&L AV SOA Governance – Next Steps • A governance framework and system architecture is under development. These will document • Policy stewards for each data element • Defense acquisition vocabulary for major weapons systems oversight • Authoritative data sources • Organizational alignment of the architecture will be achieved through • WSLM CBM governance • Inclusion of appropriate artifacts in the BEA • BEA 6.0 focus on EV data • Defense acquisition COI activities • ATL Acquisition Visibility COI established April 14, 2008 • Meeting every 2 weeks as part of the AT&L AV SOA Pilot Technical Meeting • Initial focus is on the AT&L AV SOA Pilot • Identifying related COIs

26. AT&L Acquisition Visibility COI – Responsibilities • Identify acquisition data assets and information sharing capabilities, both in operational and developmental, which should conform to the data strategy goals in DOD CIO Memorandum “DoD Net-Centric Data Strategy,” May 9, 2003 • Identify approaches to enable those acquisition data assets and information sharing capabilities to satisfy data strategy goals and to measure the value to consumers of shared data • Develop and maintain semantic and structural agreements to ensure that acquisition data assets can be understood and used effectively by COI members and unanticipated users • Register appropriate, DDMS-compliant metadata artifacts for use by the AV COI members and unanticipated users • Partner with the governing authority (OUSD (AT&L)/ARA), as appropriate, to ensure that COI recommendations are adopted through programs, processes, systems, and organizations

27. Net-Centric Strategy Alignment Implement DOD Data Strategy per Directive 8320.2 Visible Accessible Understandable Trusted Interoperable Responsive • Identify System Assets to Expose • Identify Assets for Access • Select Applications • Select/Create Taxonomy & Vocabulary • Develop Information Model & Register • Develop Data Payload Packages & Register • Provide Access • Usage Controls • Manage Rights • Register Metadata • Define & Register Metadata Relationships • Identify Key System Interfaces • Comply with Net-Centric Interface Specs • Create & Monitor Robust Feedback Mechanisms • Closely Link Development & Ops • Determine Tagging Method & Technologies • Maintain Catalogs • Tag & Post Asset Info. • Register/ Publish Metadata • Publish Data Asset Pedigree & Authoritative Source Designs • Provide Data Access Services • Post Assets • Register Service • AV Team Action in Coordination with ARA and System Owners • NCES Provides Services • Phase 1 AV Team Action in Progress, through Acquisition Data COI, with Plan To Leverage NCES Services • Phase 2 AV Team Action Planned

28. Conclusions • The AV SOA effort is fundamentally a governance effort • Employs a governance structure to manage functional stewardship of Defense acquisition data within AT&L • Leverages the three data governance keys—data definition, data authority, and data access—to achieve the goal of access to timely, accurate, and reliable decision-making data • Delivers value to major weapons systems decision makers through authoritative and timely data