mr kent werner saf usm 2 24 may 11 agenda why we re here
play

Mr. Kent Werner (SAF/USM-2) 24 May 11 AGENDA Why were here An - 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 A Vision For Development and Delivery of IT Capability for the War-Fighter Mr. Kent Werner (SAF/USM-2) 24 May 11 AGENDA Why were here An


  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 A Vision For Development and Delivery of IT Capability for the War-Fighter Mr. Kent Werner (SAF/USM-2) 24 May 11

  2. AGENDA  Why we’re here  An Enterprise Challenge  Infrastructure  Applications  Service Development & Delivery Process (SDDP)  Actions Required to Achieve Success 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. WHY WE’RE HERE  Include Industry Partners in IT Way-ahead Activities  Work in Progress: We are Identifying functions to be Performed and Requisite Skill-sets  Changes in Technology, Legislation/Policy and Commercial Business Practices  To be successful we need to address:  Infrastructure  Applications  Development and Delivery Process The cost of IT is the RESULT of our business practices – not the root cause! 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

  4. AN ENTERPRISE CHALLENGE (NOT JUST ACQUISITION) REQUIREMENTS MEASURES INFRASTRUCTURES Cost/Risk A6 MAJCOM PMO Drivers D OSD B I S U PROGRAM OF N R Cost/Risk Cost/Risk PPBE A D RECORD S E D U Drivers Drivers O I T O L M ESC T N WORK STATEMENTS W M E R SOW VS SOO A E O A S AFSP C A I S N R I N S AFMC S SCP/ICE K N P S S O ACC R T Cost/Risk Drivers 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 4

  5. INFRASTRUCTURE  Focus on both legacy and future states simultaneously  Legacy: Live and operate in legacy state continuously  Future: What will today’s technology allow in near -term future?  New Security Model: E2E 2-way authentication & authorization  Rapid delivery  Deliver small reusable applications  Condition the institution at all levels  Address inherent disconnect between network and system developers  Manage both legacy and future states simultaneously to exploit the rapid change of technology to our advantage Out-of-the-box : Manage future & legacy states together NOT one vs the other! 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. The Dual Pathway Applications over Infrastructure CONTENT DELIVERY CONTENT GENERATION Mission Assurance Engineering and Management CAPABILITY DESIGN TECHNICAL REFERENCE Architecture APPLICATION MODEL IA/COOP/MA ARCHITECTURE (CCS) Process BUSINESS DISCOVERY REFERENCE MODEL AMPS NETWORK ARCHITECTURE Service Level Management MDE MISSION PROCESSES PRESENTATION DOTMLP STANDARDS INFORMATION ASSET F SESSION Service Lifecycle Management MANAGEMENT SERVICE REFERENCE TRANSPORT MODEL VOCABULARIES SERVICES NETWORK DATA SOURCING DATA LINK DATA REFERENCE MODEL EXPOSURE SCHEMES PHYSICAL ADS DOCUMENTATION 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 6

  7. End to End Security in the OSI Stack Single Security Level Service Service Invoker Provider Application Application Web Services Security SOAP SOAP (Authentication, Integrity, Confidentiality, Non-Repudiation) HTTP HTTP SSL TLS/SSL TLS/SSL TLS/SSL (Integrity, Confidentiality) TCP TCP TCP UNTRUSTED NETWORK IP IP IP MAC MAC MAC SSL Endpoint Service Client Service Application SSL Processor Implementation or HTTP Code 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. Baseline Definitions Baseline Description Governance Target The Target Baseline specifies the standards, The AF CEITB CCB will be the controlling protocols and implementation constraints for the body for all changes to AF CEITB CIO/CTO Phase future state of the AF IT infrastructure. It is used to documentation. This CCB reviews and inform the development of the implementation approves/disapproves configuration item The “To Be” baseline. The Target Baseline is not instantiated in instantiations and change requests to any environment, but it is thoroughly documented. existing configuration items. Approved It is continually updated based upon emerging items are submitted to the AF CIO industry standards and the evolving AF enterprise Council by the CTO for validation. architecture. Implementation The Implementation Baseline is the associated The Implementation Baseline is governed baseline of acquisition selected products and their by the ITLC or Enterprise System ACQUISITION target baseline informed/allowed configurations Engineering function and validated by Phase that implement the architecture, standards and the CTO. protocols specified in the Target Baseline. The Implementation Baseline informs the Operational Baseline of the acquisition selected products and how they are to be configured to support deployment of user applications across the infrastructure topology. The Implementation Baseline governs the implementation of the Development and Integration/Test environments. Operational The Operational Baseline is the set of components The Operational Baseline is managed by the 24 th AF validated by the Information of the Implementation Baseline appropriately RUN TIME configured and deployed across Technology Lifecycle Center (ITLC) or Phase the topology of the AF IT infrastructure to provide Enterprise System Engineering function. the required warfighter capabilities and The “As Is” performance. It specifies the exact laydown and configurations of HW and SW within all facilities in the AF infrastructure topology. 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. APPLICATIONS Condition the enterprise to develop applications  For commoditized infrastructure  Standards and protocols defined & tightly configuration controlled  Independent of data  Manage data at enterprise level  For both C2 and business processes (e.g. readiness)  Be able to attribute the user authorizations and access to the data  For IT – move from macro-level to more detailed requirements  Align requirements to mission practices  Inherently governmental function Aligns to Commercial Delivery Model (e.g. Smart Phone Apps) 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. SDDP Contextual Model Define Understand Need, LRP & Understand Needed Define Need the “M”... Processes... Performance DOTMLPF EXECUTE REQUIREMENT Actions (w/in 3 min) (Bomb a target) Load Plane Refuel Plane Plan Mission P P T T T T G Legend . . . and the Info . . .including = Task T Puts/Gets w/in ADS & IT the Processes approaches P = Info Put = Info Get G 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. SERVICE DEVELOPMENT AND DELIVERY PROCESS (SDDP)  Focus on user/war-fighter trying to solve a problem  Acquisition, engineering, testing, architecture, portfolio management platform engineering & network ops are supporting functions  Solution derives directly from DOTMLPF  Place IT requirements in user’s context  Supported by architectural sandbox  SDDP defines the function/work-to-be-done vs ownership  Translates user needs into deployed capability Pay it forward & Inherit it back! 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. 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 12

Recommend


More recommend