Open Architecture


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Advanced Processing Build Installation Schedule As you can see in this slide, we are helping to implement Sea Shield and Sea Enterprise – as I said earlier, it is hard to enable one aspect of Sea Power 21 without hitting on some of the other. The take away from this is that from FY 98 to FY 02, we have been spending less on developmental cost while getting improved detection, higher detection rate, and longer holding time. COTS-based systems have been a real boon for us, and our APB 02 numbers continue the pattern you see here. In fact, those numbers are being pulled together now, so if you are here next year you will likely see an updated version of this slide because it speaks volumes for how we are getting the warfighter the capabilities they need without overspending. NEXT SLIDE FOREIGN COOPERATION INTRODUCTION SLIDE
  • Open Architecture

    1. 1. O pen A rchitecture c CAPT Tom Strei An Enterprise Approach to Introducing Open Architectures Into Navy Combat Systems… and Beyond Statement A: Approved for Public Release; Distribution is unlimited - 02 Feb 04
    2. 2. Why Open Architecture <ul><li>Business </li></ul><ul><li>Today’s In-Service Computing Architectures are Unaffordable </li></ul><ul><li>Each Ship Class Addressing the Problem Uniquely </li></ul><ul><li>Fact of Life Replacement of Obsolete Hardware </li></ul><ul><li>Commercial Market has Already Embraced Open Architecture Approach </li></ul><ul><li>Technical </li></ul><ul><li>Current Computing Architectures Limit Capability Increases </li></ul><ul><ul><li>Current Surface Ship Computing Systems Have Been at Performance Capacity for Years </li></ul></ul><ul><li>Warfighting Concepts to Warfighting Capability Takes 5 Years to IOC </li></ul><ul><li>Computer Throughput and Speed Requirements Dictate use of Commercial Computing Technologies and Modern Software Languages </li></ul>Improved Warfighting Capability Depends on Open Architecture
    3. 3. <ul><li>1990’s </li></ul><ul><li>Proliferating Surface Ship Combat System Baselines </li></ul><ul><li>Upgrade Costs Measured in the 100’s Millions </li></ul><ul><li>Shared Memory Computer Architectures Prevent Combat System Enhancements </li></ul><ul><li>No Navy Wide nor Joint Focused Coordination of Warfare System Development </li></ul><ul><li>2000-2002 </li></ul><ul><li>Unique Warfare System Development Continues </li></ul><ul><ul><li>Surface </li></ul></ul><ul><ul><li>Submarine </li></ul></ul><ul><ul><li>Air </li></ul></ul><ul><li>COTS Introduction Challenging and Increasingly Expensive </li></ul><ul><li>COTS Real-Time Computing and Switching Matures </li></ul>How Did We Get Here? <ul><li>2003 </li></ul><ul><li>Interim Navy Documentation of OA Technical and Architectural Requirements Released </li></ul><ul><li>Embraced ‘ARCI-Like’ Process to Facilitate OA Introduction in Surface Combat Systems </li></ul><ul><li>Re-Aligned DD(X) Technical Architecture to OA </li></ul><ul><li>Teamed With SIAP for TM </li></ul><ul><li>Initiated CG 47 / DDG 51 / SSDS Plan to “OPEN” Warfare Elements </li></ul><ul><li>LCS RFP calls for OA Technical Architecture </li></ul><ul><li>OA EXCOMM: Air and Submarine Communities to Join for an Enterprise Approach </li></ul>
    4. 4. Example of Improvements to Submarine Acoustic Systems More Processing Power at Lower Cost Processing Power MFLOPS Development Costs AN/BQQ-5E APB 98 APB 00 Mean Time to Detection and Classification AN/BQQ-5E APB 98 APB 00 Mean Time of Holding after Detection Improved Detection, Higher Detection Rate, and Longer Holding Time
    5. 5. The Underlying Concept of OA Common Platform Functions OACE Common Computing Environment Common Computing Environment Common Computing Environment Surface Combatant Ship System Aircraft System CVN Ship System SCS System Unique & Common Applications & Interfaces ACFT System Unique & Common Applications & Interfaces CV System Unique & Common Applications & Interfaces Surface Combatant Ship Unique Functions Aircraft Unique Functions CVN Unique Functions Submarine System Submarine System Unique & Common Applications & Interfaces Common Functions Common Functions Common Functions Common Functions Standards Based Computing Environment Standards Based Computing Environment Standards Based Computing Environment Standards Based Computing Environment Submarine Unique Functions POSIX, CORBA, etc. POSIX, CORBA, etc. POSIX, CORBA, etc. POSIX, CORBA, etc. TM, NAV, ID, etc. TM, NAV, ID, etc. TM, NAV, ID, etc. TM, NAV, ID, etc.    Platform Unique Functions Common Computing Environment Common Architecture  Interoperable System of Systems
    6. 6. Open Computing System Definition <ul><li>Key Open Computation System Characteristics: </li></ul><ul><li>Based on Open, Publicly Available Specifications ― Preferably Maintained as Standards by a Internationally Recognized Governing Group </li></ul><ul><li>Well-Defined, Widely Used Non-Proprietary (Std) Interfaces, Services and Formats </li></ul><ul><li>Durable Component Interfaces That Facilitate Component Replacement </li></ul><ul><li>Upgradeable Through Incorporation of Additional or More Capable Components With Minimal Impact on the System </li></ul>A System That Implements Sufficient Open Specifications for Interfaces, Services, and Supporting Formats to Enable Properly Engineered Components to be Utilized Across a Wide Range of Systems With Minimal Changes , to Interoperate With Other Components on Local and Remote Systems, and to Interact With Users in a Style That Facilitates Portability. ― Open Systems Joint Task Force
    7. 7. Open Architecture <ul><li>Programmatically </li></ul><ul><li>Faster “Time to Market” </li></ul><ul><li>Facilitates COTS Refresh / Technology Insertions </li></ul><ul><li>Broader Industrial Base </li></ul><ul><li>Operationally </li></ul><ul><li>Provides Joint Interoperability </li></ul><ul><li>Enables Sea Power 21 and FORCEnet </li></ul><ul><li>Increased Capabilities and Performance </li></ul><ul><li>A Navy Wide Technical Architecture… Computing Environment Based on International Standards </li></ul><ul><li>A Navy Wide Functional Architecture… Standardization of Common Components and Critical Interfaces </li></ul><ul><li>Common and Reusable Software Applications … Across Platforms in the Joint Net Centric Environment </li></ul>What is it? <ul><li>Affordability </li></ul><ul><li>Common Software Development and Maintenance Efforts </li></ul><ul><li>Avoids Costs for Testing / Certification </li></ul><ul><li>Enables Manning Reductions </li></ul>What Does it Mean…
    8. 8. Understanding OA <ul><li>OA Will Not Result in… </li></ul><ul><li>A Single Set of Computing Equipment for All Platforms </li></ul><ul><li>A Single Set of Computer Programs for All Platforms </li></ul><ul><li>OA Will Result in… </li></ul><ul><li>A Common , Navy Wide Technical and Functional Architecture Extensible to the Joint Environment </li></ul><ul><li>Maximum Use of International Standards Based Hardware and Software </li></ul><ul><li>Maximum Reuse of Warfighting Applications and Common Service Applications </li></ul><ul><li>Rapid & Affordable Modernization and Life Cycle Support </li></ul>
    9. 9. OA Standards and Design Guidance <ul><li>OA Standards and Guidance Document (Interim) and RAPIDS Released in March 2003 </li></ul><ul><ul><li>Signatories: PEO IWS, PEO C 4 I and Space, NAVSEA and SPAWAR </li></ul></ul><ul><li>OA Functional Architecture Document (Interim) Released July 2003 </li></ul><ul><li>Some 2000 Comments Received and Adjudicated </li></ul><ul><ul><li>Documents Released to VIEWnet Fall of 2003 </li></ul></ul><ul><li>OA EXCOMM </li></ul><ul><ul><li>Pursue Enterprise Approach </li></ul></ul><ul><ul><li>Use Virtual SYSCOM: NAVSEA, NAVAIR and SPAWAR </li></ul></ul><ul><li>Developed Overview Volume 0 and Revised Volumes 1-3 </li></ul><ul><li>Scheduled to Present to VSC Level I on 18 Feb </li></ul><ul><li>Documents Intended to Evolve With Broader Community Involvement and Annual Updates </li></ul>FORCEnet Compliance Dictates Compliance With OA Documentation DRAFT
    10. 10. Computing Technology Base Multi-System Resource Mgt. & Sharing Federated Switched Networks Shared Media Networks Non-Standard Middleware Non-Standard Real-Time Operating Systems POSIX Operating Systems OMG CORBA & Pub-Sub middleware Resource Mgt. Within Subsystem Enclave Security Approach Copper Cable Plant Fiber & Wireless Integrated Early 1990s Early 2000s Tactical Applications <ul><li>Res. Mgt. Origins </li></ul><ul><li>Military Fault Tol. </li></ul><ul><li>Enterprise Mgt. </li></ul><ul><li>Web Server Farms </li></ul><ul><li>Grid computing </li></ul><ul><li>On-Demand eBiz </li></ul>Example: SQQ-89 Example: DD(X) TSCEI <ul><li>What’s next? </li></ul><ul><li>Web Services </li></ul><ul><li>Model-Driven Architecture </li></ul><ul><li>More R-T </li></ul><ul><li>Secure OS and Middleware? </li></ul>
    11. 11. OA Technical Architecture
    12. 12. Measurement Report INTEL Report Sensor Track Report Sensor Report Sensor Asset Eng Control Sys Engineering Damage Bridge RV Assets Aircraft Un-Manned Vehicle Weapons System Air / Surface Missile Land Attack Missile Torpedo Decoy Gun Boat Sensor Scheduler NRT INTEL Track Track Repository Attribute Data Track Kinematics Classification Supporting Source Track System Track Assigned Missions Action Plans Plan Mission Assessment C2 Order, Schedule & Event Tactical Picture Capability Threat Assessment (Including Identity) Action: Weapon, RV, NAV & Engineering Schedule: Weapon, RV & Engineering Event: Weapon, RV, NAV & Engineering 5.0 Mission Execution (ME) 1.0 Search / Detect (S / D) 2.0 Data / Information Services (DIS) 3.0 Planning, Assessment & Decision (PAD) 4.0 Weapon / Asset Services (W / AS) 1 2 8 2 1 3 6 3 2 4 6 8 4 2 3 5 6 5 4 8 6 2 3 4 Communications Service Action Network Schedule Message Event Network Data Links 6.0 EXCOMM Radios SatCom Display NAV Time DX / DR Databases Environment Synthetic Actions Synthetic Entities Simulator Scenario Simulator Training Action, Schedule & Event 7.0 Common Services (CS) 8.0 Training (TR) 8 3 6 Joint BF Orders Commanders Estimate COA Repository BG Orders Force Integrated Scheduler ALL 6 9 9 6 9.0 Force Planning / Coordination (FP / C) Candidate OA Common Function/Application Candidate OA Platform-Unique Function / Application Force Network Local Network (OACE) Provided Data Consumed Data OA Warfare System Domain
    13. 13. OA Strategy Category 4 OA “Common Function” Systems Category 5 Total Ship Computing Systems Required for Re-Useable Applications & Common Services Legacy Systems Modernization and New Construction Category 3 OACE Standards Based Systems Categories 1 & 2 Current Systems <ul><li>Decouples Software & Hardware </li></ul><ul><li>Enables Unconstrained Computing Growth </li></ul><ul><li>Provides Inherent Performance Improvements </li></ul><ul><li>Enables Common Functions </li></ul><ul><li>Common Warfighting Applications </li></ul><ul><li>Common Services </li></ul><ul><li>Rapid & Affordable Upgrades </li></ul><ul><li>Computational Services Provided by Platform </li></ul><ul><li>Significant Automation & Reduced Manning </li></ul><ul><li>Enhanced Survivability & Maintenance-Free Deployments </li></ul>+ + O P E N A R C H I T E C T U R E No Future Upgrades Selected Systems Interfaced to OA Conformant Systems
    14. 14. OA Development Aegis DD(X) SSDS Subs E-2C OA Functional Architecture
    15. 15. OA Fielding Strategy Equip LCS, Aegis, CVs, and Amphibs with CATEGORY 3 Capability ...OA services + Apps Define and Pursue OA Technical and Functional Architecture for Surface, Air, Submarines FY 04 - 08 FY 03 - 05 Step I Step II Step III Step IV Develop CATEGORY 4 / 5 Software Applications FY 10 and Beyond FY 05 - 10 Fleet-wide Introduction of CATEGORY 4 / 5 Compliant Combat Systems
    16. 16. Navy OA Enterprise Architecture <ul><li>E2 Specific: </li></ul><ul><li>Sensor / Weapons Suite </li></ul><ul><li>Mission-Unique Functionality </li></ul><ul><li>Mission-Unique HMI Displays </li></ul><ul><li>Aircraft Avionics </li></ul>Common Navy Platform Unique Common Joint <ul><li>CVN / L-Class Specific: </li></ul><ul><li>Sensor / Weapons Suite </li></ul><ul><li>Mission-Unique Functionality </li></ul><ul><li>Mission-Unique HMI Displays </li></ul>Common Navy Common Joint Platform Unique