Expeditionary Combat Support System (ECSS) Network Complexity and - PowerPoint PPT Presentation

Expeditionary Combat Support System (ECSS) Network Complexity and Challenges Kenneth J. Moran, Brig Gen, USAF 25 May 2011 DSN 674-0825 kenneth.moran@wpafb.af.mil I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Agenda  AF Logistics “AS IS” process mapping  ECSS program overview  ECSS approach/strategy for deployment on GIG  Current stakeholders complexity challenges  Real time data challenges  Interface and release management challenges  Capacity planning challenges  Where we want to be  SDDP thoughts from an ERP perspective  Summary I n t e g r i t y - S e r v i c e - E x c e l l e n c e 2

AF Logistics “As Is” Process Mapping Inefficient DoD SC Plan Lack of Integration Manage information flows AF A4/ Integrated Office Supply Chain MAJCOM Equipment driving non-value centralized Equipment Equipment Meeting Network & Tooling / Tooling added processes AF SCM enterprise plan AF Supply (Centralized) Information Requests Executive Strategy AFMC Equipment / Tooling Board &Capacity Logistics Budget Inputs into Material Business Outside AF Board Redundant and Equipment Plan Operations financial Supplier / Factory transactions Manage Material Parts / Material Process Financial Info Finances Requirements Plan Integrate Returns Facility Personnel Operations Base Flight-lines, CIRFS supply and Budget & Budget Engineering, MAJCOMS (Decentralized) Facility Cost depot Mx Service Create Demand Requirements Manage Order Decentralized Ops Demand Info Manage Buy, Fulfill, Make, Plan Data management of Facilities Customer Make Buy Fulfill enterprise funds Lack of Demand Demand Demand Suppliers confidence in Order Capabilities Parts Material Inventory Supply Chain Lack of end-to- and Capacities Fulfillment Inventory Information end enterprise Information Manage Integrated data asset visibility Cold War Era Inventory package not Skills Manage always required Contractor / Vendor Warehouse Outside AF Human Info & Contracts Place new or Operations Contract Resources repaired material Transportation Info into Inventory Conduct Repair & Delivery Supplier / Factory Conduct Acquisition and Maintenance Plan Info Contract Info Supplier / Factory Sourcing Personnel Skills Capacity Excess inventory Part Configuration Configuration Outside AF Direct Ship Lack of Integrated to cover variance Transportation Information for adhoc and Operations Order enterprise plan Fragmented &Delivery routine driven activities sourcing Boneyard Information maintenance Maintain Configuration Supplier / Factory / BOM Supplier / Factory Outside AF No authoritative source Conduct Operations of engineering data to Transport / Manual tech ensure OSS&E Delivery data validation Transportation & Delivery Information Suppliers required I n t e g r i t y - S e r v i c e - E x c e l l e n c e No Change 2005 vs. 2010 3 Outside Logistics Logistics Controlled Transactional Finance Process

ECSS Overview Warfighter Benefits  Benefits:  Improved asset and logistics pipeline visibility  Reduced customer wait time (CWT)  Improved cycle times (repair & inventory pipelines)  Reduced inventory costs  Improved forecasting accuracy  Improved perfect order fulfillment  Beneficiaries:  Commanders, Planners and Logisticians Description Increment 1 Specifics  Requirements Basis:  Transformation of the U.S. Air Force’s global supply  ICD: GCSS-AF Capstone ORD chain and logistics processes:  CD: Signed Apr 2010 (Milestone B)  Commercial best practices from Aerospace and  Major Customers: Defense and other relevant industries  HQ AF/A4, AFMC, ACC, AMC, PACAF, HAF, GLSC,  Utilize capabilities that exist within the Commercial off- AFRC, AFSPC, ANG, AETC, USAFE, AFDW the-shelf (COTS) Enterprise Resource Planning  Contractors: (ERP) to the fullest extent possible  COTS - Oracle, FFP, award May 06 (TCV $47.1M)  Lean principles and practices  System Integrator (SI) - Computer Sciences Corp,  Includes: FFP, Sep 06 (TCV $859.7M)  186+ installations globally  External AF Interest:  3 DFAS sites  USD(AT&L)  OMB  250,000 military and civilian users (40,000 for Inc 1)  OSD CAPE  All other DOD ERPs I n t e g r i t y - S e r v i c e - E x c e l l e n c e 4

