AEGIS SESI - Sources Sought.pdf

06 JAN 2021

SOURCES SOUGHT

Title: AEGIS Systems Engineering & Software Integration (SESI)

Purpose: To Support the U.S. Navy in Systems Engineering, Integration, and Delivery of future AEGIS-based Combat Systems and Implementation of DEVSECOPS.

Note; this requirement is not for:

AEGIS baselines which will have been certified and fielded by the end of Calendar Year 2022:

Baseline 5 Baseline 6 Baseline 7 Baseline 9 Configurations 9A2A (“9o8”), 9.2.0, 9.2.1, 9.2.2, and

Capability Package 22-1 AEGIS baselines which will be in the process of actively fielding at the end of

Calendar Year 2022:

Baseline 10.0 for FLT III DDG 125 and DDG 126 U.S. Coast Guard Baseline 9G (Offshore Patrol Cutters 1 and 2) Baseline 9 Capability Package 22-2

Description:

This is a Source Sought per FAR 15.201. The Department of the Navy, Naval Sea Systems Command (NAVSEA) is seeking capable sources to perform as the AEGIS Systems Engineering & Software Integration (SESI) Contractor to support the U.S. Navy in systems engineering, integration, and delivery of AEGIS-based combat systems for U.S. Navy, U.S. Coast Guard (USCG), and Foreign Nation Surface Combatant ship classes.

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 was 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. Open architecture cruiser modernization warfighting improvements 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 was 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 Advanced Capability Build (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, an 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 maintained in a Common Asset Library (CAL).

The U.S. Navy is transitioning the monolithic AEGIS Weapon System code-base to a loosely-coupled, modular, low-propagation-cost, and scalable set of software components for the AEGIS Combat System as implemented on the U.S. Navy, U.S. Coast Guard (USCG), and Foreign Nation Surface Combatant ship classes. Additionally, the U.S. Navy is transitioning the AEGIS program’s combat system development, integration, and delivery lifecycle to a “DEVSECOPS” methodology in order to foster collaborative learning and collaborative relationships between development and operations to be lean, Agile, and capable of responding rapidly to changing technological demands.

To successfully achieve this transition, the U.S. Navy has established a prototype known as “The

FORGE.”

The FORGE is a U.S. Navy Surface Combatant Software Factory. The FORGE provides a Government furnished virtual and physical ecosystem to foster Agile software development using DEVSECOPS tools and principles. The ecosystem furnishes: Infrastructure as a Service (IaaS), Platform as a Service (PaaS), a Continuous Integration/Continuous Delivery (CI/CD) Pipeline, an Innovation Hub, and cross-functional teams lead by Government Product Owners enabling capacity-based Agile development of mission applications supporting the delivery of capabilities to U.S Navy Surface Combatants and allied partners.

The FORGE is a separate Navy transaction being pursued utilizing the Other Transaction authority of 10 U.S.C. § 2371b. Software developed at The FORGE by Mission Application Teams (MATs) shall deploy across multiple Surface Combatant ship-classes including Cruiser (CG 47), Destroyer (DDG 51), Littoral Combat Ship (LCS), Future Guided Missile Frigate (FFG(X)), Large Unmanned Surface Vessel (LUSV), U.S. Coast Guard (USCG) Cutters, and Foreign Nation Surface Combatant ship classes.

Scope of Effort:

The U.S. Navy’s AEGIS SESI Contractor shall provide systems engineering and capability integration at, from, and to The FORGE, combat system level integration and test, architecture support, weapon system installation support and Fleet software DEVSECOPS, and training curriculum development and execution.

The Contractor shall provide the material, equipment, and technical engineering required to define, design, document, integrate, test, deliver and support AEGIS-based combat systems using a DEVSECOPS methodology to provide:

• Continuous Integration

• Continuous Delivery

• Continuous Deployment

• Continuous Security

The Contractor shall collaborate with the contractors and stakeholders at The FORGE, and support the Government on-site and virtually at The FORGE. The Contractor's primary efforts shall include:

• Assisting the U.S. Navy in delivering, managing, maintaining and evolving the AWS code-base for applicability to any and all AEGIS-based ship classes including, but not limited to, CG 47, DDG 51, Littoral Combat Ship (LCS), Future Frigate Guided Missile (FFG(X)), Large Unmanned Surface Vessel (LUSV), U.S. Coast Guard (USCG) Offshore Patrol Cutter and USCG Polar Security Cutter, and Foreign Nation ship classes.

• Integrating new software capabilities, delivering future integrated warfare functionality, and enhancing existing warfare areas within the AWS code-base,

• Integrating new and existing sensors and weapons with the AEGIS Combat System (ACS) and conducting system level testing for U.S. Navy combat system certification and acceptance,

• Collaboratively designing software architecture updates in support of future combat systems requirements, and

• Implementing DEVSECOPS and Agile methodologies to test and integrate new capabilities provided by The FORGE.

Attachments:

The Government has two (2) attachments to this Sources Sought:

1. Draft Section C, Statement of Work

2. Draft DD form 254 Security Specifications

The attachments are available to US-only companies. Receipt of the attachments 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, 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.

Industry shall address whether they have a facility security clearance level of TOP SECRET.

1. 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).

