Attachment 1 - N6852024R0044 Statement of Work.docx

CUI N68520-24-R-0044

STATEMENT OF WORK (SOW)

For

Reliability-Centered Maintenance (RCM), Integrated Maintenance Concept/Plan (IMC/P), and Condition-Based Maintenance Plus (CBM+) Support For New Procurement and In-Service Aircraft

N68520-24-R-0044 Attachment 1

21 AUGUST 2024

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U. S. DoD Contractors only (Administrative or Operational Use), (14 FEB 2024). Other request for this document shall be referred to Commander, Naval Air systems Command (PMA-299), RADM William Moffett Bldg, 47123 Buse Rd, Bldg 2272 Patuxent River, MD 20670-1547.

Controlled by: DEPARTMENT OF THE NAVY Controlled by: COMFRC CUI Category: General Procurement and Acquisition and Source Selection Distribution/Dissemination Control: FEDCON POC: Robert Miedzinski, robert.m.miedzinski.civ@us.navy.mil

Table of Contents

Statement of Work (SOW) Reliability-Centered Maintenance (RCM), Integrated Maintenance Concept/Plan (IMC/P), and Condition-Based Maintenance Plus (CBM+) Support For New Procurement and In-Service Aircraft

1. Scope

1.1 Naval Air Systems Command (NAVAIR) Commander, Fleet Readiness Centers (COMFRC) requires Enterprise-level Reliability Centered Maintenance (RCM) analysis of aircraft engines, aircraft systems (i.e. Weapons, aircrew escape systems, avionics, and electrical systems), Support Equipment (SE) (i.e., avionics SE, non-avionics SE, and aircraft launch/recovery equipment), and depot plant equipment. RCM includes Condition-Based Maintenance Plus (CBM+) and Integrated Maintenance Concept and Plan (IMC/P) support.

1.2 RCM is an analytical process to determine the appropriate failure management strategies, including preventive maintenance (PM) requirements and Other Actions (as defined by NAVAIR 00-25-403 and COMNAVAIRFORINST 4790.20 series) that are warranted to ensure safe operations and cost-wise readiness. This process of developing PM requirements, with an auditable documentation package, is based on the reliability of the various components, the severity of the consequences related to safety and mission if failure occurs, and the cost effectiveness of the task. The NAVAIR 00-25-403 manual is the primary document for anyone tasked with implementing an RCM program or performing an RCM analysis on NAVAIR managed equipment.

1.2.1 IMC/P is one of many processes used to define the support system for a weapon system or other physical asset. The primary role of IMC/P is to define PM requirements and integrate tasks across all maintenance levels, balancing the operational, engineering, and fiscal aspects of a platform’s PM program, helping to reduce the amount of out-of-service time for scheduled maintenance. IMC/P is dependent on the input of a properly performed RCM analysis. Additionally, to implement the results of an RCM analysis, additional supportability analysis processes are required. Any new PM requirement or changes to an existing PM requirement will require a maintenance task analysis to determine the product support elements, such as consumables and tools, needed to accomplish the task. Changes to any elements will require the accomplishment of additional processes to implement those changes.

1.2.2 NAVAIR Programs are required to integrate CBM+ technologies and processes into current weapon systems, equipment, and materiel sustainment programs where it is technically feasible, improves materiel availability, and is cost-effective to do so per NAVAIRINST 4790.38. CBM+ implementation results in maintenance practices that monitor the condition of equipment to implement diagnostic and prognostic alerts to take appropriate maintenance actions and ultimately avoid consequences of failure. It employs real-time, or near real-time, assessments of data obtained from equipment or external tests and measurements, using either test equipment or physical inspections. CBM+ allows maintenance to be performed based on evidence of need but has broader goals since it is built upon RCM and Condition Based Maintenance (CBM). CBM is important because it allows maintenance to be performed based on evidence of need while ensuring safety, reliability, availability, and affordability.

1.3 RCM, CBM+, and IMC/P are required in support of all NAVAIR National Sites, including NAVAIR Headquarters at Patuxent River, MD, the Naval Air Warfare Center Aircraft Divisions (NAWCADs) at Patuxent River, MD, Lakehurst, NJ and Orlando, FL; the Naval Air Warfare Center Weapons Divisions (NAWCWDs) located at China Lake, CA and Point Mugu, CA.

