Synopsis_Draft SOW_ALCS.docx

STATEMENT OF WORK

AEGIS LIFE CYCLE SUSTAINMENT SERVICES

(Revision: 11/19/2019)

Section 1.0 SCOPE

Section 2.0 APPLICABLE DOCUMENTS

Section 3.0 GENERAL REQUIREMENTS

Section 4.0 INTEGRATED PROGRAM MANAGEMENT

Section 5.0 ENGINEERING/TECHNICAL SUPPORT AND SERVICES

Section 6.0 LIFE CYCLE ENGINEERING AND LOGISTICS SUPPORT AND SERVICES

Section 7.0 AEGIS WEAPON SYSTEM (AWS) ENGINEERING /TECHNICAL SUPPORT AND SERVICES FOR DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES (DMSMS)

Section 8.0 GENERAL DELIVERABLES

1.0 SCOPE

This Statement of Work (SOW) defines the efforts required for Integrated Program Management, Engineering Support and Services, Logistics Support and Services, and DMSMS Management Services in support of the AWS for the Air Dominance Department of the Naval Surface Warfare Center, Port Hueneme Division (NSWC PHD), Port Hueneme California. NSWC PHD is a field activity of the Naval Sea Systems Command (NAVSEA) and is the In-Service Engineering Agent (ISEA) for the AWS.

This SOW covers USN and (Foreign Military Sale) FMS AWS Integrated Logistics Support (ILS) efforts for baselines that are in sustainment up through those with Advanced Capability Build (ACB) 16/Technical Insertion (TI) 12H (Hybrid). It also includes any equipment in TI16 equipment that is common to baselines TI12H and below. This program requires continuation of a long-range sustainment services plan to support the development and acquisition of upgrades to the AWS and to ensure lifetime sustainment and supportability is in place for the Fleet. ILS lifetime sustainment service requirements and deliveries are driven by: AWS requirements, AWS new baseline developments and capability upgrades, upgrades and incremental improvements, the Fleet Modernization Plan, scheduled ship availabilities and operational ILS sustainment concerns. For Aegis Modernization (AMOD) and In-Service Changes ILS products are required for each change to the AWS. This SOW continues production of those ILS products from the technical data developed, as a result, of the change through testing of new equipment at Land based test sites and implementation of the necessary shipboard ILS updates.

1.1 Background

The Aegis Combat System (ACS) is the primary Surface Combat System of the U.S. Navy (USN) with the AWS as its core component. The AWS program began in 1969 with a competitively awarded development contract to Radio Corporation of America (RCA). Since that time, AWS has been fielded in all TICONDEROGA class Cruisers (22 Ships, CGs 52 - 73) and in-service ARLEIGH BURKE class Destroyers (64 ships, DDGs 51 – 113, 115). It has also been procured for those DDGs under construction (DDGs 114, 116 - 127) and planned for procurement on new construction Flight III Destroyers authorized in FY 2017; and Aegis Ashore (AA) sites. The system has also been fielded to a number of foreign Navies under the FMS.

2.0 APPLICABLE DOCUMENTS

The following documents are applicable to the tasks described herein and are for use by the contractor in the fulfillment of those tasks. The exact revisions of the documents are not cited in the text of this SOW for the convenience of reference. All of the documents listed herein are assumed to be the latest revision as of the date of award. The Government will provide direction by way of a Technical Instruction should there be a conflict between the required documents and guidance documents.

2.1 Government Document

2.2 Joint Chiefs of Staff, Department of Defense, and Department of Defense (DoD) Services Documents

Department of Defense Unique Identification (UID) Implementation Plan for DoD Maintenance Depots

2.3 Military Standards (MIL-STD)

2.4 Other Military Documents

2.5 Military Handbooks

2.6 Non-Government / Commercial Standards

3.0 GENERAL REQUIREMENTS

3.1 Security Clearances

3.1.1 With approval from the Contracting Officer’s Representative (COR), contractor personnel shall obtain and maintain a security clearance level of CONFIDENTIAL to work on specific requirements and a security clearance level of SECRET on a task-specific basis by technical instruction. Clearances shall be maintained for the duration of the period of performance. DD form 254 Department of Defense Contract Security Classification Specification shall be issued for work order.

3.1.2 In accordance with SECNAV M-5510.30, the Navy Personnel Security Program Manual (Chapter 6, Section 6-6, Paragraphs 2b and 2c), Executive Order 13467 of 30 June 2008, as well as HSPD-12 and United States Office of Personnel Management Memorandum, Final Credentialing Standards for Issuing Personal Identity Verification Cards under HSPD-12 dated 31 July 2008, the contractor shall ensure that all individuals performing work on behalf of the Government have a current, favorably adjudicated background investigation of the appropriate type to determine fitness to perform work on behalf of the Government as a contractor employee, perform sensitive national security duties, or have access to classified information. A background investigation equivalent to the current Tier requirement and which is still in scope is acceptable.

