SOW_ T.O#7_ 05.07.2025_CC.docx

NSWCPD SOW-PWS Template Rev 44

CHANGE RECORD AS OF JAN 2019

2) Enclosure 1 minor grammatical and punctuation changes were implemented

3) New Section added: 5.1 U-NNPI SECURITY REQUIREMENTS

4) Under Section 12.1 Personnel: A Note for Government was added “If there will be Personnel under the same category that will not be in CSWF; then designate a separate labor category ...” and additional contractor instructions were added related to DFARS clause 252.239-7001.

2) Removed eCMRA and eCRAFT language covered in HQ clauses: C-237-H001 and C-237-W001

2) Updated a reference to reserved NSWCPD clause from 5252.237-9106 (A) Substitution of Personnel to C-237-H002 SUBSTITUTION OF KEY PERSONNEL

3) Added Section 6.1.5 to include the NSWCPD Environmental Management System (EMS) Awareness Training requirement

2) Under Section 9.0, a statement was added to indicate that the use of GFI by the contractor is optional 3)Under Section 10. Purchases, a note was added to specify that the $10,000 amount in the fill-in is editable 4)12.1.2 Non-Key Personnel was revised to remove pre-award responsibilities that should be contained in Sections L/M, and to add an instruction to the document preparer

5) The term “Offeror” was changed to “contractor” in any occurrences

6) Under Section 14.1, the HQ clause number HQ E-2-0015 was updated to E-246-H020 (Quality Management System)

7) Added and instruction under 3.0 Requirements ensure that tasks are clearly defined and tied to CLINS

8) Added Section: 14.2 Risk Management

2) A note was added to Section 10. PURCHASES to state that consideration shall also be given to whether the contractor has an approved purchasing system.

3) The discussion of Key Personnel was moved/renumbered to Section 12.2 4) Section 12.3 DON Cyberspace IT (Information Technology) / Cybersecurity & Information Assurance Functions and Personnel Requirements and Appendix A have undergone extensive revisions 5) Section 13.0 was updated to include a reference to Clause C-237-W001 “Electronic Cost Reporting and Financial Tracking (eCRAFT) System Reporting (NAVSEA)”

6) Section 4: Data Requirements was updated to include a reference to the CDRL for sustainment contracts: Government Furnished Material (GFM) by National Stock Number and the Small Business Utilization Report CDRL 7) Revised Section 4.4 to indicate that the ODC CDRL instructions 8) A table was added to Section 7.0 travel to mirror the table that appears in the IGCE

9) Various formatting and paragraph numbering edits were implemented

requirements of NMCARS Subpart 5204.73 and Annex 16

2) Combatting Human Trafficking and Constitution Day removed from Section 5.1 as required contractor training.

3) Cybersecurity 101 added to Section 5.1 as required contractor training.

4) Industrial Security Clearance Office (DISCO) has been updated to Defense Counterintelligence and Security Agency (DCSA) in section 5.2

5) Clarification in section 10.1 that “Purchases of an individual item that is valued above $10,000 shall be approved by the Contracting Officer prior to purchase by the Contractor.”

6) Clarification in Section 12.1 that “All persons proposed in key and non-key labor categories shall, at the time of proposal submission, be U.S. citizens holding at least a current SECRET clearance, or possess a favorable DCSA adjudication as outlined in section 5.3.”

7) Added language in Section 12.4 to state “The Contractor shall indicate within the personnel section of it’s proposal, and/or indicate within individual submitted resume(s), any personnel security clearance requirements as stipulated in section 12.1 above.”

Removed requirement for to approve PCO from Section 7.0

2) Inserted Section 5.4 to clarify that contractor employees who hold a dual citizenship will not be granted access to NSWCPD facilities Added an NDA requirement for contractor exposure to PPBE data in new section 5.11

2) Section 11.0 Counterfeit Material Prevention has been re-worded

3) The requirement to include OPSEC requirements for work in support of NSWCPD that do not utilize a DD 254 is added to Section 5.11

4) The Security requirements under Section 5.2 have been completely revised to include that interim Security Clearances are acceptable for this issuance of a CaC.

Administrative revision: excessive sample text was removed from Sections 1.2 and 3.0

7/21/20

1) The hyperlink to the Counterfeit Materiel Process Guidebook, in Section 11.0 was updated

2) Section 7.2 was updated to clarify the acceptable forms of travel approval

