TimCarey

Views:
 
Category: Education
     
 

Presentation Description

No description available.

Comments

Presentation Transcript

Current and Future IAMD Support – An Industry View: A Phased Approach to Achieving Joint Battlespace Integration : 

Current and Future IAMD Support – An Industry View: A Phased Approach to Achieving Joint Battlespace Integration AUSA Panel – “Technology Requirements to Achieve Global IAMD” Tim Carey Vice President Integrated Air Defense 7 December 2005

System of Systems (SoS): an Army and Joint IAMD Imperative : 

Current Capability System Centric Operations Terrain Restricted Surveillance / Engagements (Penetrators) Limited Interoperability Weapon System Unique Interfaces IFC ENGAGED Current SHORAD Network Centric Operations Mobile, Modular, Mission Tailored AMD Task Forces Integrated Fire Control Joint Systems Integration NOT ENGAGED BCT BCT Future Capability CORPS/DIVs See First Understand First Act First Finish Decisively Current HIMAD USMC System of Systems (SoS): an Army and Joint IAMD Imperative Any Joint Shooter … with any Joint Sensor … over Integrated Fire Control Nets

Why a Common Architecture for Integrated Air Defense?: 

Why a Common Architecture for Integrated Air Defense? Consists of Key Interfaces, Components*, and Design Patterns Required to Meet Mission/Business Objectives: Meets Required Range of Operational Requirements Complies with Customer Suggested Standards Enables Use of Off the Shelf Components Interoperates with legacy systems Technology Independent Enables Affordable Evolution Testable, Verifiable, Affordable Required Warfighting Capabilities will Drive Architecture Definition *Component is a piece of the system, May be HW, SW, or a product. Architecture HW and SW Components from Multiple Programs & Developers Integrated Framework enabling interoperability and commonality

Open Architecture is Enabled by a Common Software Modular Design: 

Independence Open Architecture is Enabled by a Common Software Modular Design Functional Architecture Open Architecture Computing Environment Application Software Component Application Software Component Application Software Component System Software System Hardware Logical Interface Direct Interface Technical Architecture Typically Determines “Openness” Defines the Direct Interfaces Defines Common Services May Influence Functional Architecture Consists of Layered Logical and Direct Interfaces Functional Architecture Implements System Functionality A Hierarchy of Related Functionality and Information Can Enable a "Plug and Fight” Capability and Integration of "Best of Breed" Application Components Modularity of Architecture Driven by Integration and Evolution Plans

Army/Joint SoS Provides a path for CTM/JTM Compliance: 

Army/Joint SoS Provides a path for CTM/JTM Compliance SIGINT Tactical Joint Track Manager (JTM) GCCS/JC2 (Common Operational Picture) Info Exchange Managers Host C2 Host Nav/Time/DX Host Weapons ES EO/IR SIGINT Radar/ IFF Radar/ IFF Sensor Adaptation Sensor Adaptation Sensor Adaptation Sensor Server Sensor Adaptation Composite Tracking (Sensor Net n) Composite Tracking (Sensor Net 1-n) Global Track Data Dissem Mgr Track Server Open Network Interface / Real-Time Infrastructure Comm Svr Multi-Source Integration Global Track Management Composite Track Data Dissem Mgr Global Track Level Host C2 Adaptation Host Services Adaptation Host Weapons Adaptation DCGS (ISR Picture) Geodetic Registration Sensor types are for example, not an exhaustive list Network Centric Enterprise Services (NCES) GMTI Imagery Operational Joint Track Manager (JTM) Acoustic External Comms Communications devices shown are examples, not an exhaustive list UHF SATCOM EHF SATCOM JTRS VRC-99 MIDS/ JTIDS Tactical Data Link Manager DDS SHF SATCOM EPLRS External Comms Adaptation Combat ID Classification Combat ID Identity Partial Compliance Leverage Solutions Server Development All Functionality and Interfaces Defined Within Content of JTM Architecture. Sub-set of Functionality Delivered Within Time-frame Considered, but Extensible to Future Solutions as They Mature Mod Army Legacy Full Compliance

Roadmap to Army then Joint IAMD: 

Roadmap to Army then Joint IAMD JLENS MEADS NASAMS CLAWS CAC2S PATRIOT AGBR THAAD SLAMRAAM IFCS Sentinel Evolution THAAD JLENS SR JLENS PTIR Patriot MFR MEADS SR MEADS FCR MRRS/MMR Sentinel Common ASMD TOC AMRAAM PAC 2 THAAD Msl PAC 3 Integrated ASMD Architecture Joint Assets Coalition Assets BMDS Sensors Elevated Sensors Maritime Sensors Space Based Sensors Ground Based Sensors Intel Sensors Interagency Assets Common C2BMC AMRAAM Army Msls Navy Msl Army Msls Integrated 3d Dimension Service Architecture Joint Assets Revolution

Summary: 

Summary Future Air and Missile Defense threats will require a much higher level of integration of existing and future systems Sensor data shared as a single integrated air picture Command and control and communications will span increasingly larger geographic areas Sea based and land based interceptor missiles must be effectively matched to targets To counter these threats an effective “System of Systems” architecture must be developed and deployed to: Accommodate integration of legacy systems, protecting the large investment in existing infrastructure Allow capability to be added incrementally (e.g., TBMs, Cruise Missiles) in a logical way.

authorStream Live Help