ECSS Approach/Strategy for Deployment on GIG  Develop, test, and deploy using the same processes & policies on the same architecture, integration framework, and network  Reduce variation and complexity wherever possible:  Combine teams to accomplish testing (ECSS SI, ECSS RTO, GCSS RTO)  Integrate teams (ECSS, AFNIC, GCSS, DISA) responsible for establishing, maintaining, and monitoring all environments  Minimize number of application migrations required to deploy to production  Drive to standardize and simplify path to the user  Exploit enterprise infrastructure, services, and capabilities as much as possible; drive to do so internally and drive the enterprise to change – do not accept status quo! I n t e g r i t y - S e r v i c e - E x c e l l e n c e 5

Current Stakeholder Complexity Challenges There are really many  networks and many network owners that ECSS crosses to get capability to users  Many policies are focused toward common objectives, but each owner’s implementation may vary ECSS size and scope are  requiring transformation of the infrastructure and make it difficult to obtain synchronization and consistent prioritization Coordination and Unity is a Enormous Challenge I n t e g r i t y - S e r v i c e - E x c e l l e n c e 6

Real-Time Data Challenges Many Boxes and Firewalls between User and ECSS User path requires orchestration of connections/handshakes across a many perimeter devices, firewalls, proxy  servers, and authentication servers Time stamped data can be used to triage security, availability, and responsiveness errors as they occur   Information available locally, but not readily available at enterprise level challenging problem is resolution-time Need to simplify, standardize, and provide better level of transparency on real-time availability/performance Data I n t e g r i t y - S e r v i c e - E x c e l l e n c e 7

Interface & Release Management Challenges  Coordination of testing and deployment of interfaces requires very complex interaction with AFNET, DISA, GCSS, and ECSS trading partners  Changes to network components are managed to different requirements, schedules and is inconsistent, if any enterprise-wide notification when changes are applied  Air Force Standard Desktop Configuration is similar to the network; additionally, they don’t consider individual web based applications as part of their testing/deployment Challenges applications to try keep up with changes after they’ve been released, introducing significant risk to what’s already been fielded as well as any future release I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Capacity Planning Challenges Internet .mil users Air Force CITS Users  Matching infrastructure User Block 30 Restricted SSL Base AFNet capacity with application and Unrestricted URLs SSL Base S BlueCoat User needs requires a team S Akamai L GCDS NIPRNet Internet  Application PMO SSL SSL  DISA & GCSS Computing DECC Prem Router Services Mont  DISA Network Services New “Zeus” devices handle SSL Load Enclave Balancing  AF Network Planning Extension SSL DMZ Offload  Base-level client operations SSL & standard desktop  Any link or combination of Enclave HTTP links in the infrastructure GCSS DMZ Web Seals chain from the database Extension storage to the PC on the Load flight line can impact Balancer HTTP capacity requirement and ultimately the User’s ECSS Web Servers experience! Huge challenge for an application PMO to coordinate across an enterprise to properly plan capacity I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Where we want to be  Single focal point for applications to coordinate infrastructure requirements and issues  Simplified network path to get ECSS capability to users  Real-time transparency for infrastructure availability and performance information (from the desktop to the data center) I n t e g r i t y - S e r v i c e - E x c e l l e n c e

SDDP Thoughts from an ERP Perspective 1. SDDP appears consistent with ERP focus to refine requirements up front with goal to minimize customized coding 2. SDDP focus on “right sizing” Security is consistent with the currently overly complex situation ECSS is experiencing today 3. SDDP goal to more rigorously implement standards addresses a major issue ECSS has been facing 4. SDDP may be underestimating the development data cleansing, and deployment costs than is possible with ERP solutions 5. We are finding the relationship between the ERP and the network to be very tightly coupled … SDDP needs to address this complexity more head on 6. It is unclear whether SDDP is placing sufficient focus/importance on load and interoperability testing (who/how/when/how much) 7. It will be difficult to garner agreement from the Acquisition and Budgeting Systems to move more requirements refinement and prototyping to pre-MDD The Glass Is Half Full … We Think! I n t e g r i t y - S e r v i c e - E x c e l l e n c e 11