3) 1.0.3 Government/Contractor Relationship, a minor edit was made in the section heading IAWF/ CSWF requirements have been updated under Section 12.6 and Appendix A

Additional instructions were added to Section 5.7 DD254 REQUIREMENT

2) Section 12.5 was revised to specify that the word “shall” vs “should” is appropriate to use with minimum experience requirements

3) A requirement for C/105 OPSEC Security PM review for requirements with no DD 254 was added to Section 5.11 Section 5.8 Security has been revised to add include Facility Security Clearance (FCL) language

4) Section 5.14, Compliance to NIST 800-171, has been removed as these requirements are now contained in HQ clause C-204-H002 Implementation Of Enhanced Security Controls On Select Defense Industrial Base Partner Networks (NAVSEA) (JAN 2020)

2) Section 5.4 Operations Security (OPSEC) was revised to indicate that this section is required to be included in all SOWs

3) Sample COVID language was added under Sections 5.2.4 (On Site Work), 6.1.5 (Place of Performance), and 14.4 Numbering formats and margin settings were standardized in various sections

2) A reference to the Software Development Plan CDRL was added under 4.10 (Data Requirements)

3) Under Section 5.2 (On Site Work), obsolete references to Facility Access Determination (FAD)

4) Under 5.4.1 (OPSEC) a reference to a CIIL (Critical Indicators and information list) was added

5) Language was consolidated under Section 5.1 and the subparagraphs were re-numbered

6) Section 14.4 was added as a place holder for discussion of Software Development Plans

7) Section 5.5 Receipt, Storage, and Generation Of Controlled Unclassified Information (CUI) was updated with revised language from the Security office

2) A statement regarding the planned utilization of non-U.S. Citizens (former section 5.3.6) was removed and section 12.1 was revised The instructions under 5.3 DD254 REQUIREMENT were revised

Former Section 5.7.1 System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews has been removed and the section was renumbered. NIST SP 800-171 now governs the System Security Plan (SSP) process

2) Duplicate section 5.1.2 related to contractor badges has been deleted and consolidated under Section 5.2 and the following sections were renumbered Minor administrative changes were made under section 5.8.1.2

Unnecessary sample text was removed under Section 14

2) Section 4.0 DATA REQUIREMENTS has been revised to differentiate the requirement for submission of the periodic and the final Government Property Inventory Report and to add references to the Level 1 Material CDRLS

3) Section 4.0 DATA REQUIREMENTS has been revised to clarify the Trip Report instructions Section 4.0 DATA REQUIREMENTS has been revised to include references to the CDRLS that would be required when Level I Material requirements are present

2) OPSEC instructions were updated within Section 5.4 and updated to state that questions surrounding OPSEC requirements “shall be directed to the PCO”, and references to NISPOM were corrected to DoDM 5220.22

2) Section 3.2.2. which contained a retired group email box for the Commonality program was removed

2) An edit was made to update the NISPOM reference from DoD5220.22-M, to 32 CFR Part 117

2) A reference to the Condition Found Report (CFR) (Command) CDRL was added to Section 4.0 Data Requirements

1) Section 7.5 OCONUS Contractor Personnel Travel During COVID-19 was reserved

2) Section 14.5, NSWCPD Occupational Safety and Health (OSH) /NAVSEA Standard Items 009-01 and 009-112, was added for use in all radiological contracts

2) Updated 5.4 OPSEC to remind PCO’s of req’t to send RFP’s to our OPSEC Security PM Ernest Fentress and Special Security Officer, Stacie Ann Addley for OPSEC and SAIRC review before solicitation release via AMS/PMT. PCO’s reminded that they can still send documents that will be released to non-Government entitles prior to solicitation release (draft SOW/PWS, Sources Sought notices, Synopsis postings, RFIs) via email to Stug our OPSEC Security PM if there are concerns with the sensitivity of info. included.

Statement of Work (SOW) Code 424 Surface Combatant/Gas Turbine Engineering

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Code 424, which is responsible for Surface Combatant/Gas Turbine Engineering.

1.0.2 This contract is for non-personal services. It does not create employment rights with the U.S. Government whether actual, inherent, or implied

1.0.3 Government/Contractor Relationship

1.0.3.1 The services to be delivered under this Task Order are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Task Order between the Government and the Contractor's personnel. Therefore, it is in the best interest of the Government to provide both parties a full understanding of their respective obligations.

1.0.3.2 The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishable badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