3.1.3 Contractor employees who require access to Classified Information will be processed under the terms of the National Industrial Security Program (NISP) in alignment with the work requirements of the contract and Security Requirements on the applicable DD Form 254. Contractor employees who do not require access to classified information in performance of this contract but are assigned to sensitive national security duties, require access to sensitive information, or those that for other reasons require a fitness or trustworthiness determination shall be processed for the appropriate background investigation through the NSWC PHD Personnel Security Office for a Non-NISP investigation. Point of contact is the Personnel Security Specialist, (805) 228-7196.

3.1.4 NSWC PHD Command Security Manager (CSM) shall be made aware of any Contractor personnel who have an investigation with an action pending, eligibility has been administratively withdrawn or pending, withdrawal of interim clearance eligibility, eligibility of no determination made, or final denial or revocation of Security Clearance Eligibility.

3.2 Security Procedures

3.2.1 The contractor shall ensure that their personnel comply with all applicable DoD, Department of Navy (DoN), NAVSEA and their Field Activities, local Navy installation and both New Jersey and Virginia Government Sites security instructions. They shall also, comply with all policies, procedures and guidance both on and off Government property at Virginia Sites and NAVSEA Field Activities, remote sites or travel destinations. To include following proper check-in and check-out procedures of all contractor personnel occupying Government facilities or otherwise requiring physical access to NAVSEA Field Activities or Virginia Sites.

3.2.2 Upon contractor employee separation or the termination of this contract, the contractor shall return Common Access Cards (CACs) to the appropriate Government Agency that issued the CAC.

3.3 Information Protection and Cyber Security

3.3.1 Contractor personnel granted access to any Government system shall complete Navy Information Assurance (IA) or comparable training, at the Government’s discretion, and complete and sign appropriate IA forms required to be granted continued access to Government information technology networks. The contractor shall provide information assurance certification status of contractor personnel by category and level.

3.3.2 Contractor personnel occupying any Government site or facility shall not release proprietary or sensitive information without Government consent.

3.3.3 The contractor shall ensure and update the System Security plan for and perform Safeguarding Covered Defense Information and Cyber Incident Reporting in accordance with processes and requirement identified in National Institute of Standards and Technology (NIST) Special Publication (SP) 800- 171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations”. If the system security plan in place does not meet SP 800-171, the contractor shall notify the government of any associated plans of action to describe how and when any unimplemented security requirements will be met, how any planned mitigations will be implemented, and how and when they will correct deficiencies and reduce or eliminate vulnerabilities in the systems.

3.3.4 The contractor shall possess and maintain Cybersecurity Workforce Operating System/Computing Environment certifications required by DoN and document in a Cyber Security Workforce report in accordance with Contract Data Requirements List (CDRL) A030. The contractor shall also adhere to requirements contained in the Defense Security Systems National Industrial Security Program Operating Manual (DSS/NISPOM) and document in a Cybersecurity Implementation Plan in accordance with CDRL A036.

3.3.5 Individuals who require IT-I level access to sensitive DoD and DoN IT systems require a favorably adjudicated Tier 5 investigation, and individuals who require IT-II level access to such systems require a Tier 3 investigation. All access to DoN IT systems is, at minimum, IT-II.

3.3.6 The contractor shall prepare a monthly personnel roster of individuals performing work on behalf of the government. The reporting period shall be within 30 calendar days after effective date of order. Subsequent reports shall be submitted monthly thereafter, not later than the 10th day of the reporting month. Contractor shall submit a personnel roster in accordance with CDRL A002.

3.3.7 The contractor shall provide a list of personnel and their security clearance levels for all personnel working on this contract in accordance with CDRL A002.

3.4 Safety

3.4.1 Contractor personnel shall comply with all Government safety instructions, policies, procedures and guidance while on Government property. The contractor shall request clarification of safety procedures and guidance from a Government safety observer or manager, a responsible Government employee or the COR in any case where ambiguity or confusion may arise.