2. Applicable Documents:

Additional applicable documents and DoD specifications may be included at the task order (TO)level. Copies of the listed documents can be requested through the Contract Specialist.

2.1 Department of Defense Specifications

2.1.1 DoD Directive 5000.01 Defense Acquisition System

2.1.2 DoD Instruction 5000.02 Operation of the Adaptive Acquisition Framework

2.1.3 SECNAV 5000.2 Navy Acquisition Policy

2.1.4 SECNAV M-5510.30 Department of the Navy Personnel Security Program

2.1.5 DoD Instruction 4151.22 Condition Based Maintenance Plus CBM for Material Maintenance

2.1.6 32 CFR part 117 to the Code of Federal Regulations (CFR), National Industrial Security Program Operating Manual, (NISPOM), 24 February 2024

2.1.7 SECNAV M-5510.36B, Information Security Program, 12 Jul 2019

2.1.8 DoDM 5400.07, Freedom of Information Act (FOIA) Program, 25 Jan 2017

2.1.9 DoDI 5230.24, Distribution Statements on Technical Documents, 10 Jan 2023

2.1.10 DoDI 5200.48, Controlled Unclassified Information, 6 Mar 2020

2.1.11 DoDD 1035.01, Telework Policy for Department of Defense, 08 Jan 2024

2.1.12 SECNAV M-5510.30C, Personnel Security Program, 24 Jan 2020

2.1.13 OPNAVINST 3440.17A, Navy Installation Emergency Management Program, 1 Aug 2014

2.1.14 Department of Defense Standards (and all revisions)

2.1.15 DoD Joint Travel Regulations (JTR), 01 August 2024

2.2 Department of Defense Standards

2.2.1 None

2.3 Other Government documents

2.3.1 NAVAIR 00-25-403 Naval Aviation Reliability-Centered Maintenance (RCB) Process

2.3.2 COMNAVAIRFORINST 4790.20 (series) The Naval Aviation Maintenance Program (NAMP)

2.3.3 Data Item Descriptions (DIDs)2.3.4 DoDM 4151.25 Reliability-Centered Maintenance

2.3.5 OPNAV 4790.16 Condition Based Maintenance Policy

2.3.6 Marine Corps Order 4151.22 Condition Based Maintenance Plus Order

2.3.7 NAVAIRINST 4790.38 Condition Maintenance Plus Program

2.4 Industry documents

2.4.1 GEIA-STD-0007 Logistics Product Data

2.4.2 SAE JA1011 Evaluation Criteria for Reliability-Centered Maintenance Processes

3. Performance Requirements

3.1 General Requirements

3.1.1 Compatibility - The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government Information Technology (IT) environment through the security classification of UNCLASSIFIED. The current operating environment required for this contract includes:

Microsoft Windows 10 Microsoft Project 2010 Microsoft Office Professional Plus 2010 Microsoft Teams Adobe Acrobat XI (reader) Internet access

The Contractor shall maintain the ability to interface with and transfer data to and from the requiring office software applications and their upgraded versions including the Integrated Reliability-Centered Maintenance System (IRCMS), Joint Deficiency Reporting System (JDRS), Decision Knowledge Programming for Logistics Analysis and Technical Evaluation (DECKPLATE), Standard Data Repository (SDR), Joint Technical Data Integration (JTDI), Asset Management Program (AMP), Air Force Safety Automated System (AFSAS), Federal Logistics Data (FED LOG), and Automated Data Capture System (ADCS).

The Contractor shall use software capable of performing RCM and related data analyses, such as Weibull and Crow-AMSAA. Modeling and simulation toolkits may also be required to perform RCM tasking. The Contractor shall ensure that all media are virus free when delivered. The Contractor shall be capable of communications with all NAVAIR sites. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with all task order technical points of contact (TPOC) during working hours whether at Contractor work site or on travel.

3.1.2 Work Location and Facilities

3.1.2.1 Work location: At the discretion of the Government requirement office, it is anticipated that the predominance of task order performance will be conducted at the contractor’s facility (off-site) with the possibility of an occasional TO requirement for performance at Government facility (on-site).

Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.

Access to Government facilities will be provided during normal business hours (Monday through Friday, 0600 - 1800 hours) or other applicable timeframes as required to support work activities.

3.1.2.2 Meeting support: Meeting Support shall be identified in individual TOs in support of the tasking outlined in this SOW.

3.1.2.3 Telework/Remote Work: The Contractor may allow employees to telework and/or work remotely with approval from the COR in writing, that a position’s tasking is eligible for telework and/or remote work. The Contractor may utilize alternate worksites/locations to telework and/or work from a remote location to support continued performance of SOW tasks in accordance with company policy. When using telework and/or remote work, the Contractor remains responsible for contract performance and compliance with any applicable cost accounting standards and contract cost principles / procedures.

3.1.3 Contract Status reporting. The contractor shall provide the following documentation:

3.1.3.1 Monthly Status Report: The contractor shall provide status of progress toward objectives in accordance with the Contract Data Requirement List (CDRL A001 Status Report). The report shall include work accomplished, and by whom, since submittal of the last report.

3.1.3.2 Monthly Funds and Man-Hour Expenditure Report: The contractor shall provide a funds and man-hour expenditure report including both monthly and cumulative man-hour labor costs expended by labor category, material, and travel costs, in accordance with the Contract Data Requirement List (CDRL A002 Funds and Labor Hour Expenditure Report).

3.1.4 Work Schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.

3.1.4.1 Work schedule: The Contractor shall provide the required services and staffing coverage during normal working hours. Government core working hours are 0800-1600, and normal working hours each day are usually 8.5 hours (including a 30-minute lunch break), Monday through Friday, unless otherwise conducted in accordance with paragraph 3.1.4.1.1 or federal holidays occur as specified in paragraph 3.1.4.1.2.

3.1.4.1.1 Compressed Work Schedule (CWS): CWS is an alternative work schedule to the traditional five 8.5-hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: Eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is eighty (80) hours worked every two weeks, with 44 work hours one week and thirty-six (36) work hours the other.

The Contractor may allow its employees to work a CWS schedule provided the requirements of this SOW are met. If the contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the Government.

3.1.4.1.2 Holidays: The Government observes the Federal holidays identified on the Office of Personnel Management (OPM) website: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview.

The Contractor is permitted to observe the above Federal Holidays in accordance with its corporate policy.

3.1.4.1.3 Installation closure: When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility in support of such Federal employees shall follow their parent company’s policies.

While generally, contractor personnel may not perform work on-site at a government facility without oversight from Federal personnel, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential.

3.1.4.1.4 Overtime: Overtime is not authorized under this contract.

3.1.5 Other Direct Costs:

3.1.5.1 Travel: The Contractor may be required to travel as specified in individual TOs. Travel costs shall be identified in individual TOs. Travel may include general and administrative expenses but shall not include profit/fee. If required, temporary travel locations may include those location in paragraph 1.3.

3.1.6 Subcontractors: Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this SOW shall flow down to subcontractors providing support under this contract.

3.1.7 Management of Contractor Personnel: The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for, individual contractor employees. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services.

3.1.8 Performance Transition

3.1.8.1 Transition In. The Contractor shall facilitate transition of requirements so as to maintain the mission of RCM with minimal impact. Transition coordination shall begin on the effective date of the award and shall be complete thirty calendar days after the effective date, at which time the Contractor shall conduct performance required by task orders. The Contractor shall identify Points of Contact (POCs) for liaisons between the Government, the prime contractor (if applicable), and other contracted industry partners to ensure a proper and orderly transition and transfer of services and data between the parties cited. The Contractor shall ensure minimum disruption to vital Government business and shall ensure that there is no service degradation during or after transition.

3.1.8.2 Transition Out: The Contractor’s overall transition out strategy shall be built around maintaining the missions of all affected NAVAIR programs and divisions with no impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Prior to termination or expiration of the contract, the contractor shall ensure an orderly transition of performance and responsibilities, with no impact to the operation. The contractor shall submit a Transition Out Plan, to include the minimum elements listed below in accordance with CDRL A005 Phase-Out Transition Plan.

- Work Turnover. The contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the Government personnel for the period of transition via weekly status meetings.

- Quality Assurance. The contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

- Risk Mitigation Strategies. The contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

- Data/Information Transfer. The contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.1.9 Government Furnished Property (GFP)/Government Furnished Information (GFI):