1.0.3.3 Contractor personnel under this Task Order shall not engage in any of the inherently Governmental functions listed at FAR Subpart 7.5 or DFARS Subpart 207.5.

1.0.4 Employee Relationship:

1.0.4.1 The services to be performed under this Task Order do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

1.0.4.2 Rules, regulations, directives, and requirements that are issued by the U. S. Navy and NSWCPD under its responsibility for good order, administration, and security are applicable to all personnel who enter a Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.

1.0.4.3 Inapplicability of Employee Benefits: This Task Order does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

1.0.4.4 It is the Contractor's, as well as the Government's, responsibility to monitor Task Order activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

1.0.4.4.1 The Contractor shall notify the Contracting Officer in writing via letter or email within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this Section. The notice should include the date, nature, and circumstances of the conduct; the name, function, and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct; identify any documents or substance of any oral communication involved in the conduct; and the Contractor's estimated date when, absent a response, cost, schedule or performance will be impacted.

1.0.4.4.2 The Contracting Officer will, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

1.1 BACKGROUND

The Surface Combatant Gas Turbine Engineering Branch (Code 424) of NSWCPD are In-Service Engineering Agents (ISEA) for multiple gas turbine engine lines and provide services to sustain, maintain, and improve the United States Navy’s propulsion and power generation capabilities. This includes hardware and software support for the gas turbine engines, generators and reduction gear, Full Authority Digital Control (FADC) Local Operating Panel (LOCOP) and Human Machine Interface (HMI computer).

1.2 SCOPE OF WORK

Code 424 requires engineering, technical, and logistical support for gas turbine control hardware and software for Models AG9140RF, AG9140HF, and AG9130HF Ship Service Gas Turbine Generators (SSGTGs). Due to obsolescence and reliability upgrades, the SSGTG control system known as the Full Authority Digital Controller (FADC), has had to improve and evolve under the DDG Modernization program. This has driven the development of two separate software packages (LINUX/ Ignition platform and Windows/ iFIX platform) for each SSGTG Model (AG9140RF, AG9140HF, & AG9130HF) for a total of six (6) software packages.

This support includes bi-weekly, monthly, and yearly meetings in order to ensure efficient communication and proper transfer of information between Code 424 and the contractor. Additionally, support is required for FADC software/hardware revisions, Risk Management Framework (RMF) support, and Cyber Security improvements. This includes production of software, test procedures, test reports, etc. The contractor will be required to travel to military sites, testing locations, vendors, and manufacturers for engineering support.

1) 2.0 APPLICABLE DOCUMENTS

2) AG9140RFM-40HFM-30HFM FADC SARs LIST (Windows).xlsx

3) AG9140RFM-40HFM-30HFM FADC SARs LIST (LINUX).xlsx

3.0. REQUIREMENTS

3.1.0 Contractor shall support LBES testing (1) trip per year onsite at NSWCPD. The contractor shall support the integration of the software at LBES. Reports from technical support and testing will be accordance with CDRL 002 and CDRL 005. Travel in support of this requirement is to the following alternate performance locations.

CONUS/

OCONUS

3.1.1 Contractor shall participate in a biweekly teleconference. Reports, minutes, and action items from meetings will be in accordance with CDRL A001 and CDRL A003 detailed in Section 4 below.

3.1.2 Contractor shall produce or contribute to reports, presentations, spreadsheets, etc. to update Code 424 and its sponsors on work progress. Reports from meetings will be in accordance with CDRL A001, CDRL A002, CDRL A003, and CDRL A004 detailed in Section 4 below.

3.1.3 Contractor shall provide engineering and technical support for all software packages under the DDG Modernization program (AG9140RFM, AG9140HFM, and AG9130HFM). Software and hardware modifications are derived from lessons learned during LBES testing and issues documented during DDG-Modernization.

3.1.3.1 Contractor shall improve the LINUX based HMI Systems and GAP for DDG MOD software in accordance with the AG9140RFM-40HFM-30HFM FADC Software Action Requests (SARs) LIST (LINUX).xlsx. Reports will be in accordance with A006, A007, and A008.

3.1.3.2 Contractor shall improve the Windows based HMI Systems and GAP for DDG MOD software in accordance with the AG9140RFM-40HFM-30HFM FADC Software Action Requests (SARs) LIST (Windows).xlsx. Reports will be in accordance with A006, A007, and A008.