2. Address the following Draft Section C, Statement of Work Scope Areas of Experience and

Performance Capability

i. Systems Engineering

The Navy requests the company describe their current activities operating in an Agile and DEVSECOPS environment providing support for prime software developers in a similarly complex model. The Navy is interested in the company describing their experience with the following:

• Domain expertise in DoD Combat Systems

• Requirements engineering

• Model Based Systems Engineering (MBSE)

• Models, SIMs, and STIMs for analysis, development and testing of capabilities

• Collaboration with Government and other prime Contractor personnel in an Agile environment

ii. Integration and Testing

The Navy envisions that the Contractor will collaborate with other prime software developers and the Government to enable seamless software capability transition for integration. The Navy requests the company describe their current activities integrating and testing similar DoD Combat Systems capabilities. The Navy is interested in the company describing their experience with the following:

• System and design level models with MBSE

• System-of-System testing

• Facilitation of Impact Level 6 (IL6) and IL5 cloud continuous connectivity

• Maintaining platform parity

• Distributed Testing

• Coordination of multiple development and operational environments

• DoD Combat System capability integration

• Automated Configuration Management

• Weapon System and Combat System integration testing

• Defect identification and TOR generation

iii. Installation Support and Fleet Support

The Navy requests interested parties describe their current activities in installation support for DoD combat systems, and Fleet Response. The Navy is interested in the company describing their experience with the following:

• DoD Combat System computer program installations, checkout, and system test efforts

• Technical Team support to the Fleet in the form of:

o Deployment of ship riders o Continuous Process Improvements events o User feedback/assessments on combat system human-machine interfaces

iv. Training

The Navy requests interested parties describe their experience in the development of curriculum, technical training, training product development, and abroad install-training for the U.S. Navy and foreign partners in the following functional areas:

• DoD Combat Systems

• Factory and Pilot curriculum

• FMS

3. Barriers to Competition

Please identify any obstacles to competition for the proposed scope for AEGIS SESI effort in such areas as: classification requirements, capability requirements decomposition, Continuous Integration/Continuous Delivery (CI/CD) pipeline, Government approval process, Definition of Done, integration/coordination with other Prime contractors, infrastructure investment, facility requirements for integration and validation/verification, and/or proposed scope areas. In addition, the company may recommend solutions or mitigation paths for the Navy to overcome the obstacles.

4. Virtual Industry Day

Please indicate if your company would be interested in participating in a virtual industry day hosted by NAVSEA in 2nd quarter, calendar year 2021.

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 Source Sought is issued for informational and planning purposes only and does not constitute a solicitation or a Request for

Quote (RFQ). This Source 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 Source 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, 10 FEB 2021. The submission should include one electronic (virus scanned) copy sent via e-mail to the Contracting Officer at patrick.loftus@navy.mil and the Contract Specialist at zachary.h.cooper@navy.mil.

Please include the Source 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.

mailto:edward.rogan@navy.mil mailto:zachary.h.cooper@navy.mil