Software Engineering SOW.docx

Statement of Work (SOW) Software Development Support of Condition Based Maintenance Plus Enterprise Systems

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 532, which supports Remote Monitoring and Condition Based Maintenance (CBM) and Condition Based Maintenance and Enterprise Systems (CBM+)programs.

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 Contract are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract 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 Contract 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 Contract 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 Contract 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 Contract 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

NSWCPD Code 532, as the In-Service Engineering Agent (ISEA) for Condition Based Maintenance (CBM) assessment systems, requires support in the development, implementation and in-service maintenance of comprehensive, integrated condition-based assessment and continuous monitoring programs for surface ship equipment and systems. These efforts aim at achieving significant and real reductions in maintenance expenditures and increased equipment availability, while maintaining the operational survivability of naval ships and submarines. Program goals are to support total productive maintenance in a realistic waterfront effort that considers all aspects of system/equipment operation, maintenance, and logistics support. To execute its responsibilities, NSWCPD requires the support of maintenance engineering specialists to assist in the development, implementation, and in-service support of CBM software and cybersecurity requirements. This support requires responsive and high-quality services that only a specialized contractor can provide.

1.2 SCOPE OF WORK

The contractor shall provide software engineering, technical, logistics, training, and program support and sustainment for the development, prototyping, implementation and in-service support of Condition Based Maintenance (CBM) assessment technologies for naval ship systems on surface ship and submarine hulls for the Machinery Enterprise Information Systems Branch.

2.0 APPLICABLE DOCUMENTS