3.1.4 Contractor shall provide engineering and technical support for Models AG9140RFM, AG9140HFM, and AG9130HFM SSGTG FADCs under the DDG MOD program for obsolescence management and resolution, and field service support and troubleshooting. When documents or files are altered during the course of work, revisions shall be submitted in accordance with the CDRLs below.

3.1.4.1 The contractor shall provide engineering support to repair/support FADC components. Report will be in accordance with A004.

3.1.4.2 The contractor shall provide engineering and technical expertise in support of Risk Management Framework (RMF) package development on controls hardware and software. Report will be in accordance with A004.

3.1.4.3 The contractor shall implement cyber security (CS) improvements and controls for software upgrades, patches, CS tools and hardware upgrades to mitigate vulnerabilities and improve cyber security posture in Full Authority Digital Controllers under the DDG Modernization program. This includes implementing and documentation of Secure Technology Implementation Guides (STIGs), Security Content Automation Protocols (SCAPs), vulnerability scans, and other cyber security controls. Report will be in accordance with A006 and A009.

3.1.4.4 Work performed on software/hardware modifications, RMF, repairs etc. as defined above will submit documents/files in accordance with CDRL A001, CDRL A002, CDRL A003, CDRL A004, CDRL A005, CDRL A006, CDRL A007, and CDRL 0009 detailed in Section 4 below.

3.1.5 Period of performance of this contract shall 1 year from award.

3.2 Reserved

3.3 Manufacturing Phase-Out or Discontinuation of Production, Diminishing Sources, and Obsolete Materials or Components

3.3.1 The contractor shall notify the contracting officer immediately upon determining the unavailability of obsolete materials or components. The contractor may recommend a solution to include the impact on the contract price and delivery. The contractor shall not initiate any item redesign or incur any additional costs without the express, written authorization of the contracting officer.

3.4 Diminishing Manufacturing Sources and Material Shortages Management (DMSMS) Contract Requirements

Not Applicable.

3.5 Parts Obsolescence

3.5.1 The contractor shall establish and implement a parts obsolescence program. In the event that manufacturing phase-out or discontinuance of production of such items is contemplated, the contractor is required to notify the contracting officer and publish the discontinuance in the Government-Industry Data Exchange Program (GIDEP), where feasible; and to provide immediate advance notice of production phase-out to TPOC (Carmen Carachilo) and SME (Sahaj Dave) in Code 424.

4.0 DATA REQUIREMENTS

4.1 Contract Status Report (CDRL A001)

4.1.1 This report shall reflect both prime and Subcontractor data if applicable at the same level of detail.

4.1.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.1.3 Status reports shall include the work completed during the time period, work currently in-progress, and work still to be completed. The document shall report the contract money spent, contract money remaining, and tasks contract money was spent on.

4.2 Travel Report (CDRL A002)

4.2.1 This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.2.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.3 Status and Action Items Updates (CDRL A003)

4.3.1 This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.3.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.3.3 Spreadsheets, reports, and minutes to be updated when work is completed and revisions to be sent when work is changed. At a minimum, the document shall include the description of the action, the status, comments, and results. Contractor shall provide updated Software Action Request (SAR) lists.

4.4 Technical Report (CDRL A004)

4.4.1 This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.4.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.4.3 Test reports are required for any testing performed by the contractor or at the contractor’s facility. Test reports shall include: equipment used, test set-up, and test results. Test reports shall indicate if the hardware or software has passed the testing or not. Test reports must be delivered within ten (10) business days of completed testing.

4.4.4 Evaluation reports shall be required in the event of a failed component or a problem with fleet software or hardware.

4.5 Test Procedure (CDRL A005)

4.5.1 This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.5.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.5.3 Testing, installation, or operation procedures shall be delivered no later than five (5) business days prior to the start of testing. Procedures shall include equipment needed, set-up, and detailed procedures.

4.6 Computer Software Product (CDRL A006)

4.6.1 Linux Based FADC Software Action Requests (SARs) Updates

4.6.2.1 This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.6.1.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.6.1.3 When alterations are made to the Graphical Application Program (GAP) control software and executable files (.DLL, .CDR, .GAP, .SH, .OUT, .HEX, etc.), all files shall be provided. This is applicable to Models 9130HFM, 9140HFM and 9140RFM.

4.6.1.4 When alterations are made to the Linux-Based HMI installer software, or HMI project files all revised files shall be provided. This is applicable to Models 9130HFM, 9140HFM and 9140RFM.

