riding the it wave it acquisition technical challenges
play

Riding the IT Wave: IT Acquisition Technical Challenges Dr Tim - PowerPoint PPT Presentation

Headquarters U.S. Air Force 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 Riding the IT Wave: IT Acquisition Technical Challenges Dr Tim Rudolph CTO, Electronic Systems Center, Hanscom AFB, MA Agenda Agility to Get Capability


  1. Headquarters U.S. Air Force 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 Riding the IT Wave: IT Acquisition Technical Challenges Dr Tim Rudolph CTO, Electronic Systems Center, Hanscom AFB, MA

  2. Agenda  Agility to Get Capability  Critical Enablers  Common Infrastructure  Implementation Baseline  Integration Test Lifecycle Capability  Composable Capability Grand 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 2

  3. Consolidation of IT Infrastructure Required activities Number of Program Application separated for consolidation efforts reduced Acquisition MISSION APPLICATIONS Programs Classic Programs Mission Mission Services Services Mission & & Services Threads Threads & Threads Acquisition Programs IT Infrastructure CORE SERVICES Core Services Current Process with Stovepipe INFRASTRUCTURE Programs Infrastructure From Stovepipes to Services 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 3 3

  4. Agility to Get Capability Focus on Capability Delivery  Cut down the time it takes to field capabilities  Use services to gain capability in modular, incremental approach Separation between building Capability and building Infrastructure  Capability built on known IT infrastructure reducing timelines  Move infrastructure to managed services and commodity IT Use of Standards  Develop a Standards-based approach for building the IT infrastructure and then for building upon that IT infrastructure New Processes  Services Development and Delivery Process (SDDP)  Governance structure to align programs  Testing of new capability in the environment it will run in 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

  5. Acquisition Leadership Working to Provide Policy  Ensure PMOs comply with web services standards and processes  Develop Acquisition Strategy to use the common IT Infrastructure (network infrastructure, hosting environments, and middleware)  Provide Capabilities built using lightweight services and applications independent of infrastructure  Monitor compliance with infrastructure “to be” standards as specified in the Consolidated Enterprise IT Baseline (CEITB), aka “Target Baseline”  Support Product Center definition of the Implementation Baseline  Provide necessary expertise (critical enablers) to PMOs in order to use and manage the IT Infrastructure 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

  6. Critical Enablers Platform Services Management  Key in defining architecture and infrastructure  Work agreements with AFSPC to partner with DISA and other hosting providers and providing enterprise licenses Integration Test Lifecycle Capability (ITLC)  Perform testing to ensure proper integration of new services  Maintain repository of capability web services documentation  Support Help Desk problem solving and service monitoring Outreach  Work closely with program offices and users to understand compliance with standards & protocols and reduce development time for programs Standards & Infrastructure are 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 6

  7. Common IT Environment • Focus on levels of commonality: – Infrastructure as a Service, including network and physical infrastructure – Platform as a Service providing managed services platform – Info services, using PaaS – Redirector to the correct area – Consistent Web 2.0 presentation layer • Focus on classes of capability: – PEOs build applications Light Weight Exposure and other Info & services to fit Info/Mission Services Legacy Systems Services on infrastructure – ERP like COTS capability - provided combination of services and system(s) PaaS – More stand alone systems - (Platform) preference on consistent network/IaaS) IaaS • Third dimension includes Terrestrial (Infrastructure) (Ground & ground stations); Aerial; and “Stand Alone” Light ERP-like Space Systems Weight Hybrids • Challenge is defining baseline within Services one “cube” and growing out 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

  8. Shifting to Development Process Acquisition Participation in New Collaborative Development Processes Running Capability Layers Developing Presentation Capabilities Developing Mash-ups Testing Fielding Determining & New COA Integrating Capability Configuring Apps/ Apps Writing Code SDDP Steps: 1 2 3 4 5 6 Baselines: Target Implementation Operational Infrastructure Middleware Monitoring Providing Provide Performance Assess Put Development Infrastructure On And OS Requirements Network Help Desk Test Environments Support Network Running Infrastructure Time Requirements Services Testing Fielding Sustaining Development Development 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 8

  9. Implementation Baseline The Implementation Baseline explains how to apply the Web Web 2.0 2.0 Tenants: Capacity  Client Neutral Services  Capabilities separate from ADS Applications Infrastructure (Databases)  Bounded User Requirements Implementation Baseline Converged  Web Enabled Services Middleware Infrastructure  Strong 2-way Authentication Servers  Enterprise Sustainment of (Hosting) infrastructure and core services AFNET 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 9

  10. Enterprise Baseline Relationships Consolidated Enterprise IT (CEIT) Baseline (Target or “To Be” SAF A6 CTO leads Baseline) ESC interprets CEIT governance to change baseline to develop program baselines based on guidance enterprise needs IT Operation Baseline Implementation Acquisition (“As Is” Baseline) Baseline Policy (SAF/AQ) Programs direct developers Architecture artifacts added based on enterprise to enterprise repository standards Fielded Services, Program RFPs Applications, and (Standards and Infrastructure Requirements) 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 10

  11. Integration Test Lifecycle Capability The Integration Test Lifecycle Capability (ITLC) provides: Test solutions in realistic “hot” environment • • Aid in packaging and provisioning solutions for fielding • Maintain repository of web services documentation after fielding • Provide Help Desk Tier 2-3 support • Analysis/report on the performance of fielded services for AFSPC (24 th AF) Advise on AF IT infrastructure and the Target • Baseline as a member of the CCB Several organizations to provide the skills needed to support roles 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

  12. The Integration Test Lifecycle Capability (ITLC) in the SDDP Performs testing in Participate in the Provides level-2 and 3 “kickoff” meeting to the pre-production helpdesk support to environment to ensure determine schedule of problem solve when integration, security, tasks needed for services fail and performance fielding SDDP Bounded User Requirement Step 0 Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Define Problem Process Definition COA Development Testing Operationa l M onitors use and Involved in determining the provisioning needs for the performance of services, new capability prior to then provides recommendations for development; changes to the changes to the infrastructure infrastructure would be sent and deprecation of services to AFSPC 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 12

  13. End-to-End Test  Applications only tested in  Provide snap shot of test tools for contractor development lab external use (e.g. TestForge.mil)  Disconnected from Air  Applications tested in a Force IT environment government provided, representative environment  Real testing starts after system goes on operational  Test environment aligned to the network operational environment to stage capabilities  Lots of effort required after fielding to meet acceptable  Complete user experience tested; user performance end-to-end prior to release requirements A “Test Range” for IT systems to include collaborated responsibilities, facilities, personnel, and processes 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 13

  14. An Example of the Future State: Common IT Infrastructure + Multiple Capabilities WEB 2.0 – Presentation Layer JMS DCGS AOC-WS Legacy App A A App A B App A C App J A App J B App D A App D B Capabilities Apps Mission Mission Mission Services Mission Mission Service Service Service Common Mission Services Implementation Baseline Enterprise Core Common IT Environment Platform Services I/F Other Common Platform Service, e.g., Monitoring, Enterprise Licensing 24AF Ops Infrastructure I/F AFNET, including AFDS, etc.  Centralized design and provisioning of a common IT Infrastructure,  Increased C&A inheritance  Increased enterprise licensing & commodity procurement 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 14

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend