N0042124R0042 (Draft).docx

N0042124R0042

Section B - Supplies or Services and Prices

Lot

Labor Ceiling for CLINs 0002-0008

CPFF

See Section C, Statement of Work 3.1 - 3.4 FOB: Destination

PSC CD: R425

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

NSP Labor - O&MN

Not Separately Priced Labor in support of CLIN 0001

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

NSP Labor - APN

Not Separately Priced Labor in support of CLIN 0001

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

NSP Labor - RDT&E

Not Separately Priced Labor in support of CLIN 0001

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

NSP Labor - WCF

Not Separately Priced Labor in support of CLIN 0001

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

NSP Labor - FMS

Not Separately Priced Labor in support of CLIN 0001

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

NSP Labor - FCP

Not Separately Priced Labor in support of CLIN 0001

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

NSP Labor - FDC

Not Separately Priced Labor in support of CLIN 0001

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

ODC Ceiling for CLINs 0010-0016

COST

Travel and Material Ceiling for CLINS 0010-0016. Travel and Material in accordance with Section C, Statement of Work 3.1.5.1 and 3.1.5.2.

ESTIMATED COST

Lot

NSP - ODC O&MN

Not Separately Priced ODC in Support of CLIN 0009

ESTIMATED COST

Lot

NSP - ODC APN

Not Separately Priced ODC in Support of CLIN 0009

ESTIMATED COST

Lot

NSP - ODC RDT&E

Not Separately Priced ODC in Support of CLIN 0009

ESTIMATED COST

Lot

NSP - ODC WCF

Not Separately Priced ODC in Support of CLIN 0009

ESTIMATED COST

Lot

NSP - ODC FMS

Not Separately Priced ODC in Support of CLIN 0009

ESTIMATED COST

Lot

NSP - ODC FCP

Not Separately Priced ODC in Support of CLIN 0009

ESTIMATED COST

Lot

NSP - ODC FDC

Not Separately Priced ODC in Support of CLIN 0009

ESTIMATED COST

CLAUSES INCORPORATED BY FULL TEXT

BTXT.211-9503 LEVEL OF EFFORT (COST REIMBURSEMENT) (NAVAIR) (DEC 2012)

(a) The level of effort estimated to be ordered during the term of this contract is 441,600 man-hours of direct labor including authorized subcontract labor, if any. The contractor shall not, under any circumstances, exceed one hundred (100%) percent of the total level of effort specified in this basic contract. The estimated composition of the total man-hours of direct labor by classification is as follows:

5 Year Ordering Period

Section C - Descriptions and Specifications

STATEMENT OF WORK

Statement of Work for NAVAIR Air Vehicle Department Support

1.0 Scope.

This SOW defines the effort to be performed for the Structures Division of the Air Vehicle Department, AB2200 (formerly AIR 4.3.3), Naval Air Warfare Center, Aircraft Division (NAWCAD) in support of aircraft structural life monitoring and air vehicle airworthiness certification. Tasks fall into three technical areas: Structural Appraisal of Fatigue Effects (SAFE) Program, Strength Engineering, and Loads and Dynamics Engineering support.

The SAFE program monitors individual aircraft usage in order to quantify aircraft structural fatigue damage. It is necessary to accurately determine the fatigue life of each aircraft to ensure safety. An economic benefit may also be gained by operating aircraft for the maximum service period possible. During long-term service usage of aircraft, it is necessary to compare a given aircraft’s actual service loads history to the spectra for which it was designed. This is done in order to establish safe service lives for the aircraft in the SAFE Program. By coupling usage data with fatigue life prediction methodology and comparing it with the aircraft’s life expectancy, SAFE engineers can determine the Fatigue Life Expended (FLE). SAFE is carried out on a continuing basis, with the issuance of quarterly reports and other aircraft service life information as needed. Present naval aviation structural integrity management is based on a safe-life approach correlated with results from a full scale fatigue test. Aircraft are tracked with respect to the accumulation of the damage index. Flight data from a flight loads data recorder (FLDR) are used to determine the flight stress and strain histories at the hot spots. In turn, flight-by-flight stress and strain histories are used to calculate the incremental damage accumulated per each flight. In the past, when the accumulated damage of an aircraft equaled the same damage experienced at half the FSFT life, FLE equaling of 100%, it was removed from the inventory. Fatigue life status is published to fleet users and planners quarterly through a NAVAIR website.

The Strength Engineering branches are responsible activities related to structural design, stress analysis and fatigue for fixed and rotary wing aircraft. Branch responsibilities include controlling and directing structural tests, including: static, dynamic, fatigue and fracture tests; field and shipboard takeoff and landing tests; water landing, ground maneuver and tie-down tests. Responsibilities begin in the basic research and development stages and continue through acquisition and in-service fleet support until aircraft are retired from active service. Engineering activities include: providing the basis for design, testing validation and life certification including the processes to measure, assess, track and extend airframe/component life; defining safe operating envelopes for all United States Navy (USN) and USMC fixed and rotary wing aircraft vehicles; evaluating structural integrity of external stores and weapons during captive carriage and initial release/flight within the proximity of the air vehicle; developing structural design criteria; evaluating flight clearance requirements, reviewing flight test results and providing recommendations; developing structural inspection criteria and one time repair instructions.

The Loads and Dynamics branch is responsible for engineering activities related to flight and ground loads analysis, flutter, vibration, sonic fatigue, static aero-elastic, aero-servo-elastic and dynamic response characteristics for fixed and rotary wing aircraft. The branch controls and directs wind tunnel and ground testing for dynamics and loads; field and shipboard takeoff and landing, water landing, ground maneuvering and tie-down testing. These responsibilities begin at the basic research and development stages and continue through acquisition and in-service fleet support, until retirement from active service. Engineering activities include: providing basis for design, test validation and life certification; specifying the basis for static and dynamic loads, flutter, repeated loads and launch and recovery loads; defining safe operating envelopes for all USN and USMC fixed and rotary wing air vehicles; evaluating dynamic response of external stores and weapons during captive carriage and initial release/flight within the proximity of the air vehicle; developing design criteria; defining and directing flight and ground loads testing; establishing flight clearance requirements, reviewing test analyses and providing recommendations.

2.0 Applicable documents.

2.1 Department of Defense (DoD) Specifications

2.1.1 DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 July 28, 2020.

2.1.2 DoD 5400.7-R, Freedom of Information Act (FOIA) Program 05 Apr 2019

2.1.3 DoDI 5230.24 Distribution Statements on Technical Documents, Change 2, Effective 10 Jan 2023

2.1.4 SECNAV M-5510.30 Personnel Security Program April3, 2017

2.2 Reserved

2.3 Other Government documents (e.g. NAVAIR Documents)

2.3.2 Section 508 Amendment to the Rehabilitation Act of 1973.

2.3.3 Department of Defense Web Policies and Guidelines.

2.3.4 DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B.

2.3.5 Defense Information Systems Agency (DISA) Hosting of All Navy Websites (NAVADMIN 061/08).

2.3.6 Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07.

2.3.7 DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified Web Sites and Uniform Resource Locators.

2.3.8 Policy and Procedures for Web Risk Assessment (WRA) of Publicly Accessible Navy Sites (ALCOM 129/09).

2.3.9 DoDI 8500.01 Cybersecurity, 07 Oct 2019

2.3.10 DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 28 Jul 2017

2.3.11 Committee on National Security Systems Instruction 1253, “Security Categorization and Control Selection for National Security Systems 27 March 2014

2.3.12 DoDI 8582.01, ASD (NII) Directive-Type Memorandum (DTM) 08-027 – Security of Unclassified DoD Information on Non-DoD Information Systems, 06 June 2012.

2.3.13 Chairman of the Joint Chiefs of Staff Instruction CJCSI 3170.01I (series), Joint Capabilities Integration and Development System,. 23 January 2015 c. CJCSI 6211.02D, Defense Information System Network (DISN): Policy and Responsibilities, 23 January 2015.

2.3.14 http://www.jcs.mil/Portals/36/Documents/Library/Instructions/3170_01a.pdf?ver=2016-02-05-175022-720

2.3.15 CJCSI 6510.01F, Information Assurance (IA) and Support to Computer Network Defense (CND), 09 Feb 2011, certified current. 9 June 2015

