Download
modular approach n.
Skip this Video
Loading SlideShow in 5 Seconds..
Modular Approach PowerPoint Presentation
Download Presentation
Modular Approach

Modular Approach

319 Vues Download Presentation
Télécharger la présentation

Modular Approach

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Modular Approach • LCS Seaframe modular in architecture • Enables multiple “focused” missions to be accomplished with use of modular mission packages • Primary, secondary & possible future missions • Separate acquisition from core Seaframe • Common core mission and HM&E systems and adapters to support multiple modules • Enables ability to reconfigure, refocus, and adapt • Integration via standard interfaces (technical architecture) developed to support current and future technologies

  2. LCS Vision Reconfigurable Mission Systems Standard Interfaces Seaframe Zones C4 Air Air Sea Sea C4

  3. Core Systems and Mission Packages + = CORE SYSTEMS • Self Defense • Navigation • C4 • Mine Avoidance • Torpedo Detection & Avoidance • Warning Shots • Detect, ID, & Track Surface Contacts • Limited ISR • Core Crew MISSION PACKAGE • Modules • Manned Aircraft • UVs • Offboard Sensors • Mission Crew = + FOCUSED MISSION

  4. Module / Seaframe Interface Concept Seaframe Zone Systems Modules Module Module Station Module Station Module Station Module Common resource stations/ panels for services connection Module PackUp Kits, etc

  5. Required Capabilities: Determined Mission Package Development & Modules Process to Select and Validate Mission Packages for Each Warfare Area (MIW, ASW, SUW) Littoral Gaps: Quantified Mission Profiles: Identified Spectrum of Modularity “Tightly coupled” Zones and Modules Module Box Mission Modules: Selected Wargaming / Analysis: Validation Large Mission Bay Zone with Greater Tolerances

  6. LCS Reconfigurability Core OA C2 system enables rapid module “plug and play” VERTREP/CONREP Innovative transfer systems for simplified module load-out Use of commercial modules enables rapid movement via ramps and cranes Rapid module shipping worldwide Multi-Purpose Flight Deck Potential for at-sea module transfer Large Offboard Vehicle Zones (Hangars) for combinations of modules Common, Reconfigurable storage Cranes, Elevators, and Innovative Technologies for internal module reconfiguration 3 Day threshold for module install & OPTEST - 1 Day objective Boat / Offboard Vehicle Ramp and/or Davits enables launch and recovery of multiple modules

  7. Target LCS Flight 0 MIW Mission Package Detect Engage Minehunting (Detect/ Classify/ Identify) Battlespace Preparation Neutralize Sweep Naval Special Clearance Team Beach Surf Zone VTUAV+ COBRA VTUAV+ COBRA Near Surface Surface Near surface & floating MH-60+ RAMICS NSCT, EOD MH-60+ALMDS 30 ft MH-60 & RMS + AQS-20 Volume MH-60 + AMNS EOD Volume and bottom mines 150 ft Close-Tethered MH-60 & USV + OASIS Close-Close- MH-60 + AMNS EOD MH-60 & RMS + AQS-20 SCULPINBP-AUV Tethered 30 ft EOD Bottom MH-60 & USV + OASIS Buried Bottom Buried * NOTE : Depth Coverages Vary with System and Mine Type

  8. Target LCS Flight 0 Ship 2 ASW Mission Package Detect Engage Non-Acoustic Sensor Surface Tactical Data Radar (ARPDD) Surv/Data Relay: VTUAV LF Active Acoustic (ALFS) Weapons Delivery MH-60R / SPARTAN USV Multi-Static Active Distributed LF Sonobuoys: ACES/EER/DMNS Family Torpedo Countermeasures Torpedo Defense Systems Mobile Units LCS Mk54 Torpedo Transmit and Receive Acoustic Arrays (RMS and Spartan USV) (Towed Array / MFTA) Distributed Passive Sensors: Advanced Deployable System

  9. LCS Mission Systems and Ship Integration Team FY03 LCS Mission Systems and Ship Integration (MSSI) IPT • Integrated Product Team (IPT) comprised of Government and Industry Reps • Reports to the LCS Program Manager • Integration efforts: • Develop & maintain Technical Architecture for LCS Mission Systems (Interface Control Document (ICD)) • Targeted Interface Development • JUSC2 ACTD, Others • Spiral Development & Technology Management • Flight 0 Mission Module offsites • T&E / experimentation OPNAV SPONSOR PEO HEADQUARTERS/ONR OTHER SYSTEMS COMMANDS LABORATORIES SEA 05D2 CDR Al Gaiser, Jeff Koleser, Pete Czapiewski 05D1 Tim Barnard SEA 03 Jim Thurber SEA 04 Charles Hall SEA 06 Colleen Cannon CDR Jim Malloy Jeff Kent Jose Casals, Roy Okamoto, Tom Owen, Miguel Rivera, Joe Schaaf, Terry Sheehan PEO C4I Chuck Auxter CDR Stone PEO SHIPS PMS 501 Bill Schoenster, Todd Tompkins, Ken Montgomery, John Vasilakos Mark Shiffler Dan Harris, Jose Velez, Guy Santora, Rob McDonald AIR 4 Bob Jackson Mike Van Ryswick PMA263 Mike Henthorne CDR Spitz PEO LMW CAPT Walter Wright PMS-420 Charles Barnes PMS-490 Philip Marshall Including Industry During LCS Preliminary Design Jack Abbott, Bill Tootle, S. Peterson Dick Vogelsong NWDC CDR Todd Haeg Chris Colby, Vic Ricci PEO IWS J. Jerry LaCamera, Jr. Adrian Eversoll SPAWAR SSC Dorrance / Chagnon DeepwaterSteve Cohen Richard Oropeza Goal: Develop a LCS Technical Architecture (Seaframe to Mission Module ICD) sufficiently “open” to insure mission reconfigurability and lifecycle technology adaptability

  10. Mission Module Contracting Approach • Separate from Seaframe contracts • PEO(LMW) lead • Direct mission module development and coordination • Develop contracts • Manages funds • Schedule development of each module to suit overall mission module schedule • PEO Ships • Overall Program Management\ • Ship integration of mission modules • Coordinate overall budgeting • Implement acquisition strategy

  11. Summary • U.S. Navy is Committed to a Littoral Combatant to Address Anti-Access Threats in the Littorals

  12. BACKUP

  13. Program Status • 23 Feb 02 ASN(RDA) directed establishment of LCS Program • 08 Jul 02 N76 letter provided interim direction to PEO(S) on top level objectives for exploratory studies for Family of Ships concept • 14 Aug 02 RFP released for Ship Concept Studies • 17 Sep 02 Establishment of LCS Program Office (under PEO(S)) • 08 Nov 02 Contract award for Family of Ships Concept Studies (focused- mission high-speed ship) • 15 Nov 02 Congressional New Start approval for Littoral Combat Ship Program ($30M Congressional Plus-up) • 28 Feb 03 Planned solicitation for LCS Flight 0 preliminary designs • Receipt of proposals 14 April 03 • Proposal evaluation 15 April-13 July 03 • Contract(s) Award 17 July 03

  14. Mid-term Schedule • Preliminary design 17 Jul 03 – 11 Feb 04 • 1st update / contract modification for option items 15 Oct 03 • Final update / contract modificationfor option items 01 Dec 03 • Industry submit proposals for next phase 31 Dec 03 • Downselect to one or two for final design 03 May 04 • Exercise 1st construction option 18 Jan 05 • Exercise 2nd construction option 31 Dec 05

  15. LCS Developmental Process is Continuing Concept Development Phase Flight 0 Flight 1 Flight 2 Fleet Battle Experiments Flight 0 Ship RDT&E Results NWC Studies Industry Concept Tailored AOA Concept Development Document Preliminary Designs Mission Analysis Analysis of Multiple Concepts Interim Requirements Document October 2005 (FY 06) January 2002 October 2004 (FY 04)

  16. LCS Execution MOA • ASN (RDA) Memo 17 March 2003 outlines PEO roles in execution of LCS program • PEO Ships charged with overall program management, acquisition, total ship systems engineering, integration of the LCS and lifecycle support • Including SeaFrame-Module Interface Control Document (ICD) • Single point of contact to Congress, OSD, Media • Overall budgeting and implementation of the LCS Acquisition Strategy • PEO Littoral and Mine Warfare (LMW) charged with Mission Module development and lifecycle support • PEO Integrated Warfare Systems (IWS) charged with platform warfare system development and ensuring compliance with computing environment Open Architecture standards

  17. LCS Flag Action Group • Established to clarify/assign responsibilities and take coordinated action to support the LCS within the accelerated and aggressive timeline • Representing organizations with responsibility over one or more critical areas that support the development of LCS • CNSL, N76, N76B, N70, N75B, N780, PEO (LMW), PEO(IWS), N76C, N77B, OLA, SEA05, DNAVSEA, N81, N61, N51, NWDC, CFFC N-8, FORCEnet, DASN (SHIPS), COMOPTEVFOR, NETWARCOM, N12, DJ8

  18. LCS Ship Integration Team • Given the complexity of the integration and Seaframe-Module ICD development challenge, we established the Mission Systems and Ship Integration IPT • Mission Modules (PEO Littoral and Mine Warfare lead) • PEO LMW Systems (Remote Minehunting System, etc) • PEO IWS Systems (Guns, etc) • PEO A Systems (Helicopters) • PEO W Systems (UAVs) • Future developmental systems and possible commercial / foreign systems • Seaframe (PEO Ships lead) • PEO IWS Systems (Guns, etc) • PEO C4I Systems (Communications, etc) • Industry/Commercial Systems (engines, etc) • Future developmental systems and possible commercial / foreign systems • Technical Authority • NAVSEA, NAVAIR, SPAWAR

  19. LCS Experimentation Battle Lab Team • To insure the development of an integrated Experimentation plan, we established an LCS Experimentation Battle Lab Team • Phase I development completed 16 July 03 • LCS T&E strategy developed; being signed • LCS experimentation roadmap process developed • Draft LCS Experimentation Roadmap developed • Extensive leveraging of HSV 2 • X-Craft use TBD • Extensive Mission Module testing outlined • Phase II initiated with “Mini-Summit” 16 July 03 • Expanded Team including Fleet, PEO IWS, NAVSEA, NAVAIR, etc. • Initial Roadmap complete 31 October 03 • Linked with LCS Spiral Development process • Updated as required Draft LCS Experimentation Roadmap

  20. LCS Experimentation Battle Lab Team FleetInput Oversight Team COMNAVSURFOR PEO C4I Chuck Auxter SEA 05D CDR Al Gaiser, Pete Czapiewski SEA 03 Jim Thurber SEA 06 TBD Dick Vogelsong PEO SHIPS PMS 501 Bill Schoenster, Todd Tompkins AIR 4 Bob Jackson Mike Van Ryswick PEO IWS CAPT Al Greco Adrian Eversoll PEO LMW CAPT Walter Wright PMS-420 CDR Jim MalloyJeff Kent Execution Team Tom Owen WB&B Mark Shiffler Ken Montgomery NWDC CDR Todd Haeg Dave Lumsden Rob McDonald , Mario Berenger, Jose Velez Brian Schires Larry Zimmerman Chris Colby

  21. LCS Flight 0 Mission Package Selection CONOPs NWC Analysis of Multiple Concepts (phase II) NWDC Technology Management PEO’s MSSIT Baseline Mission Module Analyses Mission Module Offsites Module Investment Strategy OPNAV / PEO’s

  22. Missions made possible by the removal of focused mission modules CONOPSModular Mission Capabilities

  23. Technology Management • Based on CONOPS, conducted targeted Technology surveillance • PEO’s and Naval War College • Numerous offsites for technology “harvesting” • Ongoing • Evaluation of possible candidates for LCS Mission Architecture • Facilitated by LCS Mission Systems and Ship Integration IPT (MSSIT) • Fed to analysis efforts as inputs for possible core Seaframe and Mission Modules

  24. Offsites: LCS Flight 0Mission Package Selection • Need to make rapid programming decisions supporting Mission Packages for Flight 0 due to programming cycle and aggressive LCS schedule (FY07 ship 1 delivery) • A Mission Module “Offsite” analysis process conducted • Over course of 5 months, over 150 total participants • COMNAVSURFOR, CFFC, NWDC, Fleet, resource sponsor, technical community participants • Numerous studies as input, including: • CONOPS • Technology Management study • NSWC DD Analysis of Multiple Concepts • SPA Mission Analysis • Necked down approximately 1000 systems to ~30 • Culminating in Mission Module Offsite #3 • Focused on Mission Package capability definition

  25. LCS Flight 0 Mission Modules - PB04 MIW Module Package – Ship 1 ASW Module Package – Ship 2