DRAFT SOW_SPMS_RFI.docx

NSWCPD SOW-PWS Template Rev 47 Statement of Work (SOW) for New Acquisition, Ship’s Modernization and Sustainment Program Management 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 Department 20, which is responsible for machinery programs and platforms.

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 provides program management, engineering, technical, logistics, and financial support to U.S. Navy ship’s hull, mechanical, and electrical (HM&E) systems and equipment. This requirement is for NSWCPD Department 20, which is responsible for the management of machinery programs and platforms. The contractor shall provide programmatic support services to NSWCPD machinery programs and platforms. The contractor shall provide the personnel and facilities required to provide and support such services.

1.2 SCOPE OF WORK

The contractor shall provide programmatic support services to NSWCPD Department 20 (Machinery Programs and Platforms).

Areas to be supported include:

· Financial management

· Risk management

· Cyber security coordination

· Tracking status of various ongoing initiatives including:

· Regional Maintenance and Modernization Coordination Office check ins/check outs

· Ship change documents

· Material

· Travel plans

· Deliverables

· Action items

· System safety plans

· Shipboard testing

· Quality assurance issues

· Naval messages and advisories

· Engineering change proposals

· Health and status of program related contracts

· Schedule and dashboard development and maintenance

· Assisting with data calls

· Providing meeting support

This contract shall provide the personnel and facilities required to provide and support such services. Section 3.0 describes support services to be provided.

2.0 APPLICABLE DOCUMENTS

Note: The contractor shall reference and utilize the latest version available when performing tasks within this PWS.

2.1 NAVSEA Fleet Modernization Program (FMP) Management and Operations Manual

(NAVSEA SL720-AA-MAN-010/020)

2.2 NAVSEA Technical Specification 9090-600 www.dtic.mil

2.3 General Specification for Overhaul of Surface Ships GSO (NAVSEA S9AA0-AB-GOS-010)

2.4 Mandatory Procedures for Major Defense Acquisition Programs (MDAPS) and Major Automated Information Systems (MAIS) Acquisition Programs (DOD 5000.2-R)

2.5 DOD Interim Defense Acquisition Guidebook - dtd October 30, 2002

2.6 NAVSEAINST 5000.8, NAVAL SYSCOM Management Policy

2.7 MIL-STD-882, Department of Defense Stand Practice System Safety

2.8 S9800-AB-MAN-010, NAVSEA Engineering and Technical Authority Manual

2.9 NAVSEAINST 5100.12B, System Safety Engineering Policy

2.10 NAVSEAINST 5100.12M, System Safety Engineering Manual

2.11 NIST.SP.800-37, Rev. 2, Risk Management Framework for Information Systems and Organizations

These documents can be found at:

https://www.navsea.navy.mil/Resources/Instructions www.everyspec.com https://csrc.nist.gov/publications/sp800 https://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/manuals/milstds

These documents can be referenced at the websites provided or can be distributed upon request. The contractor shall reference and utilize the latest version of the documents above when performing tasks.

3.0. REQUIREMENTS

The contractor shall provide the following support services:

3.1 Program Management Support

3.1.1 Program Planning and Coordination: The Contractor shall perform program planning and coordination support among supporting Government and commercial activities. This includes technical review of documents; preparation of plans; preparation and coordination of program schedules and cost estimates; preparation and maintenance of automated databases and program master plans; preparation and maintenance of program histories and progress; and preparation and coordination of draft Memorandums of Understanding or Agreement and other documentation required to support actions such as management of personnel who support the transition of advanced technology initiatives for surface ship programs.

3.1.2 Program Reviews: The Contractor shall assist in scheduling and attending periodic program reviews conducted by program activities and conduct program reviews at the request of program sponsors.

3.1.3 Data Call Support: The contactor shall support program related data calls. The contractor shall work with the program manager and ISEAs to gather necessary data. The contractor shall collect, review, collate, and provide the data in the required format by the due date noted within the data call. Data calls subjects will vary and typically require a quick turnaround time.

3.1.4 Contract Tracking: The contractor shall track and document program related contract status and health. The contractor shall work with ISEAs to document all awarded contract actions for both labor and material contracts. The contractor shall track type of contract support being provided, contract number, contract award date, contract period of performance, etc. The contractor shall work with the ISEAs monthly to identify contract changes and changes in contract health.

3.1.5 Meeting Support, Action Item Tracking, and Briefs:

3.1.5.1 The contractor shall coordinate and host meetings, assign and take actions, record actions and meeting minutes. The contractor shall document and issue meetings minutes and meeting actions in the format required by the program. The contractor shall work with individuals assigned actions to gather action item status. This status will be recorded within the action item tracker. The contractor shall continue to gather and track action status through action closure.