2.3.16 Chairman of the Joint Chiefs of Staff Manual CJCSM 6510.01B – Cyber Incident Handling Program, 10 July 2012.

2.3.17 Navy Ports Protocols, and Services (NPPS) Manual, Version 1.5, 27 July 2017.

2.3.18 Defense Acquisition Guidebook – Chapter 6, Acquiring Information Technology, Including National Security Systems, Section 7.5, Information Assurance (IA).

2.3.19 DoD 8570.01-M, Information Assurance Workforce Improvement Program, 19 Dec 2005, (Incorporating Change 4, 10 November 2015).

2.3.20 DoDD 8000.01, Management of the Department of Defense Information Enterprise, 10 February 2009.

2.3.21 DoDD 8100.02, Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current, 23 April 2007.

2.3.22 DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 01 April 2004.

2.3.23 DoDI 8581.01, Information Assurance (IA) Policy for Space Systems Used by the Department of Defense, 2 July 2017

2.3.24 DON CIO Memo 02-10, Department of the Navy Chief Information Officer Memorandum 02-10 Information Assurance Policy Update for Platform Information Technology, 26 April 2010.

2.3.25 Federal Information Processing Standards Publications (FIPS PUB)-199, February 2004

2.3.26 National Security Telecommunications and Information Systems Security Policy NSTISSP Source: IRM Office UPDATED: August 2015 Page 12.No. 11, Revised Fact Sheet National Information Assurance Acquisition Policy, July 2003.

2.3.27 Office of the Chief of Naval Operations OPNAVINST 5239.1C, Navy Information Assurance (IA) Program, 20 Aug 08.

2.3.28 SECNAVINST 5230.15, Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software, 10 April 2009.

2.3.29 SECNAVINST 5239.3B, Department of the Navy Information Assurance Policy, 17 June 2009.

2.3.30 SECNAVINST 5239.19, Department of the Navy Computer Network Incident Response and Reporting Requirements, 18 March 2008.

2.3.31 The National Security Act of 1947.

2.3.32 Title 40/Clinger-Cohen Act.

2.3.33 Title 44/ Federal Information Security Management Act.

2.3.34 National Institute of Standards and Technology Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organizations, Revision 4, April 2013.

2.4 Industry Documents – Reserved

2.5 Information Assurance Technical Privileged Access

2.5.2 DoDD 8500.01E, "Information Assurance (IA)," of 24 Oct 2002 (update 23 Apr 2007)

2.5.3 DoDI 8500.2, "IA Implementation," of 6 Feb 2003

2.5.4 Navy Telecommunications Directive (NTD) 11-08, “Electronic Spillage Requirements,” of Nov 2008

2.5.5 DoD 5200.2-R, "Personnel Security Program," of 16 Jan 1987 (update3 April 2017)

2.5.6 Committee on National Security Systems (CNSS) Instruction 4013, "National Information Assurance Training Standard for System Administrators," of Mar 2004.

3.0 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 Controlled Unclassified. The current operating environment required for this contract includes:

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

Ability to operate in eDMZ, adherence to ATO

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall maintain state-of the-art virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with AB2200 (formerly AIR 4.3.3). Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with Air 4.3.3 during working hours whether at Contractor work site or on travel.

The Government shall provide all NMCI services; to include IT related hardware, software, and support, necessary for the performance of this contract/order. Coordination of these services is to be conducted through the COR. Disposition or transfer instructions of previously acquired NMCI assets will be provided by the COR as appropriate. NMCI assets for the performance of this contract are considered GFP and shall be documented and maintained as GFP per FAR 52.245-1 (Attachment 7)."

All Government Furnished Property (GFP) or derived information is the property of the U.S Government and shall remain in contractor spaces. The contractor will not transfer any property or derived information to any individual or agency, public or private, without the express written approval of the Procuring Contracting Officer (PCO), except as required for the specific performance of tasks under this contract.

3.1.2. Work Location and Facilities.

3.1.2.1 Work Location. 100% of work to be performed will be at the Contractor site. The Contractor shall perform services at contractor facilities located within 50 driving miles of the Naval Air Station, Patuxent River, MD.

3.1.2.2 Meeting Support.

