SOW_Addendum_1_-_Rapid_Technology_Insertion_Overview.docx

DRAFT SOW Addendum 1

1. Rapid Technology Insertion Process Description Introduction

The RTI Statement of Work (SOW) defines the requirements for the effort necessary to identify, assess, integrate, test, and field a technology or capability under the Rapid Technology Insertion (RTI) process for use on the Littoral Combat Ship. Through this RFP the Navy is soliciting technology solutions to enhance the successful completion of the primary LCS missions. The primary objective of this RFP is the development of capabilities that can rapidly transition to Fleet introduction in less than 2 years into a Mission system, Mission Module, Mission Package, or onto an LCS. Technologies must currently meet Technology Maturity Criteria (TMC) established in DRAFT SOW Addendum 2 to be considered under this RFP. In general, technologies are preferred that reduce system lifecycle cost, lower impact on ship Service Life Allowance (SLA), or reduce manpower requirements while achieving objectives.

Program Executive Office Littoral Combat Ships (PEO LCS) has twelve Technology Focus Areas, listed in Table 1. This RFP’s topics are associated with at least one of the focus areas. Each RTI solicitation will identify one or more of the Technical Focus Areas as applicable to the technology need or problem area for that solicitation.

Table 1: PEO LCS Technology Focus Areas In this procurement, the word “technology” is used to represent the capability being sought, proposed, and procured in response to an RTI Technical Challenge, and may mean a product, system, software application or program, or other capability as defined by the Contractor’s solution and proposed by the Contractor during the solicitation phase of the procurement. In some cases the phrase “product, system, or software” is added for reference, but lack of this term does not change the meaning of the word “technology” as defining the product to be delivered. Solutions being sought may also encompass non-material solutions, such as improved training or new tactics. Proposals that provide cost-effective responses to the technical challenges of this RFP without development of new systems or technology are also considered within the scope of this RFP.

2. LCS Program Background

The Littoral Combat Ships (LCS) are fast, agile, and networked surface combatants, optimized for operating in the littorals through outfitting Ships with mission-specific Mission Packages. An LCS without any Mission Package (MP) is referred to as a “Ship.” The primary missions supported by MPs are: Anti-Submarine Warfare (ASW), Mine Countermeasures (MCM), and Surface Warfare (SUW). These missions assure maritime access for Joint forces. The underlying strength of the LCS lies in its innovative use of modularity for operational flexibility. Fundamental to this approach is the capability to rapidly install a MP onto the LCS Ship to fulfill a specific mission. Similarly, an MP can be uninstalled, maintained, and upgraded at the Mission Package Support Facility (MPSF) located in Port Hueneme, CA, for future use aboard any LCS Ship. This flexible approach allows the LCS warfighting capability to adapt quickly to evolving threats using improved technology. This approach also helps to reduce the overall cost of the LCS and allows a smaller number of ship’s crew to continuously operate and maintain the Ship and its core systems.

A MP consists of Mission Modules (MMs), mission crew detachments, and support aircraft. A MM combines mission systems (vehicles, sensors, communications, and weapon systems), support equipment, Mission Package Computing Environment (MPCE) hardware and software, and Multiple Vehicle Communications System (MVCS) hardware and software. The software that is loaded into the MPCE for processing and control of specific Mission Modules (MMs) is called the Mission Package Application Software (MPAS). A MM installs into a Ship via standard interfaces. The hierarchal MP concept is best described in three ascending layers:

· Mission System = vehicles, sensors, and weapons

· Mission Module = Mission Systems + support equipment

· Mission Package = Mission Modules + mission crew detachments + aircraft

A Mission Module contains MSs, such as specialized sensors, vehicles, communication, and weapon systems, as well as support equipment, Support Containers, MPAS, MPCE, and the MVCS. The MVCS provides integrated communications for command and control of the unmanned vehicles. In addition to the hardware, the MPCE also includes operating systems and infrastructure services software.

*Note: The terms “Navy” and “Government” in this RFP are used interchangeably.

3. RTI Overview and Phasing of Project Work: All proposed projects shall be structured the same way, to provide a phased scope of work gated on project success. This phasing allows the Contractor to fully develop a test strategy, mission system integration plan, and initial fleet user assessment and support structure in the base contract scope. Relative duration and size of each phase of the project shall be consistent with how much engineering and test work is needed for the relevant technology or capability. The Phase II, III, and IV project work shall be structured as contract options, exercised at the sole discretion of the Government. The RTI program is established to seek mature technology solutions and rapidly transition them into the LCS Program and fleet use. The RTI process flow is shown in the graphic below.

NOTE: The base contract covers the Phase 1 Transition Study work scope.

Phase II, III and IV are covered by priced Options to the contract.

3.1 Phase I (Base Award, CLIN 0001): Transition Study. The Contractor shall conduct and deliver a Transition Study as the basic award scope (Phase 1) that, when approved, provides the underlying technical performance and objectives for the rest of the contract. The Contractor shall develop a Transition Study to adequately plan for the integration, test, and operational evaluation of the technology. A primary purpose of the Transition Study is to help the Navy obtain the cost of integration and lifecycle support for the new technology, including ship installation or modifications, Mission Package hardware, software integration, and training and logistics support. The Contractor shall establish exit criteria for Phases II through III in the Transition Study. All applicable Technical Warrant Holders (TWH) will be identified by the Navy in the Transition Study phase and this list will be approved by Naval Systems Engineering Directorate 05. Contractors shall propose only mature technologies (Technology Maturity Criteria (TMC) established in DRAFT SOW Addendum 2) in response to this RFP. Those projects outlining a detailed plan for transition of the technology through the RTI Phases to Fleet delivery will be considered for progression to Phase II for Engineering and Product Assessment. The Government anticipates awarding multiple contracts at this phase. The Government will exercise options it determines are in the best interests of the Government and in accordance with the terms of the contract. The Government may exercise the Phase III option to none, only one contractor, or multiple contractors, if more than one contractor is performing in Phase II, at the discretion of the Government.

