1 / 22

IDE/GTN Convergence

IDE/GTN Convergence. IDE/GTN Convergence (IGC) Vision. Vision : Provide common integrated data and application services enabling cohesive distribution solutions for the DoD Enables : Common logistics picture Distribution visibility Material asset & in-transit visibility Benefits :

berke
Download Presentation

IDE/GTN Convergence

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. IDE/GTN Convergence

  2. IDE/GTN Convergence (IGC) Vision Vision: Provide common integrated data and application services enabling cohesive distribution solutions for the DoD Enables: • Common logistics picture • Distribution visibility • Material asset & in-transit visibility Benefits: • Enhanced delivery of forces & sustainment • Improved situational understanding • Near real-time Enterprise Access to logistics and transportation data • Improved trust and confidence IDE / GTN Convergence Unity Of Effort • Business Application Tools • Logistics Visibility • Transportation C2 and ITV Services DLA Data Integrated Data Environment PM USTC Data Global Transportation Network PM

  3. At The Highest Level USTRANSCOM Reference Data DLA Reference Data A/V GCSS-J • USTRANSCOM Reference Data Management (TRDM) • Defense Logistics Information Service (DLIS) data stores IDE USTRANSCOM Operational Data DLA Operational Data • Global Transportation Network (GTN) • Business Decision Support System (BDSS) • Others • Defense Automatic Addressing System Center (DAASC) systems • Business Systems Modernization (BSM) • Others Other Apps • Core Constraint: GTN cannot provide access to “detail” data • Core Constraint: GTN does not have an Enterprise Data Warehouse • Core Constraint: GTN enhancements/upgrades must be backwards compatible • IDE requires refinement; move from providing “gateway” services to true brokering

  4. Data Integration Supporting Legacy Process Manifest Schedule Passenger Cargo Others Key: Data Strategy Integrated Data: • Service oriented view • Well defined • Gaps identifiable NewCross-Functional Data Integration Backwards Compatibility (This is HARD) Domain Data: • Supports domain view • Understandable Detail Data: • Profiling (data quality) • Authoritative • Accessible

  5. How? Vision: A common logistics picture, provided through common integrated data, resulting in end-to-end supply chain and distribution visibility Capabilities: • State-of-the-art capability to perform reporting, ad hoc queries, drill-down, and data mining • Single point of access to data within DLA and USTRANSCOM, and between DLA/USTRANSCOM and external systems Objectives - GTN (FY 07-08) and IGC (FY09-10): • Single sign-on to the GCSS-J portal – improves war-fighting user experience • Pub/Sub Access To Data - ensures reliable, access, and uniform decision making • Enterprise Data Warehouse - provides supply chain, distribution, and logistics data that is trusted across the end-to-end enterprise • Enterprise Data Sharing - provides Joint Deployment and Distribution Enterprise (JDDE) information, data, and status in a form suitable for the decision making and planning processes of the Combatant Commander

  6. SMS GTN GCSS-J Portal Others IRRIS RFITV GTN (P3I) AV IGC Capability Enabling COP Distribution & Deployment (D2) LIVE – NOV 07 Single sign on Joint Users & Fusion Centers LIVE – JUN 07 Enterprise Data Warehouse (GTN) IGC & COP(D2) Targets: • Joint Portal – Single Sign On • One version of the truth (data) • Net-centric … publish/subscribe • Focused data quality improvements • Avoids $10M across FYDP Service EnterpriseData Whse Integrated Data Environment Publish/Subscribe Source Systems LIVE – JUN 07 WPS Initial Effort: Motor Carrier Compliance IBS GATES GFM DSS

  7. GCSS-J • BLUF: We need to support GCSS-J as a Portal to compliment convergence and demonstrate how we support the overarching DoD framework • Convergence will mean more if we can demonstrate how it enables the greater integration of logistics systems • Takes scope (and risk) away from our initiative • Compliments other initiatives

  8. Other Specific Goals • Retire the existing GTN operational data store via separation of data from application and convergence with the IDE without disruption to the mission critical systems that currently rely upon GTN for data. • Migrate existing GTN and new J-FRB approved front-end user capabilities into a Single Sign-On environment utilizing the GCSS-J high and low-side portals for user access. • Provide the DoD access to integrated data required for decision support from DLA and USTRANSCOM systems from a single place. Initial scope is the data from systems required to retire the legacy GTN data store. • Provide timely access to historical data by creating an automated infrastructure to capture and broker up to five years of historical information • Improve data quality by providing quantitative measurement reports of data quality to authorized users. Provide a mechanism for functional users to directly compare quality of data in the IGC environment to source systems. • Provide organized and understandable meta-data that allows authorized users to determine the genealogy of information they see in the IGC. GCSS - J Access (via Single Sign - On) AV IRRIS GTN/P3I RF - - ITV ITV SMS AV IRRIS GTN RF SMS IGC GTN GTN EDW GTN Meta ODS Data IDE ( Ver 2.0) Source Systems Source Systems

  9. GTN/P3I SMS IRRIS RF-ITV AV Implementation Plan GCSS-J Access (via Single Sign-On) IGC Phase 1: • Migration of source system data (including history) • Data quality profiling • Pub/Sub access to detail data via IDE • Adhoc Query of detail data • Motor Carrier Compliance and new “level-1” reports Phase 2: • Integration of data to provide backwards compatibility • Pub/Sub access to integrated data • Other PMs (e.g. SMS, AV, others) begin to utilize pub/sub availability of data • Migration of GTN front-end functionality • Migration of Joint Exercise System • GTN Sunset GTN P3I Phase 2 EDW GTN ODS Meta Data IDE (Ver 2.0) Phase 1 Source Systems Source Systems

  10. 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 two phases and multiple spirals to leverage planned IDE enhancements, synchronize with several other USTRANSCOM / Distribution Process Owner (DPO) / Joint development initiatives, and inject investment into the converged environment rather than the old GTN infrastructure. IGC Contract Spirals Begin IGC Releases Focus: Sunset Legacy GTN Components GTN P3I Releases Build EDW using IDE services Supporting GTN Sustainment Releases

  11. Before & After • IGC allows GTN’s Enterprise Data Warehousing capability and the capability deliveries of the IDE to be managed by a single Program Manager. Funding from one command does NOT augment the funding of the other command’s program; efficiencies are a result of utilizing services rather than "building our own." • IGC is a change in the way that DLA and USTRANSCOM manage, contract for, sustain, and implement improvements to GTN and IDE infrastructure. The legacy components of GTN will be retired, while the newer ones (e.g., its new Enterprise Data Warehouse) will be used in conjunction with services provided by the IDE to replace the existing capabilities of GTN, as well as, create new ones. Before P3I (Now) IGC End State = New

  12. Where We Are Going FY11 FY06 FY07 FY08 FY09 FY10 FY12 Task O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S Milestone Decisions GTN Sunset Contract Decision ERAM Streamlined Products Program Products EOA/CONOPS EA/ACQ STRAT Near Term Milestones: Phase 1 Rel th 4 QTR FY08: BDSS Migration P3I #1 MCC • Low - side Infrastructure st 1 QTR FY09: Begin IGC Spiral 1 • Motor Carrier Compliance #2b • Data profiling reports Rel P3I #2a st 1 QTR FY09: Prod. Expansion WWX • Pub/Sub to detail data • Adhoc query nd 2 QTR FY09: Move Dev • Level 1 functional reports Rel BDSS P3I #3 rd • 3 QTR FY09: Spiral 2 and 3 Begin rd • 3 QTR FY09: Spiral 1 Ends Phase 2 Rel Spiral 1 • High - side Infrastructure • GTN Integration • Migrate GTN front - end Rel Favorable MS C Decision Spiral 2a & 2b • COOPS • GES • GTN Sunset Rel Spiral 3a & 3b Other IDE Releases (See IDE Schedule) Pre - Planned Product GCSS - J Portal Improvements, other DLA Releases, and COPD2 Other Releases Utilizing IGC Services Integration Moving old Test to High Side Production GTN FOC GTN Sustainment Sustainment IGC Sustainment May03 IDE IOC IDE Sustainment Oct05 H.S COOP/GES Pre - Prod to H.S. New DEV Environment Build Prod, Pre - Prod, L.S. Prod Expansion DEV,Test L-M DEV/Test to Test L.S. COOP IDE & GTN IGC

  13. Interface Schedule • Improved data quality visibility • For each system: • Capability forPub/Sub • Adhoc query • Causative research capability • Functional Data profiling capability • Quantitative Data Profiling capability Key Points: • Improve data quality • Eliminate BDSS ODS • Empower other systems: • SMS • AV • GCSS-J

  14. Service Delivery How It Worked Before Government responsible for synchronization of different contractor engineering processes! INPUTS OUTPUTS Cmd IDE Contractor “A” S.E. Process “IDE Only” Req To IDE Service Delivery J-FRB Req Analysis Team • Application Capability Requirements Generation “Hard” GTN Contractor “B” S.E. Process • “New business request” • Complexity: • Hard • Medium • IDE Only • SLA level determination “Medium” Help Desk “Easy Fix”

  15. 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 development initiatives, and inject investment into the converged environment rather than the old GTN infrastructure. Task Area I & II Task Area III & IV

  16. Implementation Schedule

  17. FADs FADs When Do FADS Compete For Work? • Applies to “front-end” application development work beyond the scope of requirements documents (CPD/CDD). ESP BICOE Easy • 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 Req Analysis Team (BICOE) • “New business request” • Complexity: • Hard • Medium • IDE Only • SLA level determination • IGCE New IGC Requirement

  18. Service Delivery FADs FADs 3rd Party FADs How It Works Today Contractor responsible for IDE and EDW engineering synchronization, configuration management, data integration, sustainment, financial tracking. INPUTS OUTPUTS Other PMs S.E. Process “IDE Only” Req To IDE Service Delivery J-FRB Req Analysis Team (BICOE) • Application Capability Requirements Generation “Hard” S.E. Process • “New business request” • Complexity: • Hard • Medium • IDE Only • SLA level determination • IGCE “Medium” Help Desk BICOE “Easy Fix”

  19. BICOE Organization IGC Chief Engineer (Bill Koch) maureen.crooks@ustranscom.mil 618.256.6791 BICOE Lead (Maureen Crooks, Acting) IDE Matrix Spt Lead (Liz Camacho-Hart) USTC Matrix Spt Lead (Maureen Crooks) Functional Lead BI Lead / Manager (Very Experienced) • Face to customers • Bring functional & technical resources together for rapid application development • Create and maintain BI standards (Best Practices) • Develop BI solutions & applications Functional Analyst #1 COTS Tool Sustainer #1 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 The BI COE allows IGC to connect goals, metrics and people across the enterprise.

  20. BICOE/DICC Relationship BICOE-Requirements ESP USTC DLA Liz Comacho-Hart Bryon Grosvalet Maureen Crooks Judy Bratcher FAD CPS BICOE-Engineering DICC Steve Rusnak Ronnie Broadfoot Mike Ashton Aaron Slaughter Richie Busigo Bilal Hassan IDE Data Working Group BICOE – Business Intelligence Center of Excellence DICC – Data Integration Competency Center DWG – Data WorkingGroup (DLA Oroganization)

  21. IGC Public Web Site http://www.dla.mil/j-6/IGC.asp IGC Secure Web Site https://www.dscp.dla.mil/idegtnc/

  22. IGC Summary • Leverages existing investment; integrate the components from individual programs of record into a comprehensive capability • Incremental, evolutionary (no big-bang) • Formalizes a relationship (DLA & USTRANSCOM) that is a “natural act” (supply + transportation = distribution) • Mitigates adverse effects of fragmented and missing data • Open architecture of modular, interoperable, components • Reusable services (eliminates redundant interfaces) • Net-centric • Best of breed approach (but, very organized … not a bunch of puzzle pieces scattered about) • Creates a data integration competency center (we implement our models and prove they work … not just building theoretical ones) • Accommodates changing technology (COTS) and requirements

More Related