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

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

Kenneth J. Moran, Brig Gen, USAF 25 May 2011 DSN 674-0825 kenneth.moran@wpafb.af.mil

Expeditionary Combat Support System (ECSS) Network Complexity and Challenges

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

2

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

Manage Customer Plan Supply Chain Network (Centralized) Plan Operations (Decentralized) Maintain Configuration / BOM Manage Equipment Manage Inventory Conduct Repair and Maintenance Process Returns

Base Flight-lines, CIRFS Engineering, MAJCOMS Create Demand

Contractor / Vendor Info & Contracts Place new or repaired material into Inventory Order Fulfillment Inputs into Material and Equipment Plan Make Demand

Conduct Transport / Delivery

Configuration for adhoc and routine maintenance

Manage Human Resources

Personnel Skills Capacity

Manage Facilities

Capabilities and Capacities

Manage Finances

Suppliers

Personnel Budget

Service Order Material Requirements

Facility Budget & Cost

Part Configuration Information Inventory Information Transportation & Delivery Information Transportation &Delivery Information

Equipment & Tooling Information Equipment / Tooling Budget Equipment / Tooling Requests &Capacity

Facility Requirements Transportation & Delivery Plan Info

DoD SC Integration Office AF Supply Executive Board AFMC Logistics Business Board AF A4/ MAJCOM Meeting

Financial Info Contract Info AF SCM Strategy Outside Logistics Logistics Controlled Transactional Finance Process

Outside AF Operations Outside AF Operations Inventory Information Contract Info

Suppliers

Outside AF Operations

Conduct Acquisition Sourcing

Outside AF Operations Demand Info Parts / Material Buy Demand Fulfill Demand Buy, Fulfill, Make, Plan Data Parts Material Direct Ship Order

AF Logistics “As Is” Process Mapping

Boneyard

Lack of Integrated centralized enterprise plan Inefficient information flows driving non-value added processes No authoritative source

• f engineering data to

ensure OSS&E Manual tech data validation required Lack of Integrated enterprise plan driven activities Lack of end-to- end enterprise asset visibility Integrated data package not always required Lack of confidence in Supply Chain Decentralized management of enterprise funds

Integrate supply and depot Mx Ops

Redundant financial transactions Cold War Era Skills Fragmented sourcing Excess inventory to cover variance 3

No Change 2005 vs. 2010

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 Increment 1 Specifics Description

• Requirements Basis:
• ICD: GCSS-AF Capstone ORD
• CD: Signed Apr 2010 (Milestone B)
• Major Customers:
• HQ AF/A4, AFMC, ACC, AMC, PACAF, HAF, GLSC,

AFRC, AFSPC, ANG, AETC, USAFE, AFDW

• Contractors:
• COTS - Oracle, FFP, award May 06 (TCV $47.1M)
• System Integrator (SI) - Computer Sciences Corp,

FFP, Sep 06 (TCV $859.7M)

• External AF Interest:
• USD(AT&L)
• OMB
• OSD CAPE
• All other DOD ERPs
• Transformation of the U.S. Air Force’s global supply

chain and logistics processes:

• Commercial best practices from Aerospace and

Defense and other relevant industries

• Utilize capabilities that exist within the Commercial off-

the-shelf (COTS) Enterprise Resource Planning (ERP) to the fullest extent possible

• Lean principles and practices
• Includes:
• 186+ installations globally
• 3 DFAS sites
• 250,000 military and civilian users (40,000 for Inc 1)

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

ECSS Overview

4

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

ECSS Approach/Strategy for Deployment on GIG

 Develop, test, and deploy using the same processes & policies

• n 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!

5

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

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

• bjectives, but each
• wner’s implementation

may vary



ECSS size and scope are requiring transformation

• f the infrastructure and

make it difficult to obtain synchronization and consistent prioritization

6

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

Real-Time Data Challenges



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

7

Need to simplify, standardize, and provide better level of transparency on real-time availability/performance Data

Many Boxes and Firewalls between User and ECSS

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

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



Matching infrastructure capacity with application and User needs requires a team



Application PMO



DISA & GCSS Computing Services



DISA Network Services



AF Network Planning



Base-level client operations & standard desktop



Any link or combination of links in the infrastructure chain from the database storage to the PC on the flight line can impact capacity requirement and ultimately the User’s experience!

NIPRNet Internet

Enclave Extension DMZ Load Balancing SSL Offload

SSL SSL

DECC Mont

Prem Router New “Zeus” devices handle SSL

Restricted Unrestricted URLs

GCDS Akamai SSL SSL Internet Users .mil users Air Force User AFNet Base Base BlueCoat CITS Block 30 S S L

GCSS Web Seals

Enclave DMZ Extension

Load Balancer ECSS Web Servers HTTP HTTP

SSL

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

11

• 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

Summary

12

 Currently, it is very complicated to develop, test, and

deploy an ERP in today’s environment

 SDDP is addressing some of these problems  ERPs present unique challenges that should be

factored in moving forward A Smart Phone Delivery Model May Not Work for an ERP