4.6.1.5 When alterations are made to the Linux-based Base Image, all revised files (.ISO, etc.) shall be provided.

4.6.1.6 When alterations are made to the Linux based App Manager Software, the revised software shall be provided. When alterations are made to recovery software files, the revised files shall be provided.

4.6.1.7 When alterations are made to the Control Assistant Software, the revised software shall be provided. When alterations are made to recovery software files, the revised files shall be provided.

4.6.1.8 When alterations are made to the Secure Application Tool Software, the revised code shall be provided. When alterations are made to recovery software files, the revised files shall be provided.

4.6.1.9 When alterations are made to the Linux based FADC Utilities, the revised software shall be provided. When alterations are made to recovery software files, the revised files shall be provided.

4.6.1.10 When alterations are made to recovery software files, the revised files shall be provided.

4.6.2 Windows Based FADC Software Action Requests (SARs) Updates

4.6.2.1 This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.6.2.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.6.2.3 When alterations are made to the Graphical Application Program (GAP) control software and executable files (.DLL, .CDR, .GAP, .SH, .OUT, .HEX, etc.), all files shall be provided. This is applicable to Models 9130HFM, 9140HFM and 9140RFM.

4.6.2.4 When alterations are made to the Windows-Based HMI installer software, or HMI project files all revised files shall be provided. This is applicable to Models 9130HFM, 9140HFM and 9140RFM.

4.6.2.5 When alterations are made to the Windows-based Base Image, all revised files (.ISO, etc.) shall be provided.

4.6.2.6 When alterations are made to the Windoes based App Manager Software, the revised software shall be provided. When alterations are made to recovery software files, the revised files shall be provided.

4.6.2.7 When alterations are made to the Control Assistant Software, the revised software shall be provided. When alterations are made to recovery software files, the revised files shall be provided.

4.6.2.8 When alterations are made to the Secure Application Tool Software, the revised code shall be provided. When alterations are made to recovery software files, the revised files shall be provided.

4.6.2.9 When alterations are made to the Windows based FADC Utilities, the revised software shall be provided. When alterations are made to recovery software files, the revised files shall be provided.

4.6.2.10 When alterations are made to recovery software files, the revised files shall be provided.

4.6.3

4.7 Software Version Description: (CDRL A007)

4.7.1 LINUX FADC Software Action Requests (SARs) Updates

4.7.1.1 This report shall reflect both prime and Subcontractor data if applicable at the same level of detail.

4.7.1.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.7.1.3 When alterations are made in accordance with the computer software product, the revised files shall be provided.

4.7.1.4 When alterations are made to the GAP Source Code, control software or executable files, a Software Version Description document will identify: any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.1.5 When alterations are made to the HMI software, a Software Version Description document will identify: any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.1.6 When alterations are made to the Linux based App Manager Software, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.1.7 When alterations are made to the Control Assistant Software, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.1.8 When alterations are made to the Secure Application Tool Software, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.1.9 When alterations are made to the Base Image, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.1.10 When alterations are made to the Linux-based HMI Installer, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.1.11 When alterations are made to the Linux based FADC Utilities, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.2 Windows FADC Software Action Requests (SARs) Updates

4.7.2.1 This report shall reflect both prime and Subcontractor data if applicable at the same level of detail.

4.7.2.2 The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the TPOC.

4.7.2.3 When alterations are made in accordance with the computer software product, the revised files shall be provided.

4.7.2.4 When alterations are made to the GAP Source Code, control software or executable files, a Software Version Description document will identify: any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.2.5 When alterations are made to the HMI software, a Software Version Description document will identify: any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.2.6 When alterations are made to the Windows based App Manager Software, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.2.7 When alterations are made to the Control Assistant Software, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.2.8 When alterations are made to the Secure Application Tool Software, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.2.9 When alterations are made to the Base Image, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.2.10 When alterations are made to the Windows-based HMI Installer, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.7.2.11 When alterations are made to the Windows based FADC Utilities, any new version or release numbers, changes made to the software, and any new or removed capabilities of the software.

4.9 Technical Data Package (CDRL A011)

4.9.1 Obsolescence Report Updates

4.9.1 The obsolescence report shall include critical and non-critical components and be provided and updated annually.

5.0 SECURITY REQUIREMENTS

Not applicable.

5.1 SECURITY TRAINING.

Not applicable.