The Government reserves the right to furnish Government Property and Information on an as needed basis at the TO level. The Contractor will be accountable for and required to manage and track GFP in accordance with applicable Government property clauses and reporting requirements.

If a TO is issued to support the Government with performance solely on-site, the Government will provide access to a Navy Marine Corps Intranet (NMCI)-issued computer, desk, phone, fax machine, copier, scanner, and associated materials. This property is considered “incidental” property per FAR Part 45 and shall not be tracked as accountable to the contract.

NMCI Assets that are removed from the Government location are considered GFP and will be listed as accountable to the applicable TO and shall be managed by the Contractor in accordance with FAR Clause 52.245-1 and will be listed as “Scheduled Government-Furnished Property (SGFP)” as attached to the contract or applicable task order.

The Contractor shall not utilize any GFP and GFI for purposes other than those authorized for the performance of this contract. All GFP and GFI is the property of the U.S. Government and is not to be transferred by any individual or agency, public or private, without the express written approval of the Contracting Officer, except as required for the specific performance of the TOs. The Contractor shall maintain formal records of GFP. The Contractor shall exercise reasonable safeguards and care for the GFP. The Contractor shall comply with the following regulations: FAR 52.245-1, DFARS 252.245-7001, and DFARS 252.245-7002. Disposition of GFP/GFI shall be made at contract completion.

3.2 Security

3.2.1 Citizenship Requirements: Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

a. The individual's name, date and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific government contract (specify contract number).

e. A statement that the Contractor has obtained an export license for the information required to perform the contract.

3.2.2 Investigative Requirements:

3.2.2.1 Unclassified: All Contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAV M-5510.30C. All Contractor personnel executing unclassified tasking under this contract are required to have a favorably adjudicated Tier-3 investigation from the Office of Personnel Management. The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government Security Office shall initiate the Contractor's Electronic Application for Investigations Processing (eApp, shall do a preliminary screening of the Contractor's eApp for suitability and derogatory information. The Contractor employee shall provide all requested information pursuant to the Privacy Act of 1974. The Government Security Office may deny the Contractor access to Government facilities and information and may prohibit the Contractor employee from performance of duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor employee's eApp, in such cases, the Contractor employee may not perform on the Contract.

3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR).

3.2.3.1 SAAR: All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR) DD Form 2875 on file by the TPOC, with required Department of Navy Cyber Awareness Challenge Training Certificate. New employees must submit their SAAR forms within thirty (30) days after their first day of work. SAAR forms shall be submitted to the TPOC or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.2 Common Access Card (CAC) / Local Badges: Contractor CACs and facility specific identification badges will be issued by the Government to access Government IT systems and for on-site contractor personnel that require access to Government facilities, as required, for performance of tasks under this contract. Badges shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to specific site security instructions and facility guidance. All CACs and identification badges issued to Contractor employees shall be returned to the TPOC or COR at the Government site in accordance with instructions and facility guidance following completion of the contract; relocation or termination of an employee; or upon request from the PCO, COR or TPOC.

3.2.4 INFORMATION SECURITY:

3.2.4.1 Reserved

3.2.4.2 If the work is performed at the Government's facility, the Contractor shall comply with instructions/guidance by the specific facility that the work will be taking place in. Contractor shall not store or transmit Controlled Unclassified Information (CUI) on personal information technology systems or via personal e-mail. E-mail containing any DoD CUI shall be encrypted. Prior to sending CUI to any non-Navy Marine Corps Internet (NMCI) addressees, the sender must first positively verify all recipients are authorized access to CUI and have need-to-know. Non-NMCI recipients must have a DoD compliant Private Key Infrastructure certificate that enables electronic transmission via unclassified networks while protecting the CUI with a digital signature and encryption.

3.2.4.3 If the work is performed at the Contractor's facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulations Part 117, NISPOM Rule and SECNAV M-5510.36B and DoD CUI Instruction 5200.48, Department of the Navy, Information Security Program.

All contractor facilities shall provide an appropriate means of storage for CUI and materials. All CUI including legacy FOUO information and Covered Defense Information (CDI) (meeting the definition DFARS Clause 252.204–7012, Safeguarding Covered Defense Information and Cyber Incident Reporting) generated and/or provided under this Contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, Controlled Unclassified Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF

3.2.4.4 Marking. All information generated by the Contractor shall be properly marked.