3.4.2 Contractors are required to adhere to the requirements of 29 Code of Federal Regulations (CFR) 1910, 29 CFR 1926 and applicable state and local requirements while in Government spaces. The contractor shall immediately notify the COR of any serious contractor personnel injuries or deaths sustained in the performance of this requirement while at Government sites. Minor injuries not requiring immediate medical attention shall be reported to the COR by the following business day. If the COR is not available, the contractor shall notify the Contracting Officer and inform the COR as soon as possible. The contractor shall cooperate with any and all official investigations of injuries and deaths. Nothing in this paragraph shall be interpreted as to deprive any person of due process or other civil rights.

3.4.3 The contractor shall prepare an Emergency Action Plan (EAP) associated to the services performed in this SOW in accordance with CDRL A019. Contractors storing classified documentation and classified equipment at their facilities in accordance with tasking in this contract shall develop and maintain an EAP and provide a report.

3.5 Environmental Protection and Compliance

3.5.1 The contractor shall comply with all applicable Federal, State, and local laws and DoD, DoN, NAVSEA Field Activities, and Virginia Site instructions, policies, procedures and guidance pertaining to the procurement, handling, storage, transfer, use and disposal of hazardous material (HAZMAT) and Hazardous Waste (HAZWASTE) for the applicable Government sites.

3.5.2 All HAZMAT/HAZWASTE generated by the contractor during the performance of this requirement shall be the responsibility of the contractor to dispose of in accordance with applicable Federal, State and local laws, regulations and instructions.

3.5.3 The contractor shall identify to the COR when any work under this requirement that is determined or discovered to impact the protection of endangered plant or animal species, environmentally-sensitive areas, or historically or culturally significant areas or artifacts prior to commencing such work.

3.5.4 The contractor shall prepare a HAZMAT/HAZWASTE report associated to the services performed in this SOW in accordance with CDRL A038.

3.6 Contractor Facility

3.6.1 The contractor facility shall have the capability of maintaining storage of classified documents/materials up to and including SECRET. The contract shall have the ability to sanitize hardware items in accordance with the DSS Manual for the Certification and Accreditation of Classified Systems under the NISPOM.

3.7 DD Form 2772, Contract Discrepancy Report (CDR)

3.7.1 If the contractor’s performance does not meet the specified criteria, the course of action will be dependent on the severity/impact/frequency of the deficiency. Re-work shall be the first action the contractor shall employ to resolve deficiencies. When the COR (in conjunction with government technical subject matter experts (SMEs)) determines a deficiency is not Government related and is significant to the performance of the contract, a CDR, Attachment J-2 (DD Form 2772), may be initiated. The COR/SME will complete blocks 1 through 6 of the form and send it to the Contracting Officer. The Contracting Officer will evaluate the validity of the CDR and if appropriate, sign and send it to the contractor to complete blocks 9 and 10. The contractor shall return the CDR to the Contracting Officer within five business days of receipt. Upon receipt of the contractor’s response, the Contracting Officer, in consultation with the COR, will evaluate the contractor’s response and take the appropriate action. The Contracting Officer must document the evaluation (in block 11) and action taken (in block 12) on the CDR.

3.8 Communications Security (COMSEC) Requirements

3.8.1 The contractor shall apply for and maintain a Communications Security Material System (CMS) account for supporting required developmental and operational testing throughout the entire contract. This will include all related equipment, cryptographic code materials, physical and administrative security material and proper certification and periodic inspection of the CMS system.

3.9 Locations of Support - Travel

3.9.1 The contractor shall support and may travel to the following locations at a minimum:

· Naval Base San Diego in San Diego, CA

· Naval Base Norfolk in Norfolk, VA

· Supervisor of Shipbuilding (SUPSHIP) Bath, ME

· SUPSHIP Gulf Coast, MS

· General Dynamics in Bath, ME

· Huntington Ingalls Industries in Pascagoula, MS.

· Lockheed Martin in Moorestown, NJ

· Aboard AEGIS ships, both in homeport and worldwide

· Tactical and land based AEGIS Shore Sites to include:

· Vice Admiral James Doyle Combat System Engineering Development Site (CSEDS) in Moorestown, NJ

· Center for Surface Combat Systems (CSCS) in Dahlgren, VA

· Aegis Training and Readiness Center (ATRC) in Dahlgren, VA

· Production Test Centers (PTCs) in Moorestown, NJ

· Integrated Warfare Systems Laboratory (IWSL) in Dahlgren, VA

· Naval Systems Computer Center (NSCC) in Moorestown, NJ

· AEGIS Ashore, Romania and Poland

· AEGIS Ashore, Pacific Missile Range Facility, Kauai, HI

· SPY-1A Test Facility in Moorestown, NJ

· Surface Warfare Engineering Facility in Port Hueneme, CA

· Surface Combat Systems Center in Wallops Island, VA

