Statement of Work (SOW) for Fleet New Construction and In-Service Provisioning, and Availability Logistics Support

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 315, which is responsible for research and development, test and evaluation, (RDT&E) engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Code 315, which is responsible for Fleet Acquisition, Construction and Life Cycle provisioning, supply support, Diminished Manufacturing Sources and Material Shortages (DMSMS) management, and shipboard configuration for the Integrated Logistics Support (ILS), for the Hull, Mechanical and Electrical (HM&E) systems and equipment installed on U.S. Navy surface ships and submarines.

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

This effort is in support of the Provisioning and Supply Support Branch (Code 315) of the Integrated Logistics Engineering, Readiness and Training Division (31), Machinery Research, Logistics and Ship Integrity Department (30). These branches are responsible for development and processing of Provisioning Technical Documentation (PTD) and Configuration Overhaul Planning (COP aka Configuration) in support of new construction, overhaul and the Station’s alteration and sustainment programs. This includes action on any logistics items reported and verified through other sources as well as updating associated products and configuration. This includes the coordination and development of PTD and logistics documentation for all U.S. Navy ship classes for new construction, fleet sustainment or operating ships, and overhaul programs. Code 315 provides expertise for all aspects of provisioning and logistic documentation, aimed at achieving optimum repair part effectiveness for all HM&E systems and equipment on U.S. Navy ship classes, and serves as the Technical Support Authority (TSA) to validate all provisioning packages prior to release to NAVSUP WSS.

This effort also includes support of Configuration Management, Provisioning and all associated machinery research and development programs. NSWCPD develops, implements, provides and maintains logistic products to provide Supply Support for Life Cycle and New Acquisition programs for HM&E systems and equipment installed on U.S. Navy surface ships and submarines.

1.2 SCOPE OF WORK

The contractor shall provide support for Code 315 for Fleet New Acquisition and Sustainment Logistics efforts. This support includes Logistics Support, Supply Support, Project Management Support, Provisioning, Information Technology support and Program Management Support. This support requires the contractor to provide technical data systems development, maintenance and infrastructure support, support of joint logistics products and processes, design, development, testing and fielding support for joint technical data integration efforts, technical data packages and other data support, technical data conversion, and distribution/management of technical data. The contractor shall furnish services a products in support of the following areas:

· Provisioning

· Availability Support

· Engineering and technical services

· Configuration Management

· Remedy Tracking (trouble tickets)

· In-Service Engineering Activity (ISEA) coordination/integration

· Metrics capture and tracking

· ILS coordination

· Program Support and Program Management for Provisioning

· Fleet Cosal Feedbacks (FCFBRs) and Allowance Change Requests (ACRs)

· Information Technology/Data Base development and management support

· Reprovisioning

2.0 APPLICABLE DOCUMENTS

2.1 MIL-PRF-49506, Logistic Management Information (LMI)

2.2 NAVSEA Technical Specification 9090-1500 (series) Provisioning Allowance, and Fitting Out Support (PAFOS), dated 2011. Chapters 4 and 8 are superseded by NAVSEAINST 4423.05 and NAVSEA S00010421-MAN-010. Chapters 1, 5, and 6 were updated in 2025. All remaining chapters are from 2011 and should be used for reference only.

2.3 NAVICP Internal Instruction 4441.170A - COSAL Use and Maintenance Manual

2.4 SL720-AA-MAN-030, Surface Ship and Carriers Entitled Process for Modernization, Maintenance, & Operations Manual

2.5 NAVSEA Technical Specification 9090-700, Ship Configuration and Logistic Support Information System, July 2005

2.6 Naval Sea Logistic Center - Integrated Logistic Support (ILS) Desk Guide Version 2.0.5

2.7 NAVSEA S9AA0-AB-GSO-010/GSO, General Specification for Overhaul of Surface Navy Ship.

2.8 NAVSEA S9AA0-AA-SPN-010/GEN SPEC, General Specifications for Ships.

2.9 NAVSEA Instruction M4423.5, Provisioning Policy, dated 7 May 2019

2.10 Provisioning Tech Manual, S00010421-MAN-010 dated April 7, 2025

2.11 MIL-STD-1522/1561: Provisioning Procedures and Technical Documentation (with SPCC Addendum): DOD 5400.07 Freedom Information Act Program: https://dap.dau.mil/policy/Lists/Policy%20Documents/DispForm.aspx?ID=2630