Any product containing CDI shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24, Distribution Statements on Technical Documents and have this statement displayed per DoDI 5230.24, Enclosures 3 and 4. Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this Contract shall be referred to the TPOC/COR of this Contract for approval.

Classified information shall be marked IAW DoDM 5200.01, Vol 2, Marking of Classified Information.

CUI, including Legacy FOUO information generated and/or provided under this Contract shall be marked IAW DoDI 5200.48. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DoDI 5230.24 and program Security Classification Guidance.

3.2.4.5 Public Release: Any CUI pertaining to this contract shall not be released for public dissemination, including posting to any social media sites, unless it has been approved for public release by appropriate United States of America Government authority. Proposed public releases shall be submitted for approval prior to release through Commander, Fleet Readiness Centers Public Affairs Office, via the COR.

3.2.4.6 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information: All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC and Government Security Office within 72 hours of the incident occurring.

3.2.4.7 Compliance to NIST 800-171

3.2.4.7.1 The Contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), or establish a System Security Plan(s) (SSP) and Plan of Action & Milestones (POA&M) that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

3.2.4.7.2 Notwithstanding the allowance for such variation, the contractor shall identify their plans in the SSP and POA&M to implement the following, at a minimum:

a. Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as Computer Numerical Control (CNC) equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

b. Implement Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

c. Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

d. Audit user privileges on at least an annual basis;

e. Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

f. Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which shall be evaluated by the Navy for risk acceptance.

g. Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

3.2.5 Operations Security (OPSEC): The Contractor shall develop, implement, and/or maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard NAVAIR or NAVAIR sites, the contractor shall comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts. Include OPSEC as part of its ongoing security awareness program and take all required Agency training. Be responsive to the Supporting OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the requirement office and contractor in support of the mission. (CDRL A003 Operations Security (OPSEC) Plan)

3.2.6 Anti-Terrorism Force Protection and Emergency Management: The work performed on this contract is not Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials’ direct curtailment of operations to “Mission Essential Only”. All Contractor personnel assigned to a government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.

3.2.7 Reserved

3.2.8 Data Monitoring: In the event of a cyber-incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Naval Criminal Investigative Service (NCIS) and associated law enforcement agencies, which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, or vendor logs that show network activity, including any additional logs the Contractor, subcontractor, or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor shall cooperate with the NCIS to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the Contractor.

In all cases, the collection or provision of data and any activities associated with this contract shall be in accordance with federal, state, and non-US law.

3.2.9 Reserved

3.3 Detailed Support Requirements

3.3.1 RCM and CBM program analysis support:

3.3.1.1 RDT&E: Program analysis efforts using RDT&E funds shall support RCM execution for weapon systems/aircraft/engines and their systems/sub-systems/SE development activities. These activities include testing as well as other program related development efforts for programs committed to production prior to completion of the R&D phase, developmental items, prototype items, and test items in support of weapon systems/aircraft/engines. The Contractor shall:

3.3.1.1.1 Provide the government technical input or recommendations to the germane RCM and CBM+ program plan. Draft or provide technical input or recommendations to the existing germane program RCM ground rules and assumptions (GR&A) document as deficiencies are identified.

3.3.1.1.2 Perform RCM analyses for any formal design changes and any new equipment. Review proposed new equipment for RCM analysis/maintainability considerations. Perform RCM analysis on systems in accordance with the germane RCM GR&A and the NAVAIR 00-25-403 RCM Process. Use Original Equipment Manufacturing (OEM)/vendor Failure Mode, Effects and Criticality Analysis (FMECAs) and RCM and/or a baseline comparison system, if applicable.

3.3.1.1.3 Evaluate existing or develop RCM analyses which includes data gathering and its analysis, updating supportability failure modes, effects, and criticality analysis (SFMECA), and providing recommendations for PM tasks, including those for the use of health management capability and Other Actions. Provide the government results, findings, recommendations through documentation in IRCMS.

3.3.1.1.4 Draft or provide the government technical input or recommendations to the germane program’s RCM Hazard Risk Assessment Matrix to categorize system failure risks and determine which failure modes require RCM analysis to mitigate safety, availability, and environmental risks and minimize costs.

3.3.1.1.5 Draft or provide the Government technical input or recommendations to the germane program’s IRCMS hardware tree or partition (as defined by NAVAIR 00-25-403) for purposes of performing RCM analysis.