· Various FMS Locations in Australia, Japan, Norway, South Korea This list is not all-inclusive. Contractor may be required to travel to other CONUS and OCONUS locations during contract performance.

3.10 Electronic Cost Reporting and Financial Tracking (eCRAFT)

3.10.1 The Contractor shall upload the Contractor's Funds and Man-hour Expenditure Reports in the eCRAFT System in accordance with CDRL A039 and submit the Contract Status Report on the same day and for the same timeframe the contractor submits an invoice into the Wide Area Workflow (WAWF) system. The amounts shall be the same. eCRAFT acceptance/rejection will be indicated by e-mail notification from eCRAFT. Compliance with this requirement is a material requirement of this contract. Failure to comply with this requirement may result in contract termination.

In conjunction with the COR and Contracting Officer, the contractor shall assign standard eCRAFT labor categories to each existing proposed and executed labor category on the contract.

eCRAFT reports are uploaded through the eCRAFT System Periodic Report Utility (EPRU). The EPRU spreadsheet and user manual can be obtained at: http://www.navsea.navy.mil/Home/Warfare-Centers/NUWC-Newport/Partnerships/Commercial-Contracts/Information-eCraft-/ under eCRAFT information. The eCRAFT e-mail address for report submission is: ecraft.nuwc.npt.fct@navy.mil. If you have problems uploading reports, please see the Frequently Asked Questions at the site address above.

3.11 Enterprise-wide Contractor Manpower Reporting Application (ECMRA)

3.11.1 The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Aegis Life Cycle Sustainment Services via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

3.11.2 The contractor is required to completely fill in all required data fields using the following web address: https://www.ecmra.mil.

3.11.3 Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk at https://www.ecmra.mil.

4.0 PROGRAM MANAGEMENT and CONTROL

4.1 Program Administration

4.1.1 The contractor shall provide program management oversight to ensure all work conducted within this contract is planned and executed in a manner that will achieve all quality, schedule and cost objectives.

4.1.2 The contractor shall designate a Program Manager. The Program Manager shall have complete responsibility and authority for the planning, execution, control and reporting of all aspects of the contractor’s efforts including subcontractor efforts.

4.1.3 Via the COR, the contractor shall coordinate and interface with the PEO IWS 1.0; Sustainment and Logistics (PEO IWS 1.0 SL); PEO IWS Foreign Military Sales 4.0 (PEO IWS 4.0); the NSWC PHD, and the Aegis Technical Representative (Aegis TECHREP).

4.1.4 The contractor shall manage and provide all deliverables and data products generated and associated with the contractor’s progress, status, and management reports including progress of work and status of assigned tasks. The contractor shall inform the Government of existing or potential problem areas relative to performance of work under the contract and coordinate responses and cost estimates.

4.1.5 The contractor shall generate and manage a sustainment program and implementation schedules in accordance with CDRL A040.

4.1.6 The contractor shall coordinate and conduct both formal quarterly program reviews and informal status meetings with the Government, and then generate and deliver applicable minutes and action items in accordance with CDRLs A041 and A042.

4.1.7 The contractor shall implement the procedures and controls to ensure proper and efficient generation, control, and dissemination of program data (i.e., metrics, documents, meeting minutes, ILS products, etc.) in accordance with the contract SOW and CDRL, DD form 1423. The contractor shall establish and maintain an integrated data environment (IDE) that facilitates the digital generation and electronic delivery of data, and that allows real-time on-line access to all program documentation and contract performance metrics. The contractor shall maintain the IDE through the end of the contract period of performance, or until all contract requirements are complete, whichever is later. Prior to disabling the IDE, the contractor shall provide to the Government an electronic copy of all data provided to the Government though the IDE in a manner suitable for the Government to re-constitute the data within its own IDE. The Government may order any data contained in the Data Accession List through use of the Deferred Ordering of Technical Data or Computer Software (252.227-7027). The contractor shall coordinate the approval and release, electronic (via IDE) transmittal and distribution of all CDRL and non-CDRL deliverable data items. The number of Government accounts for the Aegis IDE shall not exceed 30; 10 shall be “author” accounts, and the remaining shall be general user accounts. The contractor shall provide guidance and program management support to ensure use of proper computer format and upload of all electronic data items to the IDE server and populate the necessary Hyper-Text Markup Language (HTML) files for data item Internet access by the customer/user. The contractor shall administer CDRL requirements with NSWC PHD, and closeout all outstanding data requirements. The contractor shall analyze and recommend any future data technology improvements for incorporation and use on this program.

4.1.8The contractor shall provide budget control by reviewing performing activities manpower plans, monitoring actual expenditures and performance and controlling and monitoring cost expenditures.