2.12 MIL-STD-480: Configuration Control - Engineering Changes, Deviations and Waiver www.everyspec.com

2.13 MIL-STD-482: Configuration Status Accounting Data Elements and Related Features, www.everyspec.com

3.0 REQUIREMENTS

3.1 The contractor shall provide engineering, technical, and logistics support to establish and maintain effective Provisioning and Supply Support. This includes the identification and resolution of material condition discrepancies in support of fleet maintenance philosophies; Fleet Coordinated Shipboard Allowance Listing (COSAL) Feedback Reports (FCFBR’s) Allowance Change Requests (ACR’s), Remain in Place (RIP) request, Fleet/ISEA/Naval Sea Systems Command (NAVSEA)/Type Commander emails and phone calls and other avenues of reporting discrepancies; providing Government Furnished Equipment (GFE) and Contractor Furnished Equipment (CFE) tracking support and provide support for the update and maintenance of configuration data for upload to the Weapons System File/ Configuration Data Managers Database - Open Architecture (CDMD-OA) (to be replaced by Model Based Product Support (MBPS) and providing system provisioning support. Contractor will also modify and support Supply Support Tracker (SST) database, to update critical provisioning database, that captures workflow between Code 315 Diminishing Manufacturing Sources Material Shortages (DMSMS) and Code 315 Provisioning efforts, tasks and reporting.

3.1.2 Contractor shall support provisioning efforts with Integrated Logistics Information Tool (ILIT) and Interactive Computer Aided Provisioning System (ICAPS) use for building and releasing package updates.

3.1.3 Contractor shall also support input and workflow management associated with the stations Integrated Product Support Hub (IPS Hub) for the tracking and execution of provisioning actions across NSWCPD.

3.1.4 Contractor shall support Programmatic meetings for provisioning support, including attending Provisioning Guidance Conferences and other Programmatic provisioning meetings, capturing action items and provisioning requirements, and maintaining trackers with programmatic updates.

3.1.5 Contractor shall provide management oversight for the provisioning teams in evaluating provisioning packages being completed against New Acquisition, maintenance, modernization and sustainment schedules to ensure costs and schedule are in alignment of sponsor objectives.

3.1.6 These services are required in support of the new construction/acquisition, overhaul, modernization, and repair of shipboard HM&E systems, as well as life-cycle maintenance and sustainment support of other U.S. Navy systems and Foreign Military Sales (FMS) programs for and associated life-cycle logistics support documentation per requirements of references in Section 2.0.

3.2 Supply Support – In Support of Provisioning

3.2.1 The contractor shall develop, review, update, and maintain complete supply support documentation and shall be responsible for obtaining and analyzing various forms of Technical Data Packages (TDP) / Engineering Data for Provisioning (EDFP), maintenance plans, engineering drawings, reliability data, level of repair, and scheduled maintenance data in support of the supply support / provisioning process per reference 2.2.

3.2.2 The contractor shall identify spare parts (e.g. On Board Repair Parts (OBRP), Installation and Check Out (INCO) and Depot requirements), consumable material requirements, perform inventory management, and determine lead times.

3.2.3 The contractor shall provide services to assist in data migration of the Provisioning Contract Control Number (PCCN) Tracker from third party systems into the Remedy logistics tool Supply Support Tracking (SST) database that is owned and managed by Division 31 and housed within NAVLOGTD. Contractor will also subsequently maintain the database, ensure updates and software updates are made as required, and will integrate new technical requirements and functionality, as required, on behalf of Code 315. Builds will be supported to meet current CYBER requirements and must demonstrate understanding of NAVLOGTD and technical requirements for hosting within this domain. Contractors will assist in any requirements development and or refinement in support of functionality improvement efforts.

3.3 Fleet Provisioning Development and Support Management

3.3.1 The contractor shall process inbound technical drawings for cataloging into NAVSEA’s Model Based Product Support (MBPS) drawing repository (or future replacements) the Naval\Shipyard Engineering Repository (NSEDR) by reviewing proprietary information and disseminate the drawings on a need to know basis.

3.3.2 The contractor shall use photo-editing software, as needed, to touch up drawings to make them more legible, and demonstrate use and knowledge of PixEdit software. Contractor shall demonstrate operating, downloading and handling drawings and images, ensuring proper requirements for handling of classified and SUBSAFE documentation, as well as unclassified drawings. Contractor must have knowledge of Engineering Drawings or Records (EDOR.) Contractor must be able to demonstrate a volume of 60,000 images per year for NSWCPD, and 4,500 drawings per year for NSWCPD.

3.3.3 The contractor shall perform quality assurance reviews in the NSEDR MBPS drawing repository database to check for errors and to confirm drawings are properly catalogued.

3.3.4 The contractor shall contact government provisioning personnel for assistance checking the MBPS drawing repository NSEDR database to obtain drawings they do not have access to.

3.3.5 The contractor shall provide in depth guidance recommendations for NSWCPD provisioning process policy development.

3.3.6 The contractor shall develop draft implementation procedures and training guidance for provisioning personnel.

3.3.7 The contractor shall coordinate, schedule, and conduct DLA/Navy Working Group meetings to include Engineering Support Working Group (ESWG), and Provisioning Center of Excellence (PCOE) meetings among the Navy, DLA and other Services for matters involving equipment configuration control and provisioning Federal Logistic Information Data. Contractor shall support brief development for provisioning topics, and programmatic support for these meetings as required. Contractor shall run provisioning reports for requirements, progress of ongoing efforts, financial progress, meeting minutes, and other documents as requested.

3.4 Ship Change Document (SCD) and Alteration Support

3.4.1 The contractor shall review HM&E SCDs, Engineering Change Proposals (ECPs), and alteration drawing packages to determine sparing impact, conduct research for supply support, review provisioning updates and create new APLs, review configuration updates, and review Preventative Maintenance System (PMS) and tech manual updates resulting these SCDs or alterations. This is to be done using software packages including:

a. Federal Logistics (FEDLOG)

b. CDMD-OA

c. Preventive Maintenance System Schedule (PMS-MIS)

d. Technical Data Management Information System (TDMIS)

e. Others - such as the Navy Data Environment (NDE)

f. Model Based Product Support (MBPS)

g. Deckplate

h. Naval Enterprise Service Desk (NESD)

i. NAVLOGTD (Supply Support Tracking, PCCN Tracking)

3.4.2 The contractor shall compile Configuration Overhaul Planning (COP) data for determination of a need for interim spares on boar HM&E equipment being installed for an SCD or ECP scheduled for installation.

3.4.3 The contractor shall provide availability coordination support to ensure that all planned SCDs with HM&E equipment being installed are reviewed for establishment of interim spares or onboard repair OBRPs.

3.4.4 The contractor shall establish and maintain a tracking system of Technical Assessment Team (TAT) and installing activity review each SCD being installed during an availability to ensure it has been screened by NSWCPD and thoroughly reviewed for interim spares and OBRPs.

3.4.5 The contractor shall review existing and develop new ILS Certification documentation for NSWCPD via the NDE ILS Certification Module to ensure proper life-cycle logistics support is available before deployed or re-deployed scheduled ship availabilities have occurred.

3.4.6 The contractor shall ensure the assigned ship's systems and equipment have necessary levels of configuration identification, logistics support and proper logistics technical documentation per references (2.4) and (2.6).

3.4.7 The contractor shall prepare Configuration Overhaul Planning (COP) documents and coordinate with Configuration Data Managers (CDMs) as required.

3.4.8 The contractor shall maintain the Availability Planning Tool (APT) to ensure that all procedural, technical and logistics requirement for installations of alterations and modifications are met prior to the commencement of the availability.

3.5 Provisioning - Allowance Parts Lists / Allowance Equipage Lists (APL/AEL) Development, Maintenance, and Support

3.5.1 The contractor shall develop and/or review PPLs and other provisioning lists using the Interactive Computer Aided Provisioning System (ICAPS), the Automated Maintenance Planning System (AMPS) and equipment level drawings, along with EDFP.

3.5.2 The contractor shall confirm the accuracy and adequacy of developed/reviewed PPL and resolve discrepancies or deficiencies as appropriate.

3.5.3 The contractor shall review Statements of Prior Submission (SPS) provisioning packages and SPS with Change provisioning packages for accuracy and adequacy and determine if a new PPL/APL is required and report and process accordingly.

3.5.4 The contractor shall develop PPLs to add maintenance significant items that are not currently listed on APL/AEL’s.

3.5.5 The contractor shall review alteration drawings to identify APL/AEL equipment managed by NSWCPD that was installed or removed and develop APL/AEL’s as required.

3.5.6 The contractor shall review EDFP, and where required, develop PPLs using the ICAPS C/S for APL/AEL worthy equipment.

3.5.7 The contractor shall review/assign provisioning technical coding, including Source Maintenance and Recoverability (SM&R), Allowance Factor Codes (AFC) and Best Replacement Factor and Technical Replacement factors (BRF/TRF) to existing and new being developed.

3.5.8 The contractor shall use ICAPS (to be replaced by MBPS) to develop PPLs and other new/revised provisioning lists.

3.5.9 The contractor shall review SPS provisioning packages and SPS with change provisioning packages for accuracy and adequacy and approve/adjudicate/reject as required.

3.5.10 The contractor shall review fleet feedback reports, message traffic, 3M data, distance support issues (Navy 311 tickets), a NAVSUP and DLA reported issues to identify and correct APL/AEL discrepancies and deficiencies by developing draft response corrected PPLs and other provisioning lists as required and providing all required documentation for closure as an APL/AEL updates.

3.5.11 In accordance with reference 2.9 the contractor shall review and respond to Fleet COSAL Feedback Reports (FCFBR) w workable resolution/solution within 20 calendar days of receipt from their government counterpart and shall provide weekly status updates to report the number of FCFBRs that have been received, are in work, and closed out. Weekly closure rate objective is 6 FCFBRs per week, with a threshold of 40 per week.

3.5.12 Should any FCFBRs remain open beyond 45 days the contractor shall provide a detailed report of what caused the delay, of the FCFBR and the plan they are implementing in order to close-out the delinquent FCFBR. Contractor will support weekly meetings for troubled tickets, and utilize waterfront support to adjudicate and perform shipboard visits if required, to assist with closure. Contractor shall provide metrics for sponsor, including dashboards, tables, and graphs showing month to month information in support of monthly and quarterly programmatic meetings.

3.5.13 The contractor shall review SCDs, ECPs and Alteration Support and develop and/or modify APL/AEL’s as required.

3.5.14 Contractor shall utilize the Integrated Products Hub (IPS) hub to review tickets that come into Code 315 for adjudication for configuration updates, and provisioning updates and changes, and work packages accordingly. CASREP tickets will be prioritized.

3.5.15 Contractor shall maintain metrics for PCCN Tracking and ensure that all team workloads are accounted for and captured, across New Construction and Sustainment programs for Configuration, FCFBRs and Fleet requests, and Provisioning tasking.

3.5.16 Contractor will support provisioning meetings as required for Program Reviews, Quarterly Reviews, ISEA discussions, re-provisioning efforts, and policy meetings with SEA06 as required.

3.5.17 Contractor will support the Navy with complex HM&E re-provisioning efforts, including items that were entirely missed during initial New Construction provisioning or new items in support of sustainment installations, and will develop APL Trees, lay-out APLs, and assist with research on existing NSNs to best support provisioning efforts. Contractor must fully understand all aspects of reprovisioning, and explain all necessary steps, pointing to applicable database and research they have completed to support large scale re-provisioning projects.

3.5.18 Contractor shall use Integrated Logistics Information Tool (ILIT), to release workflow to NAVSUP WSS after provisioning packages have been created within ICAPs. Contractors shall run reports out of ILIT as required, and be knowledgeable in executing ECAT requests within NAVSUP for provisioning updates, or review SSR Rejects that come back from WSS regarding questions on provisioning. SAAR is required for ILIT access.

3.5.19 Contractor shall demonstrate knowledge and understanding of the latest NAVSEA provisioning policies, manuals and instructions, as managed and dictated by NAVSEA06.

3.5.20 Contractor shall attend NSLC hosted ICAPS trainings, as required.

3.6 Configuration Status Accounting (CSA) Support

3.6.1 The contractor shall review alteration drawings to identify configuration-worthy items and determine changes required to support alteration.

3.6.2 The contractor shall develop CDMD-OA work files to update the ship’s configuration to support alterations to add or delete APL/AEL’s from the ship’s configuration and adding logistic and alteration information and reviewing the resultant files to ensure the Configuration Data Managers (CDMs) have processed the changes.

3.6.3 The contractor shall conduct Validation and Verification (V&V) of newly installed systems or equipment to ensure that logistics d matches actual configuration and provide detailed reporting on the results. The government will determine whether the V&V will completed by means of desktop (drawing) or shipboard (physical sight) audit.

3.6.4 The contractor shall review CDMD-OA within 45-days after submission of a work file to ensure that the CDMs have processed changes per reference 2.5.

3.6.5 The contractor shall assist with physical sight validation audits.

3.6.6 Contractor shall attend MBPS trainings for configuration as needed.

3.7 Unique Identification (UID) Support

3.7.1 The contractor shall support development and implementation of the DoD Item Unique Identification (IUID) program to leverage integrate Automatic Identification and Data Capture (AIDC) capabilities with DoD Total Asset Visibility (TAV) initiatives.

3.7.2 The contractor shall facilitate the utilization of industry best practices and foster continuous process improvement.

3.7.3 The contractor shall incorporate IUID markings and passive Radio Frequency Identification (pRFID) into legacy Alteration Install Team (AIT) programs to support Sponsor Owned Material (SOM) / Government-Owned Material (GOM) tracking systems as req

3.7.4 The contractor shall provide the pRFID technology and skills required to mark items using various methods, including direct part marking, and submit item pedigree data to the IUID Registry, CDMD-OA and Real-Time Outfitting Management Information System (ROMIS)/ Real-Time Outfitting Management Information System Visibility (ROMISVIS).

3.8 Commonality of Systems, Subsystems, and Components – N/A

3.9 Manufacturing Phase-Out or Discontinuation of Production, Diminishing Sources, and Obsolete Materials or Components n/a

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

The contractor shall support provisioning requirements that were identified as a part of Diminishing Manufacturing Sources Material Shortages (DMSMS) proactive and reactive monitoring. This could also include Remedy Tickets, ESRS Tickets, and 339 Tickets that come to NSWCPD for adjudication for HM&E Systems. In support of DMSMS provisioning efforts, the contractor shall:

· Add, delete, modify, or create new APLs or NSNs in conjunction with validated In-Service Engineering Agent (ISEA) and Technical Warrant Holder (TWH) approvals

· Create Configuration work files to update associated ship configuration records

· Review Engineering Change proposals (ECPs), Ship Change Documents (SCDs), and fielding plans to address provisioning concerns. Review drawings associated with SCDs and ECPs to identify provisioning philosophy.

· Review ILS Certifications if required, and validate that provisioning changes are incorporated to the ship’s configuration and records.

· Complete provisioning packages in ICAPs and ILIT to address DMSMS identified in Sustainment, and New Construction Programs, in line with SOW Section 3.5.

· Ensure Supply Support Tracker (SST) and PCCN Tracking are updated with provisioning PCCNs once provisioning work files hit a Weapons System File (WSF) date in ERP.

3.11 Parts Obsolescence

n/a

4.0 DATA REQUIREMENTS

· CDRL A001, Contract Status Report

· CDRL A002, Travel Report

· CDRL A003, Contractor’s Personnel Roster

· CDRL A004, Government Property Inventory Report (PERIODIC)

· CDRL A005, Government Property Inventory Report (FINAL)

· CDRL A006, Contract Spend and Expenditure Plan

· CDRL A007, Small Business Utilization Report

· CDRL A008, Systems Security Plan

· CDRL A009, Technical Report – Study/Services (Technical Reports)

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 investigation. An interim clearance is granted by DCSA and recorded in the Defense Information System for Security (DISS). Must have a favorable fingerprint an open or closed investigation with a favorable adjudication in DISS is required prior to issuance of a badge providing access to NSWCPD buildings. Furthermore, if the Navy Central Adjudication Facility has 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 is 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 REAL 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 This effort requires 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 INSERT DAYS 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 Contractor must submit a flow down request for sharing of classified and other sensitive information between prime and subcontracts in writing to the COR and Security Contracting Officer (SCO), louise.r.brunson.civ@us.navy.mil. Each request must reference a contract number identifying the specific information for which approval is sought, a justification for needing to share the information, the contractor’s name and its contract number under which the requested information will be shared.

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

5.3.5 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.6 The contractor shall submit the subcontractor request for public release through the technical point of contact identified on the DD254.

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.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 listed on the “NSA/CSS Evaluated Products List for High Security Crosscut Paper shredders”; 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

5.7.1 Security Classification Guidance is as follows of portions of the tasking on this contract when invoked in the task order statement of work:

5.7.1.1 Contractor requires access to information and equipment classified at the Confidential National Security Information (NSI) level in order to provide industrial support services within facilities that actively supports the Navy Nuclear Propulsion Program (NNPP).

5.7.1.2 All contractor personnel accessing classified information or classified material associated with the performance of work related to the resultant contract must be United States citizens, and shall have and maintain at a minimum Confidential security clearance.

5.7.1.3 The Contractor is responsible for completing all required government mandated training to maintain security and network access to government sites and IT systems, as necessary to support.

5.8 U-NNPI

5.8.1 Purpose The Contractor hereby agrees that when provided documents (specifications, drawings, etc.) that are marked as containing NOFORN sensitive information that must be controlled pursuant to Federal law, the information contained therein and generated as part of the inquiry shall be used only for the purpose stated in the contract and shall in no case be transmitted outside the company (unless such transmittals comply with the detailed guidance of the contract) or to any foreign national within the company. While in use, the documents shall be protected from unauthorized observation and shall be kept secure so as to preclude access by anyone not having a legitimate need to view them. The documents shall not be copied unless done in conformance with the detailed guidance of the contract. All the documents shall be promptly returned in their entirety, unless authorized for proper disposal or retention, following completion of the contract.

5.9.2 Specific Requirements for Protecting U-NNPI

a) Only U.S. citizens who have a need to know required to execute the contract shall be allowed access to U-NNPI.