5.2 ON SITE WORK. Contractor personnel that require a badge to work on-site at one of the NSWCPD sites must provide an I-9 form to verify proof of citizenship. The I-9 form should be signed by the company Facility Security Officer or the company Human Resource Department. In addition to the I-9 form, Contractors shall also bring their birth certificate, current United States Passport or naturalization certificate and state issued ID to the NSWCPD Security Officer at the time of badge request to verify citizenship. Any contractor that has unfavorable information that has not been favorably adjudicated, by Department of Defense Central Adjudication Facility (DOD CAF) will not be issued a badge. Finally, contractors shall supply a copy of their OPSEC Training Certificate or other proof that the training has been completed.

5.2.1 RESERVED

5.2.4 Reserved

5.3 DD254 REQUIREMENT.

Not Applicable.

5.4 OPERATIONS SECURITY (OPSEC)

5.4.1 The Contractor shall protect critical information associated with this contract to prevent unauthorized disclosure. The NSWC Philadelphia Division's (NSWCPD) Critical Information List (CIL)/ CIIL (Critical Indicators and information list) will be provided on site, if warranted. Performance under this contract requires the contractor to adhere to OPSEC requirements, which may include the NSWCPD Contractor OPSEC Plan. When the NSWCPD Contractor OPSEC Plan is required, the contractor shall return acknowledgment of the plan within 15 days of receipt. During the period of this contract, the Contractor may be exposed to, use, or produce, NSWCPD Critical Information (CI) and/or observables and indicators which may lead to discovery of CI. NSWCPD’s CI will not be distributed to unauthorized third parties, including foreign governments, or companies under Foreign Ownership, Control, or Influence (FOCI) unless such FOCI has been appropriately mitigated through measures approved by the Defense Counterintelligence and Security Agency. Questions concerning these requirements shall be directed to the PCO.

5.4.2 CUI correspondence transmitted internally on the contractor's unclassified networks or information systems, and externally, shall be protected per NIST SP-800-171, Protecting Controlled Unclassified Information (CUI) in Non-federal Systems and Organizations.

Assembled large components/systems being transported to and from testing areas, other production or government facilities (whether or not on public roadways) shall be in an enclosed van trailer or covered flatbed trailer. Component/System outside storage, staging, and test areas shall be shielded/obscured from public view wherever physically possible.

5.4.3 NSWCPD’s CI shall not be publicized in corporate wide newsletters, trade magazines, displays, intranet pages or public facing websites. Media requests related to this project shall be directed to the PCO, and the COR who will forward the required to the NSWCPD Public Release Authority for review.

5.4.4 Any attempt by unauthorized third parties to solicit, obtain, photograph, or record, or; incidents of loss/compromise of government Classified or CI, Business Sensitive, Company Proprietary information related to this or other program must be immediately reported to the contractor's Facility Security Officer and Cognizant Security Office and/or the Naval Criminal Investigative Service, and the NSWC PD Security Division (Code 105).

5.4.5 This SOW has been reviewed against the requirements of SECNAVINST 4200.35. SAIRC controls are not required

5.5 RECEIPT, STORAGE, AND GENERATION OF CONTROLLED UNCLASSIFIED INFORMATION (CUI) All Controlled Unclassified Information (CUI) associated with this contract must follow the minimum marking requirements of DoDI 5200.48, Section 3, paragraph 3.4.a, and include the acronym "CUI" in the banner and footer of the document. In accordance with DoDI 5200.48, CUI must be safeguarded to prevent Unauthorized Disclosure (UD). CUI export controlled technical information or other scientific, technical, and engineering information must be marked with an export control warning as directed in DoDI 5230.24, DoDD 5230.25, and Part 250 of Title 32, CFR. Nonfederal information systems storing and processing CUI shall be protected per NIST SP-800-171, or subsequent revisions. All transmissions to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) and posting on social media websites (Facebook, Instagram, Twitter, LinkedIn, etc.) are prohibited. Destroy CUI associated with this contract by any of the following approved methods: A cross-cut shredder; a certified commercial destruction vendor; a central destruction facility; incineration; chemical decomposition; pulverizing, disintegration; or methods approved for classified destruction.

5.6 PLANNING, PROGRAMMING, BUDGETING AND EXECUTION (PPBE) DATA.

When contractor employees, in the performance of their duties, are exposed to Planning, Programming, Budgeting and Execution (PPBE) data, a Non-Disclosure Agreement (NDA) with all affected contactor personnel must be executed in coordination with the COR and PCO to ensure safeguarding disclosure of this data.