4.1.9 The contractor shall monitor cost.

4.1.10 The contractor shall manage and provide interface for AWS ILS life cycle support services with PEO IWS 1.0 SL, Aegis TECHREP, NSWC PHD, NSWC Dahlgren, and Land Based Test Sites.

4.1.11 Thirty (30) days after contract award, the contractor shall submit an organization chart in accordance with CDRL A043 detailing each management, technical and engineering position working on the Aegis Life Cycle Sustainment contract from the highest company level to the team lead level with descriptions of each position, responsibilities, authority, and names of the individuals filling the positions.

4.2 Quality Program

4.2.1 The contractor shall be responsible for the quality of its products delivered to the Government by using the required DoD, Navy, or Military standards or a commercial equivalent as guidance to ensure quality products as referenced in paragraph 4.1.

4.2.2 The contractor shall deliver to the Government a Quality Program Plan of the contractor’s standard quality system in accordance with CDRL A003. The contractor shall maintain the plan and provide updates when aspects of the plan changes. The quality plan shall ensure all data submitted to the Government for acceptance is technically correct and conforms to contract requirements. The contractor shall include statistical process control techniques as an integral part of the quality system. These techniques shall be used as a means of fostering continuous process improvements.

4.2.3 The contractor shall perform or have performed the inspections and tests required to substantiate the quality of the data throughout all areas of contract performance, e.g., generation, validation, packaging, and delivery.

4.2.4 The contractor's quality system procedures shall be made available for review by the Government before starting data preparation and throughout the life of the contract. The quality system shall be prescribed by clear, complete, and current instructions and include criteria for approval and rejection of data.

4.2.5 The contractor's quality program requirements shall ensure compliance with procedures governing the preparation, marking and control of technical data as referenced in paragraph 2.0, Applicable Documents.

4.2.6 The contractor shall take prompt action to correct conditions that have resulted, or could result, in data being submitted to the Government that is not in conformance with contractual requirements. The contractor’s corrective action shall include:

4.2.6.1 Review of existing records indicating the types and number of inspections made, the types and number of deficiencies found, items of data rejected, the corrective actions taken, and the quantities of data items approved.

4.2.6.2 Review and revise, where necessary, existing procedures for conducting follow-up actions to monitor the effectiveness of corrective actions and to prevent the recurrence of discrepancies.

4.3 Configuration Management (CM) for Logistics Support

4.3.1 The contractor shall prepare a CM Plan in accordance with CDRL A022 for approval by the Government. The contractor shall provide program level guidance on CM issues within logistics support and sustainment.

4.4 Performance Metrics

4.4.1 The contractor shall use Earned Value Management to generate and deliver metrics to allow clear visibility into the program and to ensure the program remains within cost and schedule. Contractor shall submit metrics in accordance with CDRL A001.

4.4.2 The contractor shall establish, update, track, and manage all program data to efficiently measure organizational goals and ensure program objectives are being met.

4.4.3 The contractor shall use and store all program related information for the life of the contract.

4.4.4 Program management shall assemble and present all performance data to the COR.

4.5 Total Ownership Cost (TOC) Policy and Process Development

4.5.1 The contractor shall identify opportunities to reduce the TOC footprint for AWS ILS and sustainment. They shall ensure TOC reduction efforts are developed and implemented to address lifecycle concerns through the term of the contract.

4.5.2 The contractor shall develop and maintain cost modeling tools and algorithms to perform TOC analysis of AWS equipment and systems. This analysis shall include, to the maximum extent possible, the costs associated with the operation and support of the equipment in the shipboard environment.

4.5.3 The contractor shall develop and update modeling techniques; perform TOC evaluations and analysis to identify and quantify TOC costs; and perform trade-off and alternative analysis to ensure that the best solution is obtained. The contractor shall document results in a Life Cycle Cost Analysis in accordance with CDRL A020.

4.6 Sustainment Schedules for Logistics Products and Deliverables

4.6.1 The contractor shall assist the Government’s Sustainment Working Group with maintaining an Aegis Modernization and Integrated Master Schedule (IMS) for AWS logistics deliverables (i.e., Supportability Engineering, Provisioning, Technical Manuals, Planned Maintenance, Training, etc.). Contractor shall provide IMS in accordance with CDRL A040.

4.6.2 The contractor shall recommend to the Government their product milestone dates for Aegis Modernization and logistics products they will deliver to the Government for inclusion in the AWS ILS schedule. The data contains a structured list of logistics events, significant accomplishments, and accomplishment criteria and the detail tasks. The data shall identify the schedule margin/contingency as a separate line item(s).

