Inactive

Title: AEGIS Fielding and Sustainment (AEGIS F&S) Sources Sought (N00024-21-R-5121) Purpose: To support the U.S. Navy’s AEGIS F&S to provide software engineering, software maintenance, software test, ... Title: AEGIS Fielding and Sustainment (AEGIS F&S) Sources Sought (N00024-21-R-5121) Purpose: To support the U.S. Navy’s AEGIS F&S to provide software engineering, software maintenance, software test, and software installation/fielding necessary to sustain fielded AEGIS baselines until modernization or replacement. Note; this requirement is not for: Future AEGIS software capability development and delivery Development or implementation of a Continuous Integration/Continuous Delivery (CI/CD) pipeline Development, Security, and Operations (DevSecOps) implementation Surface Combatant Software Factories Other Transactional Authority (OTA) scope Canadian Surface Combatant combat system development Australian Hunter Class FFG 9 combat system development Description: This is a Sources Sought per FAR 15.201. The Department of the Navy, Naval Sea Systems Command (NAVSEA) is seeking capable sources to perform as the AEGIS F&S Contractor to support the U.S. Navy in continued fielding and maintenance of AEGIS-based combat systems for U.S. Navy, U.S. Coast Guard (USCG), and Foreign Nation Surface Combatant ship classes. The AEGIS F&S Contractor will provide the material, equipment, engineering, software maintenance and support software installations required to maintain and update existing AEGIS Weapon System (AWS) and AEGIS Combat System (ACS) installations. NAICS: 334511; Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing PSC: 1230; Fire Control Systems, Complete Background: The AEGIS Weapon System is a centralized, automated, command-and-control and weapons control system that is designed as a total weapon system, from detection to kill. This computer-based command and decision element is the core of the AEGIS Combat System. This interface makes the AEGIS Combat System capable of simultaneous operations against multi-mission threats: anti-air, anti-surface and anti-submarine warfare. The first AEGIS ship, USS TICONDEROGA (CG 47), was commissioned in 1983 and deployed six months after commissioning. Ticonderoga Class guided-missile cruisers (CGs) provide multi-mission offensive and defensive capabilities and can operate independently or as part of aircraft carrier strike groups and surface action groups in support of global operations. Ticonderoga CGs have a combat system centered on the AEGIS Weapon System and the SPY-1 multi-function, phased-array radar. The combat system includes the Mk 41 Vertical Launching System that employs Standard Missile surface-to-air missiles, Tomahawk land-attack cruise missiles, advanced undersea and surface warfare systems, embarked sea-control helicopters, and robust command, control, and communications systems in a potent, multi-mission warship. The oldest 11 cruisers have been extensively modernized, including hull, mechanical, and electrical (HM&E) upgrades as well as improved quality of life, mission-life extension, integrated ship's control, all-electric auxiliaries, and weight and moment modifications. Combat systems upgrades for CGs 52-60 and 62 include an open-architecture computing environment. Specific improvements to Cooperative Engagement Capability (CEC) and SPY radar, maritime force-protection with the Mk 15 Close-In Weapon System Block 1B, Evolved Sea Sparrow Missile (ESSM), Nulka decoy, and SPQ-9B radar, and the SQQ-89A(V)15 anti-submarine warfare suite address capability upgrades. Warfighting improvements (such as the open architecture cruiser modernization), will extend the AEGIS Weapon System's capabilities against projected threats well into the 21st Century. The Navy has commenced a modernization plan of the fleet's 11 newest cruisers, which will update the ships' combat systems and HM&E systems. This updated modernization plan provides the added benefit of extending the service lives of these ships from 35 to 40 years, ensuring relevant and capable purpose-built Air Defense Commander platforms for carrier strike groups into the mid-2030s. Combat systems modernization commenced in FY 2008 with the USS BUNKER HILL (CG 52). As of early FY 2017, seven CGs have completed Advanced Capability Build (ACB) 08 combat systems modernization, and three CGs have completed ACB-12 combat systems modernization. A smaller ship, designed using an improved sea-keeping hull form, reduced infrared and radar cross section and upgrades to the AEGIS Combat System. The first ship of the DDG 51 class, USS ARLEIGH BURKE (DDG 51), was commissioned on the Fourth of July, 1991. The USS ARLEIGH BURKE reached the designed mid-life in 2008 after 17 years of service. At the same time, the Baseline 3 and 4 TICONDEROGA (CG 47) Class Cruisers (CGs) have already surpassed their designed mid-life. To adhere to the CNO’s Sea Power 21 concept and to ensure continued viability, technology upgrades in the hull, mechanical, electrical, and warfighting capabilities are required. Modernization of these ships’ combat systems will maintain their warfighting relevance, continue supportability with new technology, and establish the computing infrastructure and computer program architecture from which additional warfighting capabilities will be implemented. Previously, an ACB method was utilized which consisted of a set of computer programs that integrated combat system elements (e.g., sensors, weapons) and capabilities with the AEGIS Weapon System. The computer programs were combined with a Technology Insertion (TI) computing environment, which included computing hardware and associated middleware/operating systems and infrastructure services, to provide a ship-specific baseline. The AEGIS Weapon System computer programs were derived from an AEGIS Modernization (AMOD) Common Source Library (CSL) to assure commonality of processing among ship class baselines, where appropriate. The CSL is a collection of specifications, source code, and documented processes and instructions used to develop and maintain software products for the AEGIS Combat System. In addition, one ACB included Government Furnished Computer Programs (GFCP) for software components that were developed as part of the Program Executive Office for Integrated Warfare Systems (PEO IWS) Combat System Product Line development effort and is maintained in a Common Asset Library (CAL). The Navy, via Foreign Military Sales (FMS), has delivered or is in the process of delivering several variants of the AEGIS Combat System to our allies. FMS baselines are a variant of Baseline 5, 6, 7, 8 and the CSL. Scope of Effort: The U.S. Navy’s AEGIS F&S Contractor shall provide software engineering, software maintenance, software integration and test, and software installation/fielding necessary to sustain fielded AEGIS baselines until modernization or replacement. The AEGIS F&S primary efforts will include: Assisting the U.S. Navy in completing installations and fielding of AWS Baselines: 9.2.2, Capability Package (CP) 22.1, Capability Package (CP) 23 10 (Flight III DDGs 125 and 26), and 9.G (USCG Offshore Patrol Cutters 1 and 2) FMS Baseline K2 for Republic of Korea FMS Baseline J7 updates for Japan’s Atago Class program FMS Baseline S3 for the Spanish Frigate program FMS Baseline A2D for the Australian Hobart Class program Performing software maintenance activities for AEGIS Baselines 5, 7, 8, 9 (9A2A, 9.2.0, 9.2.1, 9.2.2, CP 22.1, CP 23, and CP 24), 10.0, and related AEGIS Ballistic Missile Defense (BMD), USCG, and AEGIS Foreign Military Sales (FMS) baselines for Japan, Norway, Spain, Korea and Australia. Participation in Government chaired software maintenance process for Change Control Boards (CCBs), Software Implementation Board (SIB), Specification Change Request Implementation and Baseline Evaluation (SCRIBE), and other related meetings. Investigate and resolve Test Observation Reports (TORs) generated during software maintenance, identified during ship operations, and identified by other US and international government activities. Conduct software testing to include Hardware-in-the-Loop testing to verify combat system performance, system interfaces with US domestic and International systems, and support combat system certification and/or authorization. Maintain and update software related documentation, specifications and operational training curriculum. The Navy anticipates most of the work will be performed at the contractors site with potential use of Navy hardware-in-the-loop facilities for system test and verification such as the Combat Systems Engineering Development Site (CSEDS) located in Moorestown, NJ and the Surface Combat Systems Center (SCSC) located in Wallops Island, VA. The Navy expects the contractor will provide facilities for maintenance of software libraries and a test bed for software testing and troubleshooting. Attachments: The Government has included background information on the combat systems associated with this Sources Sought: PEO IWS AEGIS Fielding and Sustainment Overview (pdf) The attachment is available to US-only companies. Receipt of the attachment requires submittal of a completed and previously approved Military Critical Technical Data Agreement (DD Form 2345) or a valid CAGE Code provided to the Contracting Officer and Contract Specialist listed below. Interested parties shall provide a Capability Statement in the following format: Responses shall be limited to a total of 10 pages (inclusive of any cover page or table of contents), 1-inch margins, single-sided, 10-point Times New Roman font or larger. Figures/Graphs/Tables can be included within the page limit with 8-point font or larger text. The 8-point or larger Arial font is acceptable for the graphics. Industry shall address whether they have a facility security clearance level of TOP SECRET. Company Information Provide company name, address, DUNS number, CAGE code, and designated representative name(s) and point of contact, including phone numbers and e-mail addresses. Provide number of employees employed by company’s business unit considering this opportunity, and the geographic locations. Identify contracts within the last five (5) years with similar scope and provide brief overview of company responsibilities and magnitude of its role. If a small business, identify type of small business (e.g. 8(a), Hubzone, service-disabled veteran-owned, economically disadvantaged women-owned, or women-owned). Address the following Draft Section C, Statement of Work Scope Areas of Experience and Performance Capability Software Upgrades and Maintenance The Navy requests the company describe their current activities in software maintenance and ability to introduce upgrades to an existing software baseline. The company should describe expertise in software troubleshooting, defect documentation, coding and software testing to meet the Navy’s requirements for software maintenance. The company should specifically discuss experience in analyzing documented defect observations received from their software development team, the Lifetime Support Engineering Agent (LSEA) and other activities and defining plans for resolving high priority/high payoff maintenance issues. The company should describe their capability to maintain multiple software baselines simultaneously. The company should also describe successful approaches to integrating third-party-developed software components as a part of a planned software update. The Navy is extremely interested in the company’s proposed software metrics and data reporting that will enable the various Navy activities to monitor and assess the Contractor’s software maintenance program. Software Integration, Test and Installation The company should identify their capability and capacity to perform multiple, simultaneous integration and test events to demonstrate and validate software upgrades for the AEGIS, USCG, and FMS programs. The company should highlight prior experience in complex system level integration and their extensive knowledge in hardware-in-the-loop testing. The company should describe engineering and test expertise for the integration and testing of upgrades at the system level utilizing either the Contractor’s or Navy test sites. The company should identify their integration and test process and experience in: Developing an overarching test plan from software functions to integrated system performance verify requirements for acceptance, and Conducting test program reviews to outline key test metrics and site requirements. The company should describe their familiarity with software installation aboard in-service and shore installations, which are critical for rapid installation and certification of AEGIS and related baselines. The company should describe their experience with software installation and test teams that can rapidly install, test and resolve installation software issues in a cost effective approach. Combat System Integrated Logistics Support (ILS) The company should also summarize prior activities and capabilities in providing ILS for combat systems to include as a minimum: Providing supportability engineering to update Failure Mode and Effect and Criticality Analysis (FMECA), Level of Repair Analysis (LORA), Support and Test Equipage List (STEL) and Reliability, Maintainability, and Availability (RMA) analysis, Updating and verifying Combat Systems Operational Sequencing System (CSOSS) packages, Updating and maintaining computing equipment suite of Technical Manuals (TMs), Electronic Technical Manuals (ETMs), and Planned Maintenance System (PMS) documents (i.e. Maintenance Requirement Cards (MRCs) and Maintenance Index Pages (MIPs), Providing Diminishing Manufacturing Sources and Material Shortages (DMSMS) analysis services and identify Reliability, Maintainability & Availability (RM&A) impacts of DMSMS case resolutions, and Providing maintenance planning and provisioning for the fielded TI computing equipment suites. Disclaimer: The Navy is conducting market research to identify qualified and responsible sources that may be interested in the requirements described in this notice. This Sources Sought is issued for informational and planning purposes only and does not constitute a solicitation or a Request for Quote (RFQ). This Sources Sought is not to be construed as a commitment by the Government to issue a solicitation or award a contract. In accordance with FAR 15.201, responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. As such, the Government will not reimburse any costs associated with responding to this notice. Information submitted in response to this Sources Sought will become the property of the United States Government. Submitters should properly mark their responses with the appropriate restrictive markings. Information that is proprietary or competition sensitive will be protected from disclosure under the public records law only if properly labeled as such. Response Due Date and Government Points of Contact: Interested companies should provide a response on or before 4:00 pm EST, 05 AUG 2021. The submission should include one electronic (virus scanned) copy sent via e-mail to the Contracting Officer at melisha.mcauliffe@navy.mil and the Contract Specialist at zachary.h.cooper@navy.mil. Please include the Sources Sought Title in the subject of the e-mail. All information received that includes proprietary markings will be handled in accordance with applicable statutes and regulations. An acknowledgement of receipt will be provided for all responses received. If you do not receive an acknowledgement within two working days, please notify the points of contact listed in this notice.