3.3.1.1.6 Perform statistical tests and analyses, including Weibull, Crow-AMSAA, reliability analyses, and root cause analyses related to the failure modes tracked in IRCMS. (CDRL A004 Technical Report – Study/Services)

3.3.1.1.7 Perform research, data collection, data filtering, and data analysis tasks using various systems that may be owned by the Government, OEM or other vendor to include, but not limited to, VECTOR, ADCS, JDRS, and Maintenance Repair Overhaul (MRO). The data used will vary depending on the purpose of the analysis and may include predicted and test data. (CDRL A004 Technical Report – Study/Services)

3.3.1.1.8 Provide recommendations for the development of maintenance support system requirements including tooling, facilities, manpower, and process requirements.

3.3.1.1.9 Evaluate any existing Organizational, Intermediate and Depot Level maintenance tasks, conduct performance measuring and data collection of these tasks, and develop overall reliability, maintainability, and availability improvements. The Contractor shall update IRCMS as required.

3.3.1.1.10 Participate in evaluations of completed RCM analyses and products, as requested by the particular FST being supported, in order to update and support the RCM effort.

3.3.1.1.11 Provide design interface input into system design trade studies based on known functions, functional failures, and failure modes in the baseline comparison system (as defined by the GEIA-STD-0007).

3.3.1.1.12 Perform cost/benefit analyses on failure management strategy options and potential technology insertions and make recommendations to the FST and PMA regarding the solutions with the best effectivity and return on investment in IRCMS.

3.3.1.1.13 Collaborate with PMA and FST team members to aid implementation of PM activities and Other Actions (as defined in SOW paragraph 1.2), such as design change recommendations, development and revisions to training, technical publications, and other products impacted by RCM analyses.

3.3.1.1.14 Review and provide input into maintenance concepts, use studies, and other acquisition documentation to ensure RCM concepts are incorporated, as required.

3.3.1.1.15 Perform technical tests and analyses including analyses on integrating health management data and technologies into maintenance, modeling, and simulations to aid scheduled maintenance decision-making, and analyses in support of RCM improvement projects. (CDRL A004 Technical Report – Study/Services)

3.3.1.1.16 During the Technology Development and Engineering and Manufacturing Development phases, provide recommendations to NAVAIR Sustaining Maintenance Group RCM / CBM+ Leads and RCM / CBM+ Deputy Technical Warrant holders, for improvement of IRCMS and RCM processes when deficiencies and improvements are identified.

3.3.1.1.17 Support program-specific RCM, CBM+, and IMC/P training to the PMA/FST during the Technology Development and Engineering and Manufacturing Development phases. Develop and maintain new Program-specific RCM, CBM+ and IMC/P training, as required.

3.3.1.2 Procurement: Program analysis efforts using Procurement funds shall support RCM execution for low-rate production items, full-rate production items, and modifications to items such as weapon systems/aircraft/engines and their systems/subsystems/ SE for product improvement within the current performance envelope. The Contractor shall:

3.3.1.2.1 Provide the government technical input or recommendations to the germane RCM and CBM+ program plan based on changes such as PMA schedule and/or budget changes and lessons learned during Production and hardware-modifying engineering change proposals (ECPs) for review and approval by the Government. Provide technical input or recommendations to the existing germane program RCM ground rules and assumptions (GR&A) document as deficiencies are identified.

3.3.1.2.2 Initiate RCM analyses on procurement and modified systems in accordance with the germane RCM GR&A, and the NAVAIR 00-25-403 RCM Process and utilize RCM analyses to identify PM in support of fielding.

3.3.1.2.3 Evaluate existing or develop RCM analyses which includes data gathering and its analysis, updating SFMECA, and providing recommendations for PM tasks, including those for the use of health management capability and Other Actions. Provide the government results, findings, recommendations through documentation in the IRCMS.

3.3.1.2.4 Utilize and review Failure Mode Effects Analysis (FMEA)/FMECA provided by Government, OEM(s), and vendors in order to determine and rank failure modes that may benefit from periodic maintenance. This shall be based on the relevant program Hazard Risk Assessment Matrix as defined in the NAVAIR 00-25-403. Perform this task in preparation for fielding production and modified systems that have defined PM, age exploration, and Other Actions (including design change recommendations, training and technical publication modifications, and design change recommendations).