4.6.3 The contractor shall assist the Government with developing critical paths and near critical paths, including contract deliverables, system events, and milestone reviews for ILS products in support of Fleet introduction and sustainment.

4.6.4 The contractor shall identify external schedule dependencies and notify the Government. The proposed data shall include all AWS ILS contractor and subcontractor tasks.

4.6.5 The contractor shall provide work-around and/or recovery schedules/plans, and associated impacts due to program changes.

5.0 ENGINEERING/TECHNICAL SUPPORT AND SERVICES

As directed by specific Technical Instruction, the contractor shall perform the following tasks: The contractor shall provide a wide range of engineering services including system engineering, supportability engineering, design engineering, integration and test engineering, and provide a Test and Evaluation Master Plan in accordance with CDRL A013. Other services included are change development (Engineering Change Notification (ECNs), Design Change Notice (DCNs), Engineering Change Proposal (ECPs), Ship Change Document (SCDs), Technical Data Packages (TDPs), preliminary and final ORDALT Instructions), encompassing both engineering and logistics impacts, Physical Configuration Audit support, scheduling, production, and project management capabilities linked directly to new development, sustainment for efforts related to old/legacy systems, and major upgrades or Commercial-Off-The-Shelf (COTS) Refresh of the AWS. This scope will apply to all phases of support for the AWS on Aegis Ships. Additionally, this effort may pertain to land-based training and test centers such as the PTC, ATRC, CSCS, and IWSL. This support shall be provided throughout the life cycle of the system (development to disposal).

5.1 Engineering Change Proposals (ECPs)/Non-Engineering Change Proposals (NECPs) and Deviations and Waivers

5.1.1 ECPs – The contractor shall provide Engineering Services related to development of ECPs that correct fleet problems and support technical changes to improve the AWS structure, assemblies, cabinet modules, components, and materials. This includes data collection, data analysis studies, and recommendations for special equipment, test tools, and instruments to conceive, specify, design, build, and test technical improvements, modifications, problems, and corrections as specified in applicable documents including, but not limited to the Integrated Logistics Support Plan (ILSP).

5.1.1.1 The contractor shall prepare SCDs, ECPs, and associated Rough Order of Magnitude estimates for changes to the AWS and associated AWS variants for Aegis ships and Land Based Test Sites. ECPs shall be prepared in accordance with the approved configuration management plan and in accordance with CDRL A004. The contractor shall submit an ECP whenever the detail level physical configuration, material quality, operational or functional performance of equipment or installed systems will not be in compliance with baseline design related documents (Specifications, Contract Drawings, etc.), and the Government determines a change to the baseline document is considered an appropriate means of resolving an issue. Documentation shall be developed in sufficient detail to enable Government review and evaluation of the merits of the proposed change, including cost and scheduling impact, ship class impact, and consequences if disapproved. All existing drawings and technical manuals impacted by the change shall be listed along with a brief narrative explanation of needed changes to incorporate the ECP if approved. Weight and moment data incidental to the change shall be provided. The contractor shall also prepare applicable baseline document insert sheets, with specific word changes or proposed rewrite, in accordance with CDRL A008 to facilitate baseline documentation changes to include technical manuals and drawings.

5.1.1.2 The ECPs shall include engineering design of equipment changes, ship alterations, room arrangements, interface definition, cable and connector changes, configuration changes, logistics elements, parts classification assessment, computer programming, manpower requirements and cost-and-schedule impacts. Each cost estimate shall have a detailed breakdown for engineering development, logistics, and manpower requirements. Temporary Alteration will not be accepted as official configuration control documents. In addition, the Government will review the ECP, and the contractor shall deliver to the Government at a minimum a completion of 90% technical content accuracy, for amendments, revisions, and first time submissions.

5.1.1.3 The contractor shall provide configuration management of each SCD or ECP and assist in the adjudication of design or installation issues. The contractor shall review all proposed configurations prior to and at the Configuration Control Board meetings for logistics impact and assist in the technical evaluation and resolution of board modifications. ECPs shall be boarded concurrently with the Phase IIA SCD and submitted to PEO IWS 1.0 CM, for approval, at least 30 calendar days prior to Local Configuration Control Board.

5.1.1.4 The contractor shall deliver Preliminary ORDALT Instructions to the Government for review and approval at least eight months prior to start of the first installation in accordance with CDRL A037.

5.1.1.5 The contractor shall deliver the Final ORDALT Instruction to the Government for review and approval at least 45 days after completion of first install in accordance to the applicable IMS and in accordance with CDRL A037.