3.1.2.3 Telework. The contractor may allow employees to telework with approval from the Contracting Officer’s Representative (COR) in writing, that a position’s tasking is eligible for telework. The contractor may utilize alternate worksites/locations and telework to support continued performance of the SOW in accordance with (IAW) company policy. When using telework, 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 Progress and Financial Status Report. The contractor shall provide a progress and financial status report in accordance with the Contract Data Requirement List (CDRL A002). The report shall include work accomplished since submittal of the last report, both monthly and cumulative man-hour labor costs expended by labor category and material and travel costs.

3.1.4 Work Schedule - 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. Normal working hours are usually eight and a half (8.5) hours (including a 30-minute lunch break), from 0730 to 1600 each Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800 Monday– Friday. Core hours are 0900 to 1500 Monday through Friday, and weekend work may be required.

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 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other. The Contractor, with agreement by the COR/ACOR, may allow its employees to work a CWS schedule. 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 when required by the Government. If agreement to implement the CWS schedule is reached with the COR, the overall schedule must be provided and approved. Key contractor personnel, at the discretion of the COR, may not be allowed to work a CWS schedule even if the remaining employees are permitted to do so.

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.

3.1.4.1.3 Installation closure.

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 performing non mission essential work 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 supervision 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 cannot be charged directly to the contract unless first approved in writing by the Chief of the Contracting Office (CCO).

3.15 Other Direct Costs (ODCs).

The Contracting Officer’s Representative (COR) or Alternate COR (ACOR) and Contracting Officer approval shall be obtained prior to the purchase of any material or travel expenses in accordance with NAVAIR Clause 5252.242-9515 Restrictions on the Direct Charging of Material or travel expenses in accordance with NAVAIR Clause 5252.232.9509 Travel Approval and Reimbursement Procedures.

3.1.5.1 Travel.