3.1.5.2 The contractor shall assist with generating meeting briefs. Meeting briefs are typically generated in Microsoft Power Point but depending on the nature of the meeting/brief, the medium may vary. The contractor shall gather the necessary data and compile into the format required.

3.1.5.3 The contractor shall assist with ISEA briefs. The contractor shall assist with issuing data calls to the ISEAs requesting briefs. The contractor shall collect, review, and edit submitted briefs as needed to ensure data accuracy. The contractor shall compile submitted briefs and issue as required.

3.1.5.4 Contractor personnel shall provide in-person support to meetings held at NSWCPD, as needed.

3.2 Financial Management Support

3.2.1 Financial Tracking and Reporting: The contractor shall provide financial management support. The contractor shall work with the program manager, financial analyst, in service engineering agents (ISEAs), and program sponsor to track program financials including funds requested, funds allocated, funds received, and funds expended for current fiscal year as well as past fiscal years. Financials will be tracked at the task planning sheet (TPS) level down to the individual task level at the Navy Enterprise Resource Planning (ERP) network activity level. The contractor shall track emergency funding requests and track status of those requests. The contractor will identify and track funds available for recoup or reallocation. The contractor will track funding documents received. The contractor will track overall program funding roll ups which may include Operation and Maintenance, Navy (OMN) funds, Other Procurement, Navy (OPN) funds, Research, Development, Test, and Evaluation (RDT&E), Shipbuilding, Conversion Navy (SCN) funds, etc. The contractor will track both cost reimbursable and direct cite funds status. The contractor shall create and maintain burn down tables of expiring funds at the ISEA, project, or task level.

3.2.2 Technical Skills: The contractor shall have advanced knowledge of Microsoft Excel and Microsoft PowerBI and should know how to create and manage formulas, set up conditional formatting, create bar and line charts/graphs, burn down tables, create dynamic dashboards, and perform data imports and exports.

3.2.3 Financial Review Meetings: The contractor shall coordinate and host reoccurring financial review meetings for NSWCPD programs. The contractor shall provide financial status/updates for meetings and program reviews as required by the program. Program review financial updates shall typically be provided via Microsoft Power Point, Microsoft Excel, and Microsoft PowerBI. These financial status/updates shall be developed and delivered on a frequency and schedule identified by the NSWCPD program manager.

3.2.4 Task Planning Sheet (TPS) Support: The contractor shall assist with annual task planning sheet submission. The contractor shall collect, review, and process ISEA task statements and cost estimates. The contractor shall work with the program manager and ISEAs to resolve issues identified. The contractor shall create a cost estimate roll up summary sheet in Microsoft Excel to track and identify total program costs by total requirements, funding requirements plan by month, and funding spend plan by month. The contractor shall obtain a Task Information and Planning Center (TIPC) account (or whatever system NSWCPD is using for TPS support) to receive ISEA requirements. The contractor shall acquire a NAVSEA Enterprise Planning System (NEPS) account and shall enter tasking and financial details as required by the program. The contractor shall validate plans in NEPS and submit into workflow for program manager review and approval. The contractor shall obtain account access to other NSWCPD Program Management tools as identified by the government to complete financial and program support.

3.3 Risk Management Support

3.3.1 Risk Identification, Analysis, and Mitigation: The contractor shall provide risk management support. The contractor shall assist with risk identification, analysis, and assessment. The contactor shall work with NSWCPD ISEAs to collect, identify, document, and track program related risks in accordance with NAVSEAINST 5000.8, S9800-AB-MAN-101, MILS-STD-882, NAVSEAINST 5100.12B, and NAVSEAINST 5100.12M. The contract shall document programmatic risks using a 5x5 risk matrix and shall document safety risks using a 7x7 risk matrix. The contractor shall work with NSWCPD ISEAs to identify risk mitigation steps and shall track through risk mitigation. The contractor shall ensure mitigation dates are met and if not, work with the ISEAs to modify mitigation steps and/or dates are updated as needed. The contractor shall track all risks through risk mitigation/risk retirement. The contractor shall work with ISEAs to identify and document residual risks and shall assist with coordinating required approvals as needed in accordance with NAVSEAINST 5000.8.

3.4 Scheduling and Tracking Support

3.4.1 RMMCO Tracking: The contractor shall assist with tracking the status of ISEA check ins/check outs of Regional Maintenance and Modernization Coordination Office (RMMCO). The contractor shall acquire Navy Data Environment (NDE) account to review and download RMMCO check in/check out forms.