5.1.2 NECPs – An NECP should be submitted in accordance with CDRL A032 whenever necessary to document administrative, procedural, scheduling, or documentation changes that do not directly impact the physical configuration of the equipment. The NECP shall explain the nature of the problem, identify the applicable baseline document (i.e., CDRL, Contract Clause, etc.) and provide a detailed explanation justifying the proposed course of action desired to resolve the problem. Insert sheets for applicable documents shall also be attached to facilitate change action in the event the NECP is approved.

5.1.3 Deviations and Waivers – In the event that a baseline design related document requirement cannot be met, the contractor shall submit a Request for Variance in accordance with CDRL A033. The explanation of "need for deviation" should provide detailed justification and consequences of approval, to include technical details explaining the degree of noncompliance or effect on ship equipment or system operation constraints. In a similar manner, a waiver shall document an "as built" configuration that departs from baseline documentation and should include any proposed corrections or modifications to better meet the intent of the baseline document.

5.2 AWS Supportability Engineering

5.2.1 The contractor shall provide logistics support program planning, schedule development and oversight for development of logistics products. In addition, the contractor shall manage and identify Logistics risk and opportunity, as well as support and development of presentation material providing logistics data and status as required at customer and internal reviews.

5.2.2 The contractor shall develop, update, and deliver Life Cycle Sustainment Plans and/or ILSP in accordance with CDRL A015 for Baseline updates, Modernizations, and/or changes in function or capability.

5.2.3 The contractor shall develop, update and deliver a Level of Repair Analysis (LORA) in accordance with CDRL A029 for Baseline updates, Modernizations, and/or changes in function or capability as applicable.

5.3 Support and Test Equipment (S&TE)

5.3.1 S&TE is made up of all equipment (mobile or fixed) required to support the operation and maintenance of a system. This includes ground handling & maintenance equipment, tools, calibration equipment, and manual & automatic test equipment. The contractor shall provide engineering and sustainment services to identify and maintain AWS S&TE requirements, including modernization applications.

5.3.2 The contractor shall deliver recommended changes to the Allowance Equipage List (AEL) in accordance with CDRL A005 and/or Technical Manuals (TMs) in accordance with CDRLs B001, B002, B003, B004, B005, B006, B007, B008, and B009, relative to changes made to S&TE requirements.

5.4 Reliability, Maintainability, and Availability (RMA)

5.4.1 The contractor shall receive process, analyze, and maintain Trouble Failure Reports (TFR), and Ships’ 3M data including 2-Kilo data files, and equipment configuration files. These shall be used to support the Failure Reporting and Corrective Action (FRACA) process, provisioning process, part criticality analysis, and support RBS and other provisioning optimization tasks for CG 47 and DDG 51 Class ships. The contractor shall coordinate and support the Navy Problem Review Board (PRB) to identify and resolve RMA problems.

5.4.2 RMA – TFRs. The contractor shall provide metrics on the following that depict actions taken to keep the Moorestown Test Beds operational (NSCC, PTC, CSEDS, other (BMD)): potential impact of pending baseline upgrades. The contractor shall provide the Government recommendations on DMSMS resolutions in accordance with CDRL A006.

5.4.3 The contractor shall provide data to the FRACA process. The contractor shall analyze TFR, 3M and depot repair data for reliability and maintainability trends/problems to identify issues/areas impacting the logistic support of Aegis Class Ships. The contractor shall compare both the original design expectations, and recent experience, to assist the Government in the development of appropriate corrective actions. The contractor shall conduct in-depth failure analysis and investigations to identify root cause, and assist the Government and provide recommendations in the development of corrective actions. The contractor shall deliver an RMA report including status of issues and recommended courses of actions for Government resolution of the issues in accordance with CDRL A006.

5.4.4 The contractor shall develop, maintain, and deliver Reliability Block Diagrams and Part to Block (PTB) files in accordance with CDRL A007 for Aegis equipment throughout the life cycle to support Government directed Readiness Based Sparing (RBS) modeling for selection of Onboard Allowance (OBA) spares sets. Each PTB file shall include system impacts of a failure for each application of all organizational level replaceable items represented within that file.

5.4.5 The contractor shall conduct failure analyses to measure the effectiveness of provisioning support throughout the life cycle and deliver reports in accordance with CDRL A006..

5.4.6 The contractor shall update and deliver FMECA reports as directed in accordance with CDRL A007.

5.4.7 The contractor shall update demand rate analysis for OBA candidates throughout the life cycle using TFR and Ships’ 3M Data System. The contractor shall deliver annual Provisioning Demand Rate Bulletins to support the RBS Process in accordance with CDRL A006.