2.1 General Specifications for Overhaul of Surface Ships (GSO) - NAVSEA S9AA0-AB GOS-010. [https://www.scribd.com/document/266275921/General-Specifications-for-Overhaul-of-Surface-Ships-GSO-pdf]

2.2 Fleet Modernization Program (FMP) Management & Operations Manual - NAVSEA SL720-AAMAN_010/FMP. [http://www.navsea.navy.mil/Portals/103/Documents/SUPSHIP/SOM/Ch14-IntegratedLogisticsSupport-01Nov17.pdf?ver=2017-11-02-120247-767]

2.3 Manuals, Technical: General Style and Format of (Work Package Concept) - MIL-DTL-81927C, dated 26 Nov 1997.

[http://everyspec.com/MIL-SPECS/MIL-SPECS-MIL-DTL/MIL-DTL-81927C_14024/]

2.4 Standard Practice for Manuals, Technical: General Style and Format - MIL-STD-38784(1), dated 1 Dec 2000.

[http://everyspec.com/MIL-STD/MIL-STD-10000-and-Up/MIL-STD-38784A_CHG-1_55081/]

2.5 Interactive Electronic Technical Manuals - MIL-PRF-87269A dated 15 Aug 2000, Data Base, Revisable.

[http://everyspec.com/MIL-PRF/MIL-PRF-080000-99999/MIL-PRF-87269A_3062/]

2.6 Manuals, Technical: General Acquisition and Development Requirements - MIL-DTL-24784.

[http://everyspec.com/MIL-SPECS/MIL-SPECS-MIL-DTL/MIL-DTL-24784C_20774/]

2.7 Guide for User Maintenance of NAVSEA Technical Manuals - S0005-AA-GYD-030.

[http://navybmr.com/study%20material/NAVSEA%20S0005-AA-GYD-030.pdf]

2.8 CMMI® for Development, Version 1.2, CMMI-DEV, V1.2, CMU/SEI-2006-TR-008.

[https://www.sei.cmu.edu/reports/06tr008.pdf]

The Contractor shall reference and utilize the latest version available when performing tasks within this SOW.

3.0. REQUIREMENTS

3.1 Program Management

3.1.1 The contractor shall provide engineering, technical, and management support services to the Naval Surface Warfare Center Philadelphia Division, Code 532.

3.1.1.1 Participate in technical meetings and program reviews related software development and cyber security of Code 532 CBM Systems.

3.1.1.2 Provide action item tracking support and draft meeting minutes, CDRL A009.

3.1.1.3 Develop and provide status on initiatives via Plan of Actions and Milestones (POA&Ms).

3.1.1.4 Develop programmatic and technical briefs regarding the software development and cyber security of CBM systems for various Navy and non-Navy customers.

3.1.1.5 Develop, manage, and extract programmatic and financial data for review and reporting.

3.1.1.6 Provide detail design and engineering development oversight related to CBM software development and cyber security.

3.1.1.7 Generate project plans, concepts of operation, and management outlines.

3.1.1.8 Ensure program and project support is responsive, cost effective and aligned with the objectives of the task order.

3.1.1.9 Perform research and development, design, and implement algorithms using Government-furnished data from Hull, Mechanical, & Electrical (HM&E) networks and control systems, or predictive data in order to support digital twin development for Condition Based Maintenance Plus (CBM+), Total Ship Readiness Assessment (TSRA), Surface Maintenance Effectiveness Review (SURFMER), material readiness, Tech Refresh and Life Cycle standards development.

3.1.1.10 The contractor shall validate algorithms and conclusions with appropriate mechanical and electrical personnel.

3.1.1.11 The contractor shall record the algorithm and software development in accordance with CDRL A004.

3.2 System Design and Integration Engineering for Condition Based Maintenance Systems

3.2.1 The contractor shall assist the Government with the assessment, design, and installation of Condition Based Maintenance (CBM) systems on US Navy Ships and Land Based Test Facilities (LBTF) by supporting system modernization and new concept development which will include: Engineering algorithms, Logic trees (as they pertain to systems diagnostics and prognostics), Failure Mode, Effects and Criticality Analysis (FMECA), Expert systems, Verification and validation of software developed to support these new concepts.

3.2.2 The contractor shall perform analysis and technical studies and provide technical services in the area of Condition Based Maintenance (CBM) systems engineering support. The contractor shall provide support to NSWCPD Software Support Activity (SSA) for developing, installing and functionally testing software for CBM systems, including system Simulators, On Board Trainers (OBT) and Land Based Test Facilities (LBTF).

Areas of particular involvement shall include:

3.2.2.1 Performing investigations and analysis of data, ship plans and Condition Based Maintenance (CBM) systems necessary to develop alteration packages to include Ship Change Documents (SCDs), Engineer Change Proposal (ECPs), Ship Alterations (SHIPALTs), and others as appropriate.

3.2.2.2 Providing engineering support to develop, update, and maintain ship control systems equipment specifications, design documents, and operational requirements.

3.2.2.3 Providing system and equipment reliability, maintainability and availability data, and evaluating failure trending and analysis including Failure Mode, Effects and Criticality Analysis (FMECA) and Reliability and Maintainability studies for system components.

3.2.2.4 Reviewing proposed engineering changes for impact on configuration, performance, reliability, maintainability, logistics support, safety, and life cycle costs.

3.2.2.5 Recommending and performing/supporting redesign, modification, or alteration of hardware and software for system integration and improvements.

3.2.2.6 Conducting systems engineering studies for ship control systems.

3.2.2.7 Provide engineering services and technical support to design, develop, and integrate technological improvements into Condition Based Maintenance (CBM) systems.

3.2.2.8 Provide engineering support to develop, update, and maintain Condition Based Maintenance (CBM) system model-based system engineering (MBSE) artifacts.

3.2.2.9 Provide engineering support to develop, update, and maintain Condition Based Maintenance (CBM) system software specifications, design and requirements documentation, including concept papers, interface reviews, preliminary designs, detailed designs, and system models.

3.2.2.10 Provide engineering support during Condition Based Maintenance (CBM) system design review, system interface requirements review and system software requirements review.

3.3 Computer & Software Programming

performance parameters.

3.3.1.10 Develop, deliver, &/or modify software deployment configuration for Kubernetes, Ansible, Terraform and other deployment technologies that apply as required by NSWCPD.

3.4.2 The contractor shall analyze and design required interfaces using current standard software technology. The contractor shall develop data fusion algorithms for data presentation and onboard analytics capability for machinery, controls, sensor and network engineering systems compatible with containerized software architectures for CBM systems.

3.4.3 The contractor shall develop and optimize machine learning models by employing algorithms and methods for parsing large data sets. The contractor shall incorporate mechanical and electrical expertise from ISEAs and operations and maintenance, drawings, and other data sources into model development and training.

3.4.4 The contractor shall employ pattern recognition and anomaly detection to identify actionable information from data sets including but not limited to CBM systems data sources from CG-47 Integrated Ship Control (ISC), MCM Integrated Ship Control System (ISCS), LCS, DDG-51, Smart Carrier, LPD-17 Engineering Control System (ECS), LSD 41/49 Class, DDG-1000 Machinery Control Systems.

3.4.5 The contractor shall record the algorithm and software development in accordance with CDRL A004.

3.4.6 The contractor shall provide software and algorithm support optimizing analytics and scripting using the Application Programming Interface (APIs) and data exports from CBM systems and other reliability data sets. The contractor shall employ pattern recognition and anomaly detection to identify actionable information from data sets including but not limited CBM systems shipboard, real-time control data.

3.4.7 The contractor shall develop new anomaly detection algorithms and methods to identify informative sensors/data to be used for predictive modeling, configuration management, integrated logistics support, engineering enhancements, and remote monitoring performance.

3.4.8 The contractor shall test, interface, and implement derived data fusion, imputation, optimization, and state awareness algorithms with CBM system and maintenance data sources to support readiness, maintenance philosophy, and life cycle of enterprise monitored HM&E systems.

3.5 Engineering Services

3.6.2 The contractor shall provide supporting documentation for algorithm and model conventions and training methods, as well as necessary API or other interface documentation.

3.6.3 The contractor shall ensure documentation for Capability Maturity Model Integration (CMMI), NSWCPD Systems Engineering Process (SEP), and user documentation is created for algorithms and models incorporated into CBM systems.

3.6.4 The contractor shall ensure interfaces are defined, updated, and maintained, including supporting documentation.

3.7 Cyber Security Support

NSWCPD requires cybersecurity operations support for Shipboard, Non-Shipboard, and Closed-Enclave assets. Installation, configuration, and integration of new technology with IT security standards; file backups; security patches; and the performance of analysis to ensure security controls are properly implemented. Operating systems include multiple variants of Unix/Linux, and Microsoft Windows server and workstation operating systems.

The Contractor shall implement configuration version control practices and processes (i.e. checkout/check-in; version number control; system/software baselines; merge, build, test, and release) for software, hardware, firmware, images, technical manuals, test procedures and other support documentation.

3.7.1 The contractor shall conduct vulnerability assessments of Windows and Linux/UNIX systems, to include:

3.7.1.1 Vulnerability Scanning & Identification Secure Configuration in accordance with STIG findings.

3.7.1.2 Ensure Endpoint Compliance – tasks include deployment and management of host-based security products; issuance of antivirus scans, updates, and management/resolution of any discovered issues such as automated software patch distribution and endpoint imaging processing.

3.7.1.3 Perform intrusion detection analysis and recommend/execute protection against vulnerabilities – tasks include network perimeter Intrusion Detection/Perimeter Security (ID/PS) monitoring, and the adjudication of network-activity; host-based ID/PS monitoring, and the adjudication of host-based activity.

3.7.1.4 Install security patches on servers to eliminate identified vulnerabilities, and report on patch compliance.

3.7.1.5 Perform routine audits of systems and software; add, remove, and/or update user account information and perform password-resets, as applicable in accordance with the latest Roster List.

3.7.1.6 Monitor system-security to maintain security posture, and document the latest version of system-configuration.

3.7.1.7 Conduct performance tuning – tasks include optimization of equipment and devices to ensure performance of parts and systems is as close to their theoretical peaks as possible.

3.7.1.8 Research and recommend methods and procedures to implement new security patches and remediation.

3.7.1.9 Plan and coordinate security measures to safeguard information in computer files against accidental or unauthorized damage, modification or disclosure. Recommendations for implementation shall be presented to NSWCPD.

3.7.1.10 Plan and support the installation and testing of new products and improvements to computer systems, such as the installation of new databases. Recommendations for implementation shall be presented to NSWCPD. If approved, Contractor shall coordinate and schedule the approved installations.

3.7.1.11 Develop and prepare implementation-and-maintenance, access control, inventories, and communications-documentation, as well as Standard Operating Procedures (SOPs).

3.7.2 The contractor shall assist in the preparation of high-level policies and/or strategies for Information Assurance; this includes the development of technical documentation such as Summaries and White papers, Presentations, User manuals, and Administrative Guides.

3.7.3 The contractor shall coordinate and schedule program reviews - Contractor shall maintain master project calendar and coordinate arrangements for presentations/meetings; Contractor shall maintain Plan of Action and Milestones (POA&M).

3.7.4 The contractor shall assist in the creation and preparation of technical documentation such as user manuals, reports, outlines, and summaries.

3.7.5 The contractor shall update and manage software libraries in accordance with (SOP) procedures and execute the destruction of dated versions in accordance with DoD mandates.

3.7.6 The contractor shall provide technical services in support of delivering cyber-secure systems and solutions including the development and submittal of Risk Management Framework (RMF) risk assessments, implementation of DoD secure system configuration and hardening requirements identified in Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) and Security Requirements Guides (SRGs), Assured Compliance Assessment Solution (ACAS) vulnerability assessments, anti-virus (AV) scanning, Standard Engineering Process (SEP) artifacts, and other supporting documentation required for certifying and maintaining afloat, RDT&E, and/or enterprise platforms.

3.7.7 The contractor shall develop RMF Assess & Authorize (A&A) package documentation in accordance with DoD/NAVSEA directives, which includes the following components: Platform IT (PIT) Determination package documentation, System Categorization Form, Information System Continuous Monitoring Strategy (ISCM), Security Plan (SP), Step Concurrence forms, Plan of Actions and Milestones (POA&M), Security Assessment Plan (SAP), Security Assessment Report (SAR), Risk Assessment Report (RAR), Security Authorization Package, CYBERSAFE Certification, Package Endorsement Letters, and any additional administrative/technical resources required for submission.

3.7.8 The contractor shall ensure RMF A&A package is submitted to the certification authority (CA) in sufficient time for review and operational cybersecurity risk recommendation to obtain Designated Accrediting Authority (DAA) authorization decision prior to operations or tests on a live network (i.e. LBES or shipboard).

3.7.9 The contractor shall develop, maintain, and execute all IA related tasks and duties in accordance with regulations to include the development and execution of DIACAP/RMF Program to Plan of Action and Milestone (POA&M) or Security Technical Implementation Guide (STIG).

3.7.10 In accordance with RMF, the contractor shall monitor and maintain the security posture of IT systems to include patching, implementing STIGs, analyzing network traffic, and applying new physical security measures.

3.7.11 The contractor shall develop and/or test new and existing security features to be implemented into the control system operating environment and/or software.

4.0 DATA REQUIREMENTS

4.1 CDRL A001, Contract Status Report

4.2 CDRL A002, Travel Report

4.3 CDRL A003, Contractor’s Personnel Roster

4.4 CDRL A004, Other Direct Costs Report

4.5 CDRL A005, Government Property Inventory Report (PERIODIC)

4.6 CDRL A006, Government Property Inventory Report (FINAL)

4.7 CDRL A007, Technical Report Study/Services

4.8 CDRL A008, Key Events Schedule/ Plan Of Action And Milestones (POAM)

4.9 CDRL A009, Meeting Minutes

4.10 CDRL A010, CSWF Baseline Certifications

4.11 CDRL A011, Source Code

5.0 SECURITY REQUIREMENTS

5.1 SECURITY TRAINING. The Contractor is responsible for completing all required Government mandated training to maintain security and network access to government sites and IT systems to include but not limited to: Antiterrorism Level 1 Awareness; Records Management in the DON: Everyone's Responsibility; Training and Readiness: The Active Shooter; NAVSEA Introduction to Controlled Unclassified Information; Operations Security (OPSEC); NAVSEA Counterintelligence Training; Privacy and Personally Identifiable Information (PII) Awareness Training; NAVSEA Physical Security training and Cybersecurity 101 Training. Certificates of successful completion shall be sent to the COR and as otherwise specified in the contract.

5.1.1 In accordance with the National Industrial Security Program Operating Manual (NISPOM) (37 CFR Part 117), Contractor personnel that require access to Department of Navy (DON) information systems and/or work on-site require an open investigation or favorable adjudicated Tier 3 by the Vetting Risk Operations Center (VROC). An interim clearance is granted by VROC and recorded in the Defense Information System for Security (DISS). An open or closed investigation with a favorable adjudication is required prior to issuance of a badge providing access to NSWCPD buildings. Furthermore, if the Navy Central Adjudication Facility, have made an unfavorable determination access will be denied. For Common Access Card (CAC) you must have an open investigation and/or a favorably adjudicated investigation. Interim security clearance are acceptable for a CAC. Access will be denied for anyone that has eligibility pending in DISS. Vetting through the National Crime Information Center, Sex Offender Registry, and the Terrorist screening database shall be process for a contractor that does not have a favorable adjudicated investigation.

5.1.2 Within 30 days after contract award, the contractor shall submit a list of all contractor personnel, including subcontractor employees, who will have access to DON information systems and/or work on-site at one of the NSWCPD sites to the appointed Contracting Officer Representative (COR) via email. The contractor shall provide each employee's first name, last name, contract number, the NSWCPD technical code, work location, whether or not the employee has a CAC and or Standard Access Control Badge (SACB), the systems the employee can access (i.e., NMCI, RDT&E), and the name of the Contractor's local point of contact, phone number and email address. Throughout the period of performance of the contract, the Contractor shall immediately provide any updated information to the COR when any Contractor personnel changes occur including substitutions or departures.

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.3 DD254 REQUIREMENT. This effort may require access to classified information up to the SECRET level. No classified data will be generated or stored by the Contractor. The Contractor is required to have and maintain a SECRET clearance. The requirements of the attached DD Form 254 apply.

5.3.1 The contractor is required to maintain a Facility Security Clearance (FCL) in accordance with the DD254 to perform certain work under the contract. Although it is not required at time of award, it shall be obtained within 30 after award. Otherwise the government will have no obligation to continue ordering work under the contract and may not exercise any of the available options.

5.3.2 The Contractor shall appoint a Facility Security Officer (FSO), who shall (1) be responsible for all security aspects of the work performed under this contract, (2) assure compliance with the National Industrial Security Program Operating Manual (NISPOM) (32 CFR Part 117), and (3) assure compliance with any written instructions from the NSWCPD, Security Office.

5.3.3 The contractor shall forward signed copies of DD254s provided to subcontractors to the Naval Surface Warfare Center Philadelphia Division (NSWCPD), ATTN: Security.

5.3.4 The contractor shall direct the subcontractor to obtain approval, through the prime Contractor, for the public release of information received or generated by the sub through the prime Contractor.

5.3.5 The contractor shall submit the subcontractor request for public release through the technical point of contact identified on the DD 254.

Additional information related to the facility clearance process can be obtained by visiting www.dss.mil or http://www.dss.mil/isec/pcl_index.htm.

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.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.

6.0 PLACE OF PERFORMANCE

6.1 The primary place of performance will be at Naval Surface Warfare Center, Philadelphia, PA. The contractor will have to perform work at the contractor’s facility, as well. Routine visits between contractor personnel and government personnel for liaison with appropriate officials and performance of work is required. Local commuting expenses will not be reimbursed. Travel may be required to the locations listed in Section 7 below.

To ensure support is available as required, the contractor must be in the Region/Zone of the Philadelphia Naval Business Center and require not more than local travel orders for the Program representatives to visit the Contractor’s facility. The contractor’s facility must have adequate capabilities (floor space, high speed data connectivity, computers, telephones, conference rooms, and printers) to fully support those portions of the SOW that does not require on-site presence. At least 55% of the work under this task is to be performed on-site at the local Philadelphia NSWCPD office.

Contract. The Contractor shall provide a list of employees who require access to these areas, including standard security clearance information for each person, to the Contracting Officer Representative (COR) no later than three business days after the date of award. The work space provided to the Contractor personnel shall be identified by the Awardee, with appropriate signage listing the company name and individual Contractor employee name.

6.1.4 Access to Government buildings at Naval Surface Warfare Center Philadelphia Division is from 0600 to 1800 Monday through Friday, except Federal holidays. Normal work hours are from 0600 to 1800, Monday through Friday. Contractor employees shall be under Government oversight at all times. Government oversight requires that a Government employee be present in the same building/facility whenever Contractor employee(s) are performing work under this Contract. Contractor personnel are not allowed to access any Government buildings at NSWCPD outside the hours of 0600 to 1800 without the express approval of the Procuring Contracting Officer (PCO).

6.1.5 Reserved

6.1.6 Early Dismissal and Closure of Government Facilities

6.1.6.1 When a Government facility is closed and/or early dismissal of Federal employees is directed due to severe weather, security threat, or a facility related problem that prevents personnel from working, onsite Contractor personnel regularly assigned to work at that facility should follow the same reporting and/or departure directions given to Government personnel. The Contractor shall not direct charge to the contract for time off, but shall follow its own company policies regarding leave. Non-essential Contractor personnel, who are not required to remain at or report to the facility, shall follow their parent company policy regarding whether they should go/stay home or report to another company facility. Subsequent to an early dismissal and during periods of inclement weather, onsite Contractors should monitor radio and television announcements before departing for work to determine if the facility is closed or operating on a delayed arrival basis.

7.0 TRAVEL

7.1 The Contractor may be required to travel from the primary performance location when supporting this requirement. The estimated number of trips is 595 trips for the entire period of performance.

The contractor shall be required to travel CONUS (any state in USA) and OCONUS (primarily Japan, and any country in Europe) to accomplish the tasks contained in this contract. Travel in support of this requirement is anticipated to include, but may not be limited to, 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.2.1 In accordance with the TI instructions, before initiating any travel the Contractor(s) shall submit a detailed and fully-burdened estimate that includes the number of employees traveling, their expected travel costs for airfare, lodging, per diem, rental car, taxi/mileage and any other costs or actions requiring approval. The travel estimate shall be submitted to the Contracting Officer's Representative (COR) and Contract Specialist. Actuals cost, resulting from the performance of travel requirements, shall be reported as part of the Contractor's monthly status report. The reportable cost shall also be traceable to the Contractor's invoice

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

GFP is required for completion of tasks under this SOW. All Government Furnished Property is property of the U.S. Government and shall not be transferred to any individual or agency, public or private, without the express written approval of the originating Contracting Officer.. Accountability for Government Property under this task order shall be managed in accordance with FAR Part 45 and DFARS Part 245 as well as the Government Property clauses in the Task Order, regardless of whether the property is Contractor Acquired Property (CAP), GFP, or received directly from another commercial source as a deliverable from a Government issued contract.

Additional Government Property accountability requirements are outlined in the following Directives and Instructions and shall be adhered to as applicable:

· DODI 4161.02, Accountability & Management of Government Contract Property

· DoDM 4140.01, DoD Supply Chain Material Management Procedures: Material Returns, Retention and Disposition

· DODI 5000.64, Accountability & Management of DoD Equipment and Other Accountable Property

· OPNAVINST 4440.26B, Operating Materials & Supplies and Government Furnished Material Management

· SECNAVINST 5200.43A, Property Management

All GFP identified in Attachment A shall be provided no later than 9/1/2026.

8.1 Reporting

The Contractor shall perform reporting functions and actions to maintain an accurate accounting of property. Receipt Reporting: DFARS 252.245-7005 “Management and Reporting of Government Property” requires the Contractor to report receipt of all GFP using the PIEE GFP Module.

8.2 Shipping Notification

FAR 52.245-1 requires the Contractor to report when GFP is returned to the Government. DFARS 252.245-7005 “Management and Reporting of Government Property” requires this notification be in the form of a shipment through the GFP Module in PIEE.

8.3 Inventory Reporting

FAR 52.245-1 requires the Contractor to periodically perform, record, and disclose physical inventory results. While the FAR clause does not define “periodically,” SECNAVINST 5200.43A requires on-hand inventory count reports to support property type specific inventory requirements as set forth in their respective governing instructions. The contractor shall provide an inventory report in accordance with CDRL X. The Government Property Inventory Report outlines the frequency of reporting based on property type per contract needs. If the contractor does not possess any GFP, the Government Property Inventory Report shall reflect no GFP on-hand as required on the reporting schedule.

The Contractor shall provide support within a reasonable time after the Government’s written request to support any Government audit in which GFP, or its related documentation, is requested as part of normal audit processes.

8.4 Lost, Damaged or Stolen GFP Reporting

FAR clause 52.245-1 requires the Contractor to investigate and report to the Government all incidents of property loss as soon as the facts become known. DFARS 252.245-7005 “Management and Reporting of Government Property” further requires the Contractor to report lost, damaged or stolen Government property using the Property Loss functionality within the PIEE GFP Module. The Contractor shall support the Government’s process to assign liability and document loss in support of lost, damaged or stolen GFP.

8.5 Excess Property Reporting

Per FAR 52.245-1, the Contractor shall promptly disclose and report Government property in its possession that is excess to contract performance.

8.6 Property Disposition

Government Property Distribution shall be in line with FAR 52.245-1(j) and DFARS 252.245-7005 “Management and Reporting of Government Property". The contractor shall provide a written notice to the Contracting Officer when property held under this contract has not been used in 100 calendar days. All General Equipment/assets provided as GFP shall be returned to the Government for disposition at the completion of its use unless otherwise directed in writing by the Contacting Officer or the Accountable Property Officer (dependent on who is administering the contract). The Contractor shall complete the plant clearance inventory schedule using the plant clearance capability of the GFP module of the PIEE to generate an electronic equivalent of the SF 1428, Inventory Disposal Schedule.

The contractor shall obtain PCO or plant clearance officer approval (dependent on who is administering the contract) prior to disposal of excess GFP/CAP after the contractor completes the plant clearance inventory schedule.

8.6.1 Property Disposition Instructions

All Contractor Acquired Property shall be delivered to the Government with a DD Form 1149. The DD Form 1149 shall include the following:

• Dollar Value

• Purchase Request Number

• Item Description

• Serial Number

• Model Number

• Quantity

• Task Order Number

• Technical Point of Contact

• Assigned Unique Serialized Identification Number

• All Delivered items for which the Government’s unit acquisition cost is $5,000.00 or more shall have an IUID tag and the corresponding information uploaded into iRAPT (Invoicing, Receipt, Acceptance and Property Transfer)

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

The contractor must obtain a DD1149 before removing any Government Furnished Property, including Plant, Property, and Equipment (PP&E) from NSWCPD premises for general use. For situations where the contractor picks up/replaces NSWCPD property for maintenance purposes, the contractor shall provide an equipment receipt, showing Manufacturer, Model/Part Number, Serial Number and Asset Number/Barcode, on their company letterhead to the COR. Any and all GFP returned to the Government shall include a DD 1149 to document transfer of liability back to the Government.

8.7 Property Closeout. IAW FAR 52.245-1, the Contractor shall promptly perform and report to the PCO or plant clearance officer (dependent on who is administering the contract) contract property closeout to include reporting, investigating and securing closure of all loss of Government property cases; physically inventorying all property upon termination or completion of this Contract/TO; and disposing of items at the time they are determined to be excess to contractual needs.

8.8 Property Tagging:

The contractor can either tag issued equipment or use the provided NSWCPD Plant property barcodes, or NMCI asset tags. If the contractor chooses to use their own tag, it shall not cover the NSWCPD barcode, or NMCI asset tag. The NSWCPD barcode, and or NMCI asset tag number, when provided shall be used on contractor inventory reports.

9.0 GOVERNMENT FURNISHED INFORMATION

Not applicable

10.0 PURCHASES

10.1 Only items directly used and incidental to the services for this Contract and for work within the scope of the Statement of Work, shall be purchased under the Other Direct Cost (ODC) line items. Purchases of an individual item that is valued above $10,000 shall be approved by the Contracting Officer prior to purchase by the Contractor. The purchase request and supporting documentation shall be submitted via email to the Contracting Officer and the Contracting Officer's Representative (COR) it shall be itemized and contain the cost or price analysis performed by the Contractor to determine the reasonableness of the pricing.

10.2 Information Technology (IT) equipment, or services must be approved by the…