3.4.2 Schedule Development and Maintenance: The contractor shall provide scheduling support. The contractor shall work with NSWCPD ISEAs to collect, document/develop, review, and maintain modernization schedules. The contractor shall compile individual schedules into one master schedule. Schedules may start with funding requests and include design development through shipboard installation and RMMCO check out. The contractor shall work with ISEAs to gather and incorporate weekly schedule updates. If deadlines are missed, the contractor shall contact ISEAs for updates. Schedules are typically maintained in Microsoft Excel or Microsoft Project. The contractor shall have extensive working knowledge of both Microsoft Project and Microsoft Excel. Schedules may track baseline dates as well as revised and actual dates, as well as percent completion data, individuals responsible for tasking, etc. The contractor must understand how to set up lead and lag tasking in Microsoft Project.

3.4.3 Material Tracking: The contractor shall assist with the tracking of material for surface ship programs.

3.4.3.1 The contractor shall work with the ISEAs to ensure all necessary material has been ordered and will be received by the required date for ship events. If material is ordered late or will be delivered late, the contractor work shall work with the ISEA to document reason(s) for delays.

3.4.3.2 The contractor shall review NSWCPD material inventory lists. These lists are issued quarterly. The contractor shall work with ISEAs to determine who owns what material and applicable installation (hull and SCD). The contractor shall identify material that has no owner and material that is not slated for shipboard installation. The contractor shall work with the program manager for disposition of such material. The contractor will generate material movement forms to disposition material as deemed necessary by the program manager.

3.4.3.3 The contractor shall track program related DD FORM 1149s (Requisition and Invoice/Shipping Document) to ensure program related DD FORM 1149’s have been issued to track transfer of material from NSWCPD or contractor to the ship.

3.4.4 Travel Tracking: The contractor shall assist with the tracking of ISEA travel. This is needed to know who will be on which ship and when (ISEA, hull, dates visited).

3.4.5 Deliverable Tracking: The contractor shall assist with the tracking of program related deliverables. The contractor shall survey ISEAs on a reoccurring basis to gather status of program related deliverables. The contractor shall record status and generate/issue metrics.

3.5 Engineering and Configuration Management Support

3.5.1 Configuration Management: The Contractor shall provide technical and engineering services in support of configuration management, provide technical support to identify the functional and physical characteristics of an item during its life cycle, controlling changes to those characteristics and provide information on the status of change actions.

3.5.2 Engineering Change Proposal (ECP) Management: The Contractor shall manage, distribute and track engineering change proposals (ECPs). ECPs will be compiled into a repository, such as SharePoint. As ECPs are developed and transformed into ship change documents (SCD), the contractor shall track and report SCD status.

3.5.3 Engineering Change Proposal (ECP) Development: The Contractor shall provide support for Engineering Change Proposal development, changes and/or improvements resulting from directed changes in basic requirements or from discrepancies in specifications or contract design drawings that are identified during the detail design development.

3.5.4 Ship Change Document (SCD) Tracking: The contractor shall assist with ship change document (SCD) tracking. The contractor shall review program fielding plans and work with ISEAs to identify upcoming and future surface ship efforts. The contract shall track SCD title, number, and phase status. The contractor shall acquire an NDE account to review and download SCDs.

3.5.5 Advisory/Naval Message Tracking: The contractor shall track HM&E equipment related class and ISEA advisories and Naval messages for surface ship programs. The contractor shall assist in issuing, updating, and closing advisories. The contractor shall provide a tracking matrix detailing the status of all advisories.

3.5.6 Engineering HM&E Support: The Contractor shall provide ship hull, mechanical, electrical and control systems engineering support of US naval vessels in support of new acquisition, ship life extension, sustainment, modernization, and In-service Engineering.

3.5.7 Engineering Program Support: The contractor shall provide engineering support services for programs, projects and/or special studies being conducted. Examples may include ship design efforts; operational/performance capabilities evaluations, hazard assessments; equipment or ship survivability studies; and risk analyses efforts for HM&E systems, subsystems and equipment.

3.5.8 Design Support; The Contractor shall provide program management and engineering support for design efforts associated with program HM&E systems. Support functions shall include the following:

3.5.8.1 The Contractor shall provide technical support for design agent oversight. Review System Data Requirements Lists (SDRLs), answer design agent questions, perform technical information research, financial support and provide information to design agents regarding system requirements during the detailed design process.

3.5.8.2 The Contractor shall provide on-site support to the Acquisition Ship Design Manager (SDM) team at ship design, acquisition and program locations. This shall include daily interfaces with Acquisition SDM, Machinery Technical Warrant Holder, and NSWCPD ISEA personnel to resolve ongoing and emergent ship design issues, coordination of the review of shipbuilder test procedures, technical waivers, proposed ship changes, and alterations as directed by the SDM, SDM related financial planning, execution and management, and preparation of construction production status reports.