5.4.8 The contractor shall participate in RBS and provisioning meetings.

5.4.9 The contractor shall conduct special provisioning studies in accordance with CDRL A026.

5.4.10 Studies shall include the research and development of specialized math models and computer software to aid in the optimization of the RBS process. It shall also include enhancements to the RBS process required to support expansion of RBS to include, but not be limited to, non-homogeneous or nested redundant configurations, mission availability, and multi-echelon support systems.

5.4.11 The contractor shall develop, maintain, and deliver an RMA Program Plan for lifetime support efforts in accordance with CDRL A026.

5.4.12 The contractor shall perform and deliver Maintenance Engineering Analysis and Maintenance Task Analysis in accordance with CDRL A014 for new configurations and updates to existing configurations in support of 3M.

5.4.13 The contractor shall perform RBS optimization process modeling and deliver consolidated spares lists in accordance with CDRL A012.

5.4.14 The contractor shall establish/maintain a RMA repository with Government access to share RMA data and information, such as agendas, minutes, presentation materials and reports/analyses, source data (original Lowest Replaceable Unit (LRU) reliability predicted failure rates, adjusted failure rates and superseded Part Number list), 3M data (from the Navy to the contractor) and TFR data (from the contractor to the Navy) and provide Navy agencies access to selected TFR files.

5.4.15 The contractor shall evaluate all proposed ECPs to assess criticality and impact on system availability and provide input to the ECP developers in accordance with CDRL A026.

5.4.16 The contractor shall participate in all Navy/contractor Problem Review Boards, IWS In-Service Reviews, PEO IWS 1.0 SL Quarterly Meetings, Fleet Issues Working Groups, RMA Working Group and ILS related meetings and reviews.

5.4.17 The contractor shall provide the DMSMS Program support services and identify and include RMA impacts of DMSMS case resolutions in accordance with CDRL A004.

5.4.18 The contractor shall interface and provide RMA inputs/recommendations to Supportability and Design Engineering in COTS selection in accordance with CDRL A016.

5.5 AWS Supply Support

5.5.1 The contractor shall provide engineering and logistics support services for the maintenance and sustainment of AWS Maintenance Assistance Modules (MAMs), and Operating Space Items (OSIs).

5.5.2 The contractor shall maintain MAMs configuration consistent with ECP/ORDALT requirements and Class II changes as referenced in the SL720-AA-MAN-030 Navy Modernization Process Management and Operational Manual (NMP-MOM).

5.5.3 The contractor shall monitor and maintain ECN review board packages. The contractor shall revise, update, document, and deliver any changes to the AEL COSAL and/or technical manuals relative to changes made to MAMs/OSI requirements.

5.6 Configuration Management for Aegis Weapon System (AWS)

5.6.1 The contractor shall provide CM for Government Furnished Property (GFP) and establish the CM processes, procedures and policies to enable proper support of COTS/Commercial Item/Non-Developmental Item(NDI)-based GFP by Navy Lifetime Support organizations after the equipment leaves these sites. The contractor shall coordinate the development of GFP configuration and quantity requirements for various modification, test, and integration tasks. The contractor shall document this activity in a GFP Inventory and Forecasting Report in accordance with CDRL A028.

5.6.2 The contractor shall extend to the Government the full coverage of any standard commercial warranty normally offered in a similar commercial sale, provided that such warranty is available at no additional cost to the Government. The contractor shall provide a copy of the standard commercial warranty with the item. The standard commercial warranty period shall begin upon the final acceptance of the applicable material or software.

5.6.3 The contractor shall develop and deliver configuration data in Navy Data Environment and other databases via a web-based front-end to ensure proper Configuration Status Accounting for the AWS and its components and provide CM processes to integrate unique item identification in accordance with CDRL A009.

5.6.4 The contractor shall assist the Government in performing CM including Physical Configuration Audit support of GFP requirements for equipment integrated and tested.

5.6.5 The contractor shall receive process and monitor GFP deliveries.

5.6.5.1 The contractor shall provide services to determine status and availability of GFP by collaborating with the Navy technical community and provide technical service expertise.

5.6.6 The contractor shall provide CM of the ECP process from preliminary change proposal through delivery of final documents.

5.6.7 The contractor shall maintain and deliver engineering drawings for out-of-production Aegis equipment via ECNs as directed by Technical Instruction and lifetime support organizations in accordance with CDRLs C002 and C003. Engineering drawings are a major component of a TDP. Engineering drawings disclose the physical and functional requirements of an item using graphic and/or textual presentations.

5.6.8 The contractor shall maintain a…