b) When not in direct control of an authorized individual, U-NNPI must be secured in a locked container (e.g., file cabinet, desk, safe). Access to the container must be such that only authorized persons can access it, and compromise of the container would be obvious at sight. Containers should have no labels that indicate the contents. If removed from the site, U-NNPI must remain in the personal possession of the individual. At no time should U-NNPI be left unsecured (e.g., in a home or automobile, or unattended in a motel room or sent with baggage).

c) U-NNPI documents will have the word NOFORN at the top and bottom of each page. The cover sheet will have the warning statement shown below. Documents originated in the course of work that reproduce, expand or modify marked information shall be marked and controlled in the same way as the original. Media such as video tapes, disks, etc., must be marked and controlled similar to the markings on the original information.

d) U-NNPI may not be processed on networked computers with outside access unless approved by CNO (N00N). If desired, the company may submit a proposal for processing NNPI on company computer systems. Personally owned computing systems, such as personal computers, laptops, personal digital assistants, and other portable electronic devices are not authorized for processing NNPI. Exceptions require the specific approval of the cognizant DAA and CNO (N00N).

e) U-NNPI may be faxed within the continental United States and Hawaii provided there is an authorized individual waiting to receive the document and properly control it. U-NNPI may not be faxed to facilities outside the continental United States, including military installations, unless encrypted by means approved by CNO (N00N).