3.6 Test and Evaluation Support

3.6.1 Shipboard Testing Tracking: The contractor shall provide testing support. The contractor shall coordinate and track the status of test plan development, test procedure development, and land-based software development activities. The contractor shall coordinate ship yard test support, track shipboard problem improvement reports (SPIRs), and generate testing metrics.

3.6.2 General Test and Evaluation: The Contractor shall provide test and evaluation support for programs, projects and/or special studies being conducted, such as Live Fire Test and Evaluation (LFT&E), assessments or analyses; Total Ship Survivability Trials (TSSTs); Full Ship Shock Trials (FSSTs); shock testing and trials; inspections; and testing efforts. In support of these and other program/projects/studies provide test and evaluation support using approved processes that focus on validating requirements and developing impartial test and evaluation products, including: writing supporting documentation, such as test plans and procedures, test agendas, evaluation reports, operation and safety instructions and other documentation as required; conducting scheduled testing scenarios with Government personnel observing; conducting field trials to validate the efficacy of the developed hardware, systems and techniques; participating in testing; and writing quantitative, qualitative and gap analyses.

3.6.3 Technical Review and Assessment: The Contractor shall provide technical and engineering support services to Production and Test Directors to include: reviewing evaluation test and trials documentation; tracking the disposition/correction/resolution of Trial Cards; conducting technical reviews of specifications, test procedures, schedules, and other test documentation; and providing recommendations/assessments.

3.6.4 Software Test and Evaluation: The Contractor shall provide design and review of software requirements specifications from framework items to capability specific functions and participate as an active member of the Configuration Control Review Board to adjudicate all processes, procedures, test review and acceptance.

3.6.5 Laboratory and Shipboard T&E: The Contractor shall provide laboratory and shipboard Test & Evaluation for component design, component manufacturing, equipment operation, and system functionality.

3.6.6 Trials Support: The Contractor shall support pier side dock trial, and at-sea trials for applicable systems and equipment.

3.7 Integrated Logistics Support (ILS)

3.7.1 ILS Tracking and Coordination: The contractor shall provide integrated logistics support (ILS). The contractor shall assist with tracking the status of various program related ILS products and services. The contractor shall provide ILS integration and coordination support for availabilities to ensure that all required ILS products associated with the HM&E equipment alterations are properly updated, developed and issued in accordance with NAVSEA milestones

3.7.2 ILS Documentation and Support:

3.7.2.1 The Contractor shall provide evaluation, assessment and recommendations for Integrated Logistics Support plans and products for completeness and adherence to specifications for systems and equipment as directed from the applicable Program office. ILS elements may include Supply Support, Technical Data and Publications, Facilities, Maintenance Planning, and Personnel and Training.

3.7.2.2 The Contractor shall develop Integrated Logistics Support certifications and checklists to support new and/or modified systems and equipment as directed from the applicable Program office.

3.8 Quality Assurance and Documentation Support

3.8.1 Quality Assurance Tracking: The contractor shall track program related quality activities and issues. Examples of quality activities include quality assurance (QA) workbook status and system engineering process (SEP) surveillance reports, and SEP audit events. Examples of QA issues include tracking level 1, 2, and 3 SPIRs, contractor-issued cure notices, and contractor-issued corrective action requests. The contractor shall compile QA issues and activities and report out metrics.

3.8.2 Share Drive/SharePoint Management: Share Drives/SharePoint Usage. The contractor shall use program related share drives and/or SharePoint as required per the program manager. The contractor shall store required data/files on share drives and/or SharePoint as directed by the program manager in order to share program related data/files with entire program team and sponsors. The contractor shall set up new program related folders as necessary. The contractor shall maintain share drive/SharePoint folders in an organized manner.

3.8.3 System Safety Plan (SSP) Tracking: System Safety Plan Tracking: The contractor shall assist with tracking program related system safety plans (SSPs). As part of the NSWCPD system engineering process, most programs and systems are required to have SSPs in place. The contractor shall work with the ISEAs to identify all program systems required to have a SSP. The contractor shall acquire a copy of each ISEA’s SSP.

3.8.4 Collaboration Tool Support: The contractor shall provide administrative support to content in various government collaboration and content sharing tools such as SharePoint sites, wiki pages, Fusion, Jira, Confluence, Sailor to Engineer website, TIPC, Microsoft PowerBI, etc. Support includes posting, updating, and organizing site content.

3.8.5 Quality Assurance (QA) Development:

3.8.5.1 The Contractor shall conduct and execute all QA activities in accordance with NSWCPD's Standard Software based Systems Process (SSP).

3.8.5.2 The Contractor shall conduct periodic and milestone software QA audits and prepare audit results for distribution.

3.8.5.3 The Contractor shall conduct software-based system quality assurance audits.

3.8.5.4 The Contractor shall design and develop software processes and procedures related to quality assurance in the organization's standard process.

3.9 Post Delivery and In-Service Technical Support

3.9.1 Problem Resolution: The Contractor shall provide technical assistance for resolution of system and equipment level problems and failures in support of Post Delivery Availabilities, Ship Surveys and In-Service Technical Support.

3.9.2 Ship Checks and Assessments: The Contractor shall provide detailed ship checks for reported problems and provide recommendations and assessments for problem resolution.

3.9.3 On-Site Technical Support: The Contractor shall provide On-Site technical support for system and equipment problem resolution in support of new acquisition development programs and current platforms.

3.10 Reserved

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

N/A

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

N/A

3.5 Parts Obsolescence

N/A

4.0 DATA REQUIREMENTS

· Contract Status Report (CDRL A001)

· Travel Report (CDRL A002)

· Contractor’s Personnel Roster (CDRL A003)

· Other Direct Costs Report (CDRL A004)

· Government Furnished Material (GFM) by National Stock Number (CDRL A005)

· Government Property Inventory Report (CDRL A006)

· Government Property Inventory Report (Final) (CDRL A007)

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 DD254 REQUIREMENT. 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 90 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 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.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

N/A

5.8 U-NNPI

N/A

6.0 PLACE OF PERFORMANCE

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 per year can be seen in the below table. 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

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. Accountability for Government Property under this contract/order shall be managed in accordance with FAR Part 45, DFARS Part 245, and the Government Property clauses included within the Solicitation and Contract.

GFP is required for completion of task(s) under this SOW. See GFP attachment for detailed information. All GFP identified in the GFP attachment will be provided within 4 weeks of contract award.

The Contractor shall notify the COR via email, with the TPOC and PCO Cc’d, of any GFP received in error or not on an approved GFP attachment in EDA within seven (7) business days of physical receipt of the property.

8.1 Reporting Requirements.

The Contractor shall follow all reporting requirements to accurately account for GFP.

8.1.1 PIEE Shipment Reporting.

Contractor Receipt Reporting: Clause 252.245-7005 “Management and Reporting of Government Property” requires the Contractor to report receipt of all GFP using the PIEE GFP Module, regardless of whether the Government has submitted a PIEE electronic shipment.

Contractor Shipment Reporting: Clause 52.245-1 “Government Property” (including Alternates 1 & 2) requires the Contractor to report to the Government when GFP is returned. Clause 252.245-7005 requires this notification to be an electronic shipment through the PIEE GFP Module.

A DD Form 1149 shall accompany all government property shipped between the Government and the Contractor using a third party, such as UPS, FedEx, or USPS. The DD 1149 does not take the place of the PIEE shipment. It is a requirement in addition to the PIEE shipment

8.1.2 Inventory Reporting.

The Contractor shall submit a Government Property Inventory Report (Periodic) in accordance with CDRL XXXX. The CDRL identifies all reporting requirements. The Contractor shall continue to submit an inventory report IAW the CDRL even if all GFP has been returned to the Government. The Contractor shall also submit a Government Property Inventory Report (Final) in accordance with CDRL XXXX. When the Contractor has never received any GFP, the Contractor shall annually certify to the Procuring Contracting Officer (PCO) via email, with the Contracting Officer’s Representative (COR) and Technical Point of Contact (TPOC) Cc’d, that it does not have any GFP.

The Contractor shall also provide support within a reasonable timeframe after any Government request (to include by DoD support agencies such as DCMA) to support any Government audit in which GFP, or its related documentation, is requested as part of normal audit processes.

8.1.3 Lost, Damaged or Stolen GFP Reporting.

Clause 52.245-1 (including Alternates 1& 2) requires the Contractor to investigate and report to the Government (to the COR via email, with the TPOC and PCO Cc’d) all incidents of lost or damaged Government property as soon as the discovery is made. Clause 252.245-7005 requires the Contractor to report loss of Government property by using the Property Loss functionality within the PIEE GFP Module. The Contractor shall support the Government’s process to assign liability and document the loss in support of lost, damaged or stolen GFP.

8.1.4 Excess Property Reporting.

In accordance with Clause 52.245-1 paragraph (f)(viii)(A), the Contractor shall promptly disclose to the COR via email, with the TPOC and PCO Cc’d, Government property in its…