The Contractor shall provide metrics for exit criteria of each project phase, data collection plans, the testing approach, and integration and test costs as identified in the Transition Study. The contractor shall provide any prior system test results or operational use data for consideration. Formal Developmental Testing (DT) and Operational Testing (OT) plans will be identified in the initial Phase I Transition Study. Phase I scope will be performed under a firm fixed price contract line. The Contractor shall also comply with SOW paragraphs 3.0 and 3.1 when completing the base contract scope. All Contract work scope after Phase I Transition Study is an OPTION to the contract and may be exercised depending upon the success of the Contractor in previous project phases and availability of funding.

3.2 Phase II (OPTION CLINs 1001 – 1004): Assessment. The assessment phase focuses on engineering and product assessment includes technology development and feasibility testing, performance assessment, and product improvement and assessment. Phase II project scope will be performed under a Cost Plus Incentive Fee (CPIF) contract line. Phase II technology evaluation will include the first three testing and assessment steps of the four step RTI process as outlined in SOW paragraph 3.2. This testing integration testing in a lab environment is to show that the technology can actually transition into the host system. Once the technology is verified via Contractor testing and developmental testing described in the above steps, the technology would be installed in the MP or on the applicable PEO LCS MS or ship. The Contractor shall deliver hardware units at the completion of this phase after completion of all contractor testing and land-based testing, including any initial land-based DT tests.

The Contractor shall comply with SOW paragraphs 3.0 and 3.2 when completing the assessment phase contract scope.

3.3 Phase III (OPTION CLINs 2001 - 2003): Ship / MM Integration & Fleet Experimentation. The Contractor shall provide Engineering Services in support of System and Ship Integration, including contractor support to install the technology on a relevant platform or system and testing at-sea. The exact nature of the Navy testing is dependent upon the type of product or technology being developed. This installation may be a Temporary Alteration (TEMPALT) of the LCS that is later converted to a Permanent Ship Alteration (SHIPALT) or MP ECP upon completion of operational testing. The Contractor shall support At-sea trials under CLINs 2001 to 2003, which will be conducted to ensure operational performance requirements are met. Data collected by the Government during this phase will be used to assess whether the Contractor reliability, availability, and maintainability (RAM) requirements will be maintained throughout the life cycle of the applicable mission system. At-sea testing will normally focus on end-to-end testing on an LCS ship to assess launch and recovery, ship integration, and crew impacts in a sustained operational mode. The project scope in this phase will be performed under a Cost Plus Fixed Fee contract line with a fixed cost and fee for each hour.

Ship /MM integration & testing will consist of other certification testing to ensure successful performance and integration testing, for example, Hazards of Electromagnetic Radiation to Ordnance (HERO)/ Hazards of Electromagnetic Radiation to Personnel (HERP), Weapon System Explosives Safety Review Board (WSESRB), Software System Safety Technical Review Panel (SSSTRP), Electromagnetic Interference (EMI)/ Electromagnetic Compatibility (EMC), Environmental qualification (shock, temperature, vibration, etc.), human factors, Information Assurance (IA), Command, Control, Communications, Computers and Intelligence (C4I) Integration, and logistics support product development as required for successful Fleet introduction. The specific testing applicable to the technology (product, software, or system) being assessed will depend upon the technology and will ultimately lead to successful testing on the LCS or other ship in an operational configuration.

In this phase, the Contractor shall provide engineering support services to the Navy during the conduct of the 4th step of the test and evaluation testing describe in paragraph 3.3. The duration of the System and Ship Integration Phase will vary appropriately for software applications, ship-based hardware and ship-launched systems, and helicopter or UAV-based systems. For biding purposes Offerors should plan for 3 short (3 day) trips to San Diego CA, and 2 longer trips (2 weeks) embarked with an LCS ship sailing from San Diego, CA.

The Contractor shall comply with the following Statement of Work paragraphs when completing the Ship/MM Integration and Fleet Experimentation contract scope: 3.0 & 3.3.

3.4 Phase IV, Fielding (OPTION CLINs 3001 - 7003). Phase IV consists of manufacture and fielding of the software application, production hardware units and/or interim repair depot support (including software support for software products). These contract options can only be awarded after completion of successful system level testing in Phase III. Phase IV project scope will be completed under firm fixed price contract lines.

The Contractor shall comply with Statement of Work paragraphs 3.0 and 3.4 when completing the Fielding contract scope.

3.5 LCS Compatibility.

All capabilities must be compatible with the Littoral Combat Ship and its Interface Control Drawings, crew capability, and launch/recovery capabilities (Ref: Interface Control Document (ICD) For the Littoral Combat Ship (LCS) Flight Zero Reconfigurable Mission Packages, Baseline 1.2, of December 04, 2009, Rev. A). All software applications must be compatible with the LCS Mission Package Computing Environment (MPCE) Version 1.9, (Ref: Common Hardware Requirements Specification for the LCS Mission Package Computing Environment (MPCE), MPCE-CD-0040 V1.0, of 12 September 2012). Copies of these documents are available via request to the NAVSEA Contracts Office Point of Contact (POC) listed below. Through each phase of the RTI project the PMO will coordinate technical requirements with the NAVSEA 05T Technical Warrant Holder (TWH) teams.

image1.png image2.png