3.3.1.2.5 Update the PMA’s Hazard Risk Assessment Matrix to support decision-making for production systems and systems being modified. The Hazard Risk Assessment Matrix shall be utilized to categorize system failure risks and determine which failure modes require RCM analysis to mitigate safety, availability and environmental risks and minimize costs.

3.3.1.2.6 Incorporate new or modify existing IRCMS hardware trees or partitions (as defined in the NAVAIR 00-25-403) for purposes of performing RCM analysis for production systems and for systems being modified or retrofitted.

3.3.1.2.7 Utilize statistical analyses, including Weibull, Crow-AMSAA, reliability analyses, and root cause analyses related to failure modes for production systems and new failure modes for systems being modified or retrofitted in support of RCM and CBM+ analyses. (CDRL A004 Technical Report – Study/Services)

3.3.1.2.8 Collect, filter, analyze weapon systems/aircraft/engines and their systems/sub-systems/support equipment data using various systems owned by the Government, OEM or other vendor such as VECTOR, ADCS, JDRS, AFSAS, and MRO in support of RCM analyses for production systems and systems being modified or retrofitted. The data used will vary depending on the purpose of the analysis and may include predicted, test, and operational data.

3.3.1.2.9 In support of production systems and in-service hardware modifications, provide maintenance requirements, in approved contractor format per guidance from the FST Lead, for Organizational, Intermediate, and Depot level. This includes the review of RCM programs and products for production systems and systems being modified, provide evaluations and recommendations on analyses performed, ensure priorities are aligned with the RCM Ground Rules and Assumptions, provide support as requested by the particular FST being supported, and update documents and products.

3.3.1.2.10 Analyze cost/benefits on failure management strategy options and potential PM packaging options and provide recommendations to the Government for optimum availability, turnaround time, and minimized costs. (CDRL A004 Technical Report – Study/Services)

3.3.1.2.11 In support of production systems and in-service hardware modifications, provide recommendations for the development of maintenance support system requirements, including tooling, facilities, manpower and recommend improvements regarding process requirements.

3.3.1.2.12 Support PMA and FST team members in the implementation of PM activities and Other Actions, such as design change recommendations, training and technical publications development and revisions, in order to enable fielding of procurement and modified systems.

3.3.1.2.13 Review and provide input into programmatic documentation supporting procurement or modified systems to ensure RCM and CBM+ concepts are incorporated as required.

3.3.1.2.14 Perform technical analyses for production systems and in-service hardware modifications, including analyses on integrating health management data and technologies into maintenance, modeling and simulations to aid scheduled maintenance decision-making, high flight hour (HFH) impacts on RCM, system disposal planning impacts on RCM, and analyses in support of RCM improvement projects. (CDRL A004 Technical Report – Study/Services)

3.3.1.2.15 During the Production and Deployment phase, provide recommendations for improvement of IRCMS and RCM, CBM+, and IMC/P processes in regards to how they could better support the NAE.

3.3.1.3 O&M: Program analysis efforts using O&M funds shall support program planning and execution of RCM activities associated with weapon systems/aircraft/engines and their systems/sub-systems/SE that are fielded and capabilities that achieved initial operating capability. The Contractor shall:

3.3.1.3.1 Provide the government technical input or recommendations to the germane RCM and CBM+ program plan. Draft or provide technical input or recommendations to the existing germane program RCM ground rules and assumptions (GR&A) document as deficiencies are identified.

3.3.1.3.2 Update existing RCM analyses, to include data collection and analysis, input and maintenance of data in IRCMS, and provide recommendations for PM, including health monitoring capability and Other Actions.

3.3.1.3.3 Maintain and update the PMA’s Hazard Risk Assessment Matrix, in order to categorize system failure risks and determine which failure modes require RCM analysis to mitigate safety, availability and environmental risks and minimize costs.

3.3.1.3.4 Maintain and update existing hardware trees or partitions (as defined in the NAVAIR 00-25-403) for purposes of performing RCM analysis for in-service systems.

3.3.1.3.5 Track, monitor, and update failure modes in IRCMS by performing statistical analyses, including Weibull, Crow-AMSAA, reliability analyses, and root cause analyses. (CDRL A004 Technical Report – Study/Services)