Travel will be allowable only when it is essential to the performance of the tasks detailed in Section 3.3. Reimbursement for travel performed shall be in accordance with the Department of Defense Joint Travel Regulation (http://www.defensetravel.dod.mil/site/travelreg.cfm). The COR shall concur and approve all travel performed in support of this contract prior to the commencement of the travel. COR approval for local travel expenses is required. Travel may include general and administrative expenses, but shall not include fee/profit. Temporary travel to other locations in support of program tasking is required. If required, temporary travel locations include, but are not limited to: Atlanta, GA; Cherry Point, NC; El Segundo, CA; Fort Worth, TX; Jacksonville, FL; Philadelphia, PA; St. Louis, MO; San Diego, CA; Seattle, WA; St. Augustine, FL; Stratford, CT; West Palm Beach, FL; and Whidbey Island, WA. This list is not all inclusive as locations may change over the life of the contract. Travel authorization request shall be prepared and submitted no less than 30 business days prior to travel for COR approval.

The Contractor shall travel, as required, during the performance of this contract to Navy, Contractor or DoD facilities, and other government agency offices (i.e., for meetings, conferences, seminars, and training classes). The Government shall reimburse the Contractor for allowable travel costs, exclusive of fee, incurred by the Contractor in performance of the contract in accordance with the Department of Defense Joint Travel Regulations and clause CTXT.232-9509, “TRAVEL APPROVAL AND REIMBURSEMENT PROCEDURES.”

3.1.5.2 Material. Prior written approval of the COR shall be required for all purchases of materials over $3,500. If the contractor’s proposal includes a list of materials with associated prices, then the (COR’s/ACO/PCO as applicable) acceptance of the contractor’s proposal shall constitute written approval of those purchases. Any material provided by the contractor is subject to the requirements of the Federal Acquisition Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable Department of the Navy regulations and instructions. All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Other Direct Charges may include general and administrative expenses but shall not include fee/profit. NAVAIR clause 5252.242-9515 Restriction on Direct Charging of Material (NAVAIR)(July 1998) is applicable.

The costs of general purpose business expenses required for the conduct of the contractor’s normal business operations are not an allowable direct cost in the performance of this contract. General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies. The contractor shall track, manage, and otherwise account for purchases made under this contract.

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 Transition Out Strategy.

The contractor’s overall strategy shall be built around maintaining the mission of the Structures Division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of this contract, the contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The contractor shall submit a Transition Out Plan, to include the minimum elements listed below in accordance with (CDRL A011).

•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 incoming contractor or 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 Data Handling

In the performance of the contract, the Contractor may have access to non-public proprietary information. The contractor shall require that any employee performing services under the contract execute a Non-Disclosure Agreement (NDA) satisfactory to the Contracting Officer. The NDA shall acknowledge the Contractor and employee’s duties with respect to non-public information and promise to comply with those obligations. A copy of the executed NDAs shall be provided to the Government. Further, the Contractor shall, within 15 days after the effective date of this contract, obtain and provide to the COR signed NDAs with each subcontractor and consultant (CDRL A007); and shall obtain and provide to the COR signed individual NDAs with all Contractor, subcontractor and consulting personnel that performs work under this contract (CDRL A008).

In addition to complying with the terms and conditions of NAVAIR 5252.209-9510(e)(5) with respect to proprietary data of third parties and DFARS 252.227-7025 with respect to technical data, the Contractor shall not use, modify, reproduce, release, perform, display, or disclose any non-public information provided to or obtained by the Contractor in the course of performing the contract only for Government purposes and shall not do so for any commercial or personal purpose. IMPORTANT: Executing the NDAs attached to this contract does not alleviate the contractual duties and obligations the contractor has, pursuant to NAVAIR Clause 5252.209-9510(e)(5), including, but not limited to, agreeing to execute agreements with companies furnishing proprietary data in connection with work performed under this contract. In the event that the Contractor knows of or identifies that it has a commercial interest in the subject matter of any proposed or on-going agreement with respect to which contracts services are to be performed; the Contractor shall consider such interest a potential conflict of interest under NAVAIR 5252.209-9510(g) and promptly disclose it to the Contracting Officer.

3.1.10 Quality Standards

Standards for quality and data deliverables are contained in the Contract Surveillance Plan (CSP), Attachment (1). The CSP establishes the methods by which the COR will observe, evaluate, and document Contractor performance in meeting critical quality standards identified in the contract. In accordance with the CSP the contractor, not the Government, is responsible for the management and quality control actions necessary to meet the quality standards set forth by the Task Orders.

3.1.11 Information Technology (IT) Information

The Government will provide all necessary obsolete reference documents and those not generally available to the contractor as requested. The Contractor shall not purchase any IT equipment on behalf of NAVAIR in support of this Contract.

3.1.11.1 System Software/Application Compliance

3.1.11.2 Web Sites, Web Enablement and Application / System Development, Modification, and Maintenance Support Services.

All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and strategies, and should be integrated within the NAVAIR Enterprise portal and collaboration environment. Policies include, but are not limited to references 2.3.1 through 2.3.7.

3.1.11.3 Software Development/Server Procurement

Any tools developed that will be hosted by the NMCI or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.

3.1.11.4 Cybersecurity

As a minimum, software, documentation (data deliverables) and/or IT services delivered by this contract shall be in compliance with the references 2.3.8 through 2.3.10 and 2.3.17. Information technology services shall only be performed by personnel who are qualified and certified in accordance with reference 2.3.17. Personnel proposed and/or used in the performance of this contract as certified personnel shall be limited to those whose specifically assigned duties and responsibilities require certification. All Cybersecurity shall be in compliance with the following listed instructions in references 2.3.11 through 2.3.32. All IT procured on behalf of this contract shall meet all DoD/DON and NAVAIR cybersecurity polices. Failure to follow these policies will result in denied access to NMCI, One Net, Integrated Shipboard Network System (ISNS) and other DON, DoD and Joint Networks. These cybersecurity policies are standard across the Department and ensure cybersecurity compatibility and interoperability. The following specific criteria must be met before the contractor can be connected to any DoD or NAVAIR network in support of this contract. Requirements include:

a. Network Vulnerability Scanning. NAVAIR Deputy CIO for Information Assurance maintains authorized auditing tools and shall provide for firewall/port scans, device discovery scan, vulnerability assessment, and other requirements as required to ensure secure interoperability with DoD networks. The contractor shall be responsible for the remediation of any equipment that fails these audits prior to the connection of the system to the networks. Results of approvals shall be documented via Memorandum of Agreement with the Facility Security officer and the Defense Security Service Representative for that contractor.

b. Extent of Validation Scanning. To prevent scanning of corporate assets, all such networks, equipment and connections shall be physically segregated from any Government/contractor corporate networks that are not in direct support of DoD contracts.

c. Circuit Provisioning. Any circuit or connection between NAVAIR and/or DoD site and the contractor site shall be provisioned via the Defense Information Security Agency and comply with CJCSI 6211.02D, Defense Information System Network (DISN): Policy and Responsibilities, 24 Jan 2012.

d. Servicing Systems from a Remote Contractor Site. Remote Access Service connections that allow off-station operation and/or administration of contractor owned systems, located at any NAVAIR facility or site, shall not be permitted, with the exception of those systems connecting to the Command via the Outreach Services identified in Section 6, Enterprise Architecture.

e. Memorandum of Agreement and Inter-Connection Agreements. A Cybersecurity Memorandum of Agreement (MOA) between the contractor owning the equipment and AIR-7.2.6 shall be developed and signed before the equipment can be connected to NAVAIR networks. Failure to comply with the signed MOA shall be grounds for disconnection from the network.

3.1.11.5 Enterprise Architecture

a. Contractor Networks and Connections. Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non- Government, external IP space via the NAVAIR-provided Virtual Private Network (VPN) Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

b. Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the NAVAIR Enterprise Architect (AIR-7.2.3) prior to build out.

c. Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.

3.1.12 Deliverables

The following provides a summary of each CDRL:

3.1.13 Availability of Government Documents.

The AIR-4.3.3 Division will assist the contractor in obtaining Government documentation not generally available to the Contractor to perform tasks specified in this SOW. Any instruction or document replaced or superseded throughout the life of the contract shall become applicable to the requirements defined in this SOW.

3.1.13.1 Availability of Non-Government Standards and Other Publications.

The Contractor shall obtain source documentation from original equipment manufacturers as required to perform the tasks specified in this SOW.

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:

SECURITY: All Contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAV M-5510.30C. All Contractor personnel 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 Questionnaire for Investigations Processing (eQIP)), shall do a preliminary screening of the Contractor's eQIP 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 from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor's eQIP. 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-N: All Contractor personnel requiring access to Government IT systems shall have an approved DOD System Authorization Access Request (SAAR-N) or DD Form 2875 on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. Instructions for processing the SAAR forms are available at: https://disa.mil/en/NewsandEvents/2023/UpdatedDDForm2875.