f) U-NNPI may be sent within the continental United States and Hawaii via first class mail in a single opaque envelope that has no markings indicating the nature of the contents.

g) Documents containing U-NNPI shall be disposed of as classified material.

h) Report any attempts to elicit U-NNPI by unauthorized persons to the appropriate security personnel.

i) Report any compromises of U-NNPI to the appropriate security personnel. This includes intentional or unintentional public release via such methods as theft, improper disposal (e.g., material not shredded, disks lost), placement on Web site, transmission via email, or violation of the information system containing U-NNPI.

j) The only approved storage for U-NNPI is CDMS NOFORN.

6.0 PLACE OF PERFORMANCE

6.1 The contractor's primary place of performance shall be at government facilities in Philadelphia, PA. It is estimated that 56% of the work will occur on-site at the NSWCPD facility and 44% of the work will occur off-site at the contractor facility.

If performance will be on a Government site, include the following as applicable:

6.1.1 Performance will occur at the following government sites: NSWCPD, Bath, ME Pascagoula, MS, Washington, DC, Groton, CT, Mechanicsburg, PA, Marinette, WI

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 27 per year.

The contractor shall be required to travel CONUS (any state in USA) and (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

Government-Furnished Property (GFP) means property in the possession of, or directly acquired by, the Government and subsequently furnished to the Contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes Contractor-Acquired Property (CAP).

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