3.3.1.3.6 Track, monitor, and update data collection, data filtering, and data analysis tasks using various systems that are owned by the Government, OEM or other vendor to include, but not limited to, VECTOR, ADCS, JDRS, AFSAS, and MRO. The data used will vary depending on the purpose of the analysis and may include predicted, test, and operational data.

3.3.1.3.7 Track, monitor, and update degraders and trends related to RCM metrics, as requested by the particular FST being supported, which will include performing Root Cause Analysis and developing corrective actions. This effort shall include review of emergent issues to ensure RCM analyses are up to date and complete. The Contractor shall update existing RCM analyses and perform RCM on new failure modes as required. The Contractor shall monitor degraders and trends related to RCM metrics as required. The Contractor shall identify and monitor high cost/readiness degraders for RCM candidates.

3.3.1.3.8 Track and update any existing Organizational, Intermediate and Depot Level PM tasks, sustain performance measuring and data collection of these tasks, processes, and logistics analyses, and develop overall reliability, maintainability, and availability improvements. The Contractor shall provide in-service engineering support in development and maintenance of MRC decks, Depot Specifications, Local Process Specifications (LPS), and Local Engineering Specifications (LES). This shall include day-to-day consulting, logistics forecast, and data queries from Naval aviation maintenance data systems, Naval Supply System Command (NAVSUP), Aircraft Inventory Readiness Reporting System (AIRRS), and other sources as required. The Contractor shall update IRCMS as required.

3.3.1.3.10 The Contractor shall participate in periodic reviews of the MRC, PMIC, PMI Field and Depot Specifications, and related technical publications for maintenance improvement opportunities, implementation of RCM results, task packaging efficiencies, and process improvement opportunities and ensure results of analyses are incorporated with the products.

3.3.1.3.11 Provide recommendations for the development and sustained optimization of maintenance support system requirements, including tooling, facilities, manpower, and process requirements.

3.3.1.3.12 Update cost/benefit analyses on failure management strategy options and potential technology insertions and make recommendations to the FST and PMA regarding the solutions with the best effectivity and return on investment. (CDRL A004 Technical Report – Study/Services)

3.3.1.3.13 Collaborate with PMA and FST team members to support implementation of PM activities including the use of health monitoring capability and Other Actions (see SOW paragraph 1.2), such as design change recommendations, training and technical publications revisions for in-service systems.

3.3.1.3.14 Provide recommendations for corrective actions based on failure data on fielded systems.

3.3.1.3.15 Develop and support briefs, lessons learned, and RCM and CBM+ -related programmatic documentation, as required.

3.3.1.3.16 Review and provide input into programmatic documentation to ensure RCM concepts are incorporated, as required.

3.3.1.3.17 Perform ongoing technical analyses including, analyses on integrating health management data and technologies into maintenance, modeling and simulations to aid scheduled maintenance decision-making, HFH impacts on RCM, system disposal planning impacts on RCM, and analyses in support of RCM improvement projects. (CDRL A004 Technical Report – Study/Services)

3.3.1.3.18 Provide recommendations for improvement of IRCMS and RCM process when deficiencies and improvements are identified.

3.3.1.3.19 Provide technical and programmatic support for the NAVAIR RCM and CBM+ Community of Practices. Efforts shall include, but are not limited to, providing input to NAVAIR RCM and CBM+ Policy and drafting procedure documents, supporting DoD and industry groups, updating knowledge management portal, and providing technical support for PMA and FST RCM analysis.

3.3.1.3.20 Support training at various NAVAIR sites, provide updates to the NAVAIR RCM, CBM+, and IMC/P courses, and develop and maintain new RCM, CBM+, and IMC/P training and tools for NAVAIR and/or the joint services, as required.

3.3.1.4 O&M Reserve: N/A

3.3.1.5 Working Capital Funding: Program analysis efforts using WCF funds, shall support program planning and execution of RCM activities associated with depot plant equipment. The contractor shall:

3.3.1.5.1 Provide the government technical input or recommendations to RCM plans associated with plant services. Draft or provide technical input or recommendations to the existing RCM GR&A document associated with plant services as deficiencies are identified.

3.3.1.5.2 Update existing RCM analyses, to include data collection and analysis, input and maintenance of data in IRCMS, and provide recommendations for PM tasks including health monitoring capability and Other Actions.

3.3.1…