5.7 U-NNPI SECURITY REQUIREMENTS

Not Applicable.

5.8 U-NNPI

Not Applicable.

5.9.2 Specific Requirements for Protecting U-NNPI

6.0 PLACE OF PERFORMANCE

The Contractor's primary place of performance shall be at the Contractor’s facility. The contractor shall also travel to military sites, testing locations, vendors, and manufacturers.

6.1.5 Not Applicable.

6.1.6 Not Applicable.

7.0 TRAVEL

7.1 The Contractor is required to travel from the primary performance location when supporting this requirement. The in support of this requirement is anticipated to include the following alternate performance locations.

7.2 The number of times the Contractor may be required to travel to each location cited above may vary as program requirements dictate, provided that the total estimated travel cost is not exceeded. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. All travel shall be approved before travel occurs. Approval may be via email by the Contracting Officer (PCO), the Contacting Officer’s Representative (COR) or the fully executed Technical Instruction (TI) signed by the Contracting Officer.

7.3 All travel shall be conducted in accordance with FAR 31.205-46, Travel Costs, and B-231-H001 Travel Cost (NAVSEA) and shall be pre-approved by the COR (CDRL A002).

7.4 Travel Costs

7.4.1 The current “maximum per diem” rates are set forth in the (i) Federal Travel Regulations for travel in the Continental United States; (ii) Joint Travel Regulations for Overseas Non-Foreign areas (e.g., Alaska, Hawaii, Guam, Puerto Rico, etc.); and (ii) Department of State (DOS) prescribed rates for foreign overseas locations.

7.5 Reserved

8.0 GOVERNMENT FURNISHED PROPERTY REMOVE IF NOT APPICABLE.

Not Applicable.

8.1 Reporting

Not Applicable.

8.2 Shipping Notification

Not Applicable.

8.3 Inventory Reporting

Not Applicable.

8.4 Lost, Damaged or Stolen GFP Reporting

Not Applicable.

8.5 Excess Property Reporting

Not Applicable.

8.6 Property Disposition

Not Applicable.

8.6.1 Property Disposition Instructions

8.6.2 Issuance of the DD 1149 “Requisition and Invoice/Shipping Document”

8.7 Property Closeout.

8.8 Property Tagging:

9.0 GOVERNMENT FURNISHED INFORMATION

1) AG9140RFM-40HFM-30HFM FADC SARs LIST (Windows).xlsx

2) AG9140RFM-40HFM-30HFM FADC SARs LIST (LINUX).xlsx

1) AG9140RF-HF XT FADC HAR LIST Rev 20250314.xlsx

2) AG9140RF-HF XT FADC SAR LIST REV 20250321.xlsx

Estimated date of delivery is within 15 days of contract award. The information will be delivered via encrypted email.

10.0 PURCHASES

10.1 Not applicable

10.2 Not applicable

11.0 COUNTERFEIT MATERIAL PREVENTION

11.1 Electronic End-Items

Not applicable

11.2 Non-Electronic Materiels

Not applicable.

11.2.1 Not applicable.

11.2.1.1 Not applicable.

11.2.1.2 Not applicable.

11.2.1.3 Not applicable.

11.2.1.4 Not applicable.

11.2.1.5 Not applicable.

12.0 PERSONNEL

12.1 Personnel Requirements. Not applicable.

12.2 Not applicable.

12.3 Not applicable.

12.4 Key Personnel

12.5 Non-Key Personnel

12.6 DON Cyberspace IT (Information Technology) / Cybersecurity & Information Assurance Functions and Personnel Requirements

Not applicable.

12.6.1 The table below outlines the requirements for the listed cyber positions:

Not applicable.

13.0 NSWCPD ELECTRONIC COST REPORTING AND FINANCIAL TRACKING (ECRAFT) SYSTEM (REMOVE IF CONTRACT DOES NOT INCLUDE COST TYPE CLINS)

Not applicable.

14.0 SPECIAL REQUIREMENTS (REMOVE IF NOT APPICABLE)

Not applicable.

14.0 SPECIAL REQUIREMENTS

Not applicable.

14.1 Quality Management System

14.2 Risk Management

14.4 Software Development Plan (SDP) (Delete if N/A)

14.5 Applicable NSWCPD Occupational Safety and Health (OSH) /NAVSEA Standard Items 009-01 and 009-112