SAAR forms shall be submitted to the COR, Government Technical Point of Contact (TPOC), or to the assigned DoD Mission Partner - Identity, Credentialing, Access Management (MP ICAM) Associate.

3.2.3.2 CAC/Local Badges: The Contractor shall coordinate and ensure the provision of security badges required to allow Contractor personnel access to designated workspaces; the Contractor shall comply with all applicable security requirements, abide by direction given by Military Police or other security personnel, and adhere to installation traffic laws. Performance of work under this contract will require access to sensitive information or systems.

Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and 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 in DoDM 1000.13. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site in accordance with NASPAXRIV Instruction 5510.15, Regulations Governing Admission to Naval Air Station, Patuxent River, Webster Field, and Navy Recreation Center Solomon’s, following completion of the contract, relocation or termination of an employee, or upon request from the COR. The

Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract.

3.2.4 Information Security. The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with the National Industrial Security Program Operating Manual (NISPOM) codifying 32 Code of Federal Regulation Part 117, NISPOM Rule, and SECNAV M-5510.36B. All Contractor facilities shall provide an appropriate means of storage for controlled unclassified information and materials. All controlled unclassified information shall be appropriately identified and marked in accordance with DoD Instruction 5200.48, Controlled Unclassified Information (CUI).

3.2.4.1 Marking: Controlled Unclassified Information including Legacy FOUO and Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) 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. Any product containing Covered Defense Information 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, Enclosure 3.

All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement(s):

