IDE/GTN Convergence How We Process Requirements

1. IDE/GTN Convergence How We Process Requirements Business Intelligence Center of Excellence (BI COE) Data Integration Competency Center (DI CC) AS OF: 12 Jun 2009

2. Lockheed Martin awarded a 5 year BPA as the Enterprise Service Provider (ESP) for 3 Task Areas: Task Area 1: Core Services (designed to retire legacy GTN) Task Area 2: Sustainment (both IDE and GTN P3I) Task Area 3: Extended Core Services Estimated value is $89 Million Teaming Partners (meets 30% Small Business Goal) Data Networks Corporation, INNOLOG, Oakland Consulting Group, Rainbow Data Systems Front-End Application Developers (FADs): Task Area 4 – Front-end application development Federated Software Group, EDS, General Dynamics, Booz Allen Hamilton IGC Contract Structure

3. BI COE Missions Clearinghouse for external IGC requirements -- Single face to customer -- Manage requirements through life cycle (through validation) Organic BI development for requirements (directed workload) -- Create BI Reports, Dashboards -- Capability demonstration and limited user training -- Coordinate with DI CC regarding data needs and troubleshooting; for example, a performance issue Forum for coordinating BI development by ESP (<$250K) and FADs (>$250K) PMO / ESP collaboration for establishing BI development process and standards Forum for coordination / peer review of front-end ESP and FAD BI deliverables

4. DI CC Missions Forum for coordination and peer review of backend ESP deliverables for: -- Interface development -- ETL processing -- EDW development -- ESP metadata creation & management -- ESP web services for exposing data -- Data profiling and disposition of quality issues Support BI COE development needs PMO / ESP collaboration for establishing backend development process and data mgmt standards Forum to coordinate business rule applications to IGC Data

5. BI COE and DI CC Scope BI COE Scope MyIGC Portal & Discovery Application UIReports, Dashboards, Charts Business Objects Semantic Layer Data Warehouse Structures and Views DI CC Scope ETL / Metadata Data Broker Source Systems Consumer Systems

6. BI COE Organization IGC Chief Engineer (Bill Koch) maureen.crooks@ustranscom.mil (618) 256-6791 DSN 576-6791 BI COE Lead (Maureen Crooks) IDE Functional Lead/RM (Liz Comacho-Hart) USTC Matrix Support Lead (Maureen Crooks) BI Lead / Manager (Very Experienced) Functional Lead IDE Requirements Analyst Bryon Grosvalet Functional Analyst #1 COTS Tool Sustainer #1 Responsible For: • Accepting new requirements • First line POC for customers Functional Analyst #2 COTS Tool Sustainer #2 Cost Analyst COTS Tool Developer #1 COTS Tool Developer #2 COTS Tool Developer #3 COTS Tool Developer #4 LTC Walter Nichols / TCJ6-G / (703) 767-6690 /walter.nichols@dla.mil 9/13/2014

7. BI COE / DI CC Relationship BI COE Requirements ESP USTC DLA Maureen Crooks Liz Comacho-Hart FAD CPS BI COE-Engineering DI CC Steve Rusnak Ronnie Broadfoot Mike Ashton Aaron Slaughter Richie Busigo Bilal Hassan IDE Data Working Group • BI COE – Business Intelligence Center of Excellence • DI CC – Data Integration Competency Center • DWG – Data Working Group (DLA)

8. Front End Application Development Overview FADs FADs ESP BI COE Non-Complex • Greater than $250k • When ESP proposal significantly exceeds IGCE for amounts less than $250k • When ESP cannot accommodate schedule requirements due to workload Less than $250k Requirements Analysis Team (BI COE) • New business request • Complexity: • Hard • Medium • IDE Only • SLA level determination • IGCE New IGC Requirement

10. Client fills out Requirement Summary Form (RSF) and submits to BI COE Develop/Negotiate User Requirements Document (URD) jointly with BI COE Functional Develops MIPR and provides to IGC PM Provides funding for requirement development Receives development effort status reports New DoD Client Responsibilities

11. BI COE provides visibility of ALL IGC requirements Enables workload management across program Supports identification of reuse and / or consolidation of opportunities Requirement plus funding evolves into TA3 and/or TA4 work Process is being exercised IGC and IDE collaborate to prioritize workload Unresolved IDE prioritization issues elevate to PEO BI COE helps customers create valid requirement(s) IGC contract works under single processes Take Away

12. QUESTIONS?

13. BACKUP SLIDES

14. Service Delivery FADs FADs 3rd Party FADs How It Works Contractor responsible for IDE and EDW engineering synchronization, configuration management, data integration, sustainment, financial tracking. INPUTS OUTPUTS Other PMs System Engineering Process J-FRB “IDE Only” Req To IDE Service Delivery RQMT Analysis Team (BI COE) • Application Capability Requirements Generation “Hard” System Engineering Process ERRC • “New business request” • Complexity: • Hard • Medium • IDE Only • SLA level determination • IGCE “Medium” Help Desk BI COE RDT “Not Complex”

15. BI COE / DI CC Rough Scoping Contract Doc Prep Execute R E Q U I R E M E N T S ESP Customer Rapid Development CPS/ICA GCE/MIPR ROM/MOA Contract Award LE FAD RSF CCB PM New IDE Requirement RDT Rapid Development Front End Only Back End Only Both FE & BE

16. BI COE / DI CC Team 16

17. Overview The IGC implementation plan has been refined into an overarching program schedule which sunsets legacy GTN components in FY10. The plan is synchronized with guidance from the USTRANSCOM Distribution Portfolio Manager (DPfM), DLA PEO, and USTRANSCOM DPEO and is comprised of multiple spirals to leverage planned IDE enhancements, synchronize with several other USTRANSCOM / Distribution Process Owner (DPO) / Joint initiatives, and injects investment into the converged environment rather than the old GTN infrastructure. Task Area I & II Task Area III & IV

18. Implementation Schedule