Distribution Statement (Insert Appropriate Letter and Authorization Title), (Insert Appropriate Reason Category) (dated – (Date of Distribution Authorization). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: (Program/User Agency mailing address).

3.2.4.2 Public Release: Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or X, unless it has been approved for public release by appropriate U.S. government authority. Proposed public releases shall be submitted for approval prior to release through: Public Affairs Office, 47123 Buse Road, RADM William A. Moffett Building, Patuxent River, MD 20670-1547.

3.2.4.3 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 24 hours of the incident occurring.

3.2.5 Operations Security (OPSEC): The Contractor shall develop, implement, and 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:

a. Assignment of responsibility for OPSEC direction and implementation.

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

c. Establishment of OPSEC education and awareness training.

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

e. 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 RO and contractor in support of the mission.

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.3 Detailed Support.

3.3.1 SAFE Program Support. The Contractor shall provide SAFE processing required to produce, revise, update, and distribute SAFE Reports for defined Type/Model/Series aircraft. The contractor shall:

3.3.1.1 CLIN 0004 (RDT&E) Develop and certify advanced crack initiation and crack growth methodologies based on physics-based material fracture mechanics. Evaluate current SAFE crack initiation and crack growth methodologies and recommend any changes or corrections needed for the SAFE fatigue tracking program. Compare predicted fatigue and crack growth behavior with test findings and aircraft teardown findings. Document and deliver fatigue life tracking methodology (including logical algorithms), validation and verification test results, and recommendations in Aircraft Fatigue Life Methodology Report CDRL. Deliver software source code and executable programs developed in Individual Aircraft Tracking Software CDRL. Deliver software user’s manual for the Individual Aircraft Tracking Software CDRL. (CDRLs A001, A009, and A010).

3.3.1.2 CLIN 0004 (RDT&E) Develop prognostic health monitoring (PHM) solutions to integrate on-board aircraft usage data, maintenance records, and pilot reported data to predict and mitigate fatigue failures. Investigate proposed PHM implementation into flight loads data recorders and other related support equipment to identify potential problems and areas for improvement in the fatigue life tracking program. Document and deliver methodology (including logical algorithms), evaluation and test results, and recommendations in Application of Prognostic Health Monitoring System to Aircraft technical report. Deliver software source code and executable tools produced and utilized in completing the analysis in SAFE Analysis Tools. Deliver a software user’s manual for the SAFE Analysis Tools. (CDRLs A001, A006, and A009).

3.3.1.3 CLIN 0003, 0008 (Procurement, Foreign Cooperative Projects(FCP)) Review and analyze fatigue life changes due to aircraft modifications including engineering change proposals, airframe changes, mission system equipment upgrades or new external weapons/pods configurations. Document and deliver analysis methodology (including logical algorithms), analysis results, and recommendations in Aircraft Modifications Impact on Fatigue Life technical report. Deliver software source code and executable tools produced and utilized in completing the analysis in SAFE Analysis Tools. Deliver a software user’s manual for the SAFE Analysis Tools. Assess Individual Aircraft Tracking (IAT) software program and incorporate changes that impact Fatigue Life Expended (FLE) calculations. Deliver software source code and executable IAT program. Deliver IAT software user’s manual. (CDRLs A001, A006, A009, and A010).

3.3.1.4 0003, 0008 (Procurement, FCP) Review and analyze changes in measured aircraft parametric data caused by incorporation of new flight data recorder, mission computer, or airborne sensors for use in determining basic aircraft FLE values. Generate appropriate changes to external loads, internal loads, and stress calculations. Conduct technical studies of flight loads data recorder structural data and other related data to identify potential problems and areas for improvement in the fatigue life tracking methods. Document and deliver analysis methodology (including logical algorithms), analysis results, and recommendations in Flight Data Updates Impact on Fatigue Analysis for Aircraft technical report. Deliver software source code and executable tools produced and utilized in completing the analysis in SAFE Analysis Tools. Deliver a software user’s manual for the SAFE Analysis Tools. Assess Individual Aircraft Tracking (IAT) software program and incorporate changes that impact Fatigue Life Expended (FLE) calculations. Deliver software source code and executable IAT program. Deliver IAT software user’s manual. (CDRLs A001, A006, A009, and A010).

3.3.1.5 0003, 0008 (Procurement, FCP) Analyze structural life management methods provided by Original Equipment Manufacturers (OEMs) as part of new aircraft…