SOW RR PIP.docx

Statement of Work (SOW) Product Improvement Program (PIP)

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 Division 20, 42, and 44, which is responsible for Propulsion Systems, Power Systems, and Program, Platform and Financial Management.

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

(i) Confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) Countermand any communication regarded as a violation,

(iii) Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or

(iv) In the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor.

1.1 BACKGROUND

The Propulsion and Power Systems Departments (42 and 44) of the Naval Surface Warfare Center, Philadelphia Division (NSWCPD), provide assistance and depot engineering support for Marine Gas Turbine Engines (MGTs) and their packages.

This contract is in support of the Product Improvement Program (PIP). The PIP is an engineering support program that maintains and improves the operational readiness, safety, reliability, maintainability, and operating and support costs to support the U.S. Navy.

Historically, the MT30 Marine Gas turbine had a separate PIP working group contract. NSWCPD’s intend is to consolidate contracts and incorporate all MT30 engine needs into this PIP contract. To support these requirements, the U.S. Navy requires a service support contract with the original equipment manufacturer (OEM), Rolls-Royce Corporation, to ensure updated technical documentation, availability of spares, management of obsolescence and related configuration changes, technical support services, fleet support services, software support, etc., at both a program and waterfront level.

1.2 SCOPE OF WORK

The Product Improvement Program (PIP) is an engineering support program that provides engineering man-hours and services as required to maintain and improve the operational readiness, safety, reliability, maintainability, as well as operating and support costs for the Rolls- Royce Corporation (RRC) products defined in Attachment 1 (acronyms listed in Attachment 2) used by the U.S. Navy. The contractor shall provide all Maintainability and Availability (M&A) and Technical Data programs for RRC products. These services shall be provided at the contractor’s facilities and other locations as designated by the Government.

The Contractor shall provide lifecycle, modernization and in-service support for the Rolls-Royce Marine Gas Turbine Engines and their related shipboard auxiliary systems on all applications used throughout the U.S. Navy. The support required will involve technical, logistics, training, administrative and program management efforts related to Rolls Royce Marine Gas turbine lifecycle and in-service concerns. This functional service support shall provide the Naval Surface Warfare Center Philadelphia Division (NSWCPD) support for technical documentation, obsolescence management, technical assistance, etc. End users of the products of these functional areas under a service agreement could include the SEA 05Z Marine Gas Turbine Technical Warrant Holder (TWH), Marine Gas Turbine NSWCPD ISEAs, the PMS 505 LCS Fleet Introduction and Sustainment Program Office/SEA 21, and PMS 443 Surface Ship Sustainment Office to help them support the fleet.

The PIP is necessary to maintain adequate and effective operational readiness, safety, and mission effectiveness of RRC systems. Virtually all mechanical equipment needs continuing engineering support to solve operational problems. Military systems require a higher level of engineering support than commercial equivalent systems. The military systems normally push the leading edge of technology and are subjected to ever changing demanding environments and mission cycles. New problems are continually experienced after approval for operational use. The new problems are a result of greater exposure, changes in mission, changes in system weight or configuration, variations in manufacture or repair, aging of the hardware, maintenance concept changes, critical materials availability, and changing component coating and fuel compounds. (i.e.: Bio-Fuel technologies and similar advances). These changes in engine usage can be dramatic and can have a dramatic impact on safety, readiness, and mission effectiveness. Therefore, a program (PIP) to address that impact is essential to maintain these systems at full operational capability.

2.0 APPLICABLE DOCUMENTS

2.1 NAVSEA Standard Items

2.2. ASQ/ANSI/ISO 9001:2015 Quality Management Systems - Requirements The Contractor shall reference and utilize the latest version available when performing tasks within this PWS.

3.0. REQUIREMENTS

3.1 The Contractor shall provide the necessary supplies, services, materials, and facilities to conduct the RR PIP program and to perform the engineering support and required testing defined in each task. New technologies and system designs are developed which will accomplish one or more of the following objectives: resolve service-revealed deficiencies; reduce maintenance costs; improve propulsion equipment reliability/maintainability; and, improve system efficiency and performance. Major functions the contractor shall perform include:

3.2 Investigating Engineering

3.2.1 The contractor shall conduct engineering investigations, using contractor personnel, material, and facilities, unless specific material is provided by the government. The contractor shall perform failure analysis, data analysis, modeling, and simulations. The investigations shall relate to the RRC products including, but not limited to: PIP Program for installation, operation, maintenance, operations limits, training requirements, and documentation. A report of the results of each investigation, including conclusions and recommendations, shall be prepared. Each task shall be performed in accordance with the Program Management requirements.

3.3 Product Improvements

3.3.1 The contractor shall provide materials, engineering personnel, and the manufacturing and testing facilities to design parts, components, or systems to meet program objectives. The contractor shall validate the designs by bench tests, propulsion equipment tests, and support of fleet evaluations. The contractor shall perform technical manual validation, redlines, and improvements. Engineering Change Proposals (ECP) and associated technical data shall be developed and submitted. The contractor shall provide engineering and technical expertise in support of and to implement hardening of Rolls-Royce products with respect to Risk Management Framework (RMF) package POAMs (Plan of Action and Milestones) on control hardware and software. Evaluating security of Rolls-Royce product systems under development as needed. The contractor shall implement security requirements through secure design and secure implementation. Specific components or systems which require such design effort shall be assigned by Naval Surface Warfare Center Philadelphia Division (NSWCPD) in accordance with the Program Management requirements.

3.4 Support of Government Testing

3.4.1 The contractor shall provide the personnel to monitor and provide assistance and evaluate tests of design improvements being tested on U.S. Naval craft, or Government equipment as may be required by these tests. Test support services shall be provided in accordance with the Program Management requirements. In addition, the maintenance and repair of any government owned test equipment or special tooling at the contractor’s facility is also covered under this PIP contract

3.5 PIP Review

3.5.1 The contractor shall conduct PIP reviews as scheduled, between the contractor and NSWCPD. The reviews will include, but not be limited to keeping government personnel abreast of progress in the assigned tasks, reviewing priorities, discussing and resolving technical matters (such as approaches to solutions of problems or adequacy of existing designs), and checking on funds expended and/or available for new work. Format of the technical reviews will be as mutually agreed upon by the contractor and NSWCPD.

3.6 Fleet and Depot Support

3.6.1 The contractor shall provide technical support directly to U.S. Navy crafts or activities when required under a task order. The assistance shall encompass background research, Fleet, craft, ship, and depot support, on-site investigations, in-service engineering, maintainability, reliability, maintenance planning, service repair limits, data analysis, modeling, and simulations or maintenance processes at all echelons of the engine programs; this also includes any direct fleet support and evaluations required, including travel necessitated in support of any delivery order.

3.7 Program Management

3.7.1 The PIP shall be performed in accordance with the following:

3.7.1.1 Task Orders: Task Orders will be issued that will include detailed instructions of the task to be performed.

3.7.1.1.1 At a minimum the contract shall provide Program Management Technical Oversight, Contract/ Subcontract Management, Financial Management, and Data Management for tasks under this SOW.

3.7.1.2 Priorities: Each task order will indicate the priority associated with the task to be performed. The order in which the Contractor will conduct work shall be consistent with the priority classification assigned to each task order. Classifications to be used are listed below in decreasing order of urgency:

3.7.1.2.1 EMERGENCY. Safety items only – all possible resources should be directed to resolve these tasks.

3.7.1.2.2 URGENT. Potential safety items which do not necessitate emergency classification – items which have serious impact on operations.

3.7.1.2.3 PRIORITY. Items which prove of considerable value in reliability, maintainability, availability, economy or performance – to be accomplished on an expeditious and continuing basis.

3.7.1.2.4 ROUTINE. Tasks of a routine nature.

3.7.1.3 Meetings: Interim PIP review meetings will be held to discuss specific engineering problems which need definition and guidance. These meetings will be held on an “as needed” basis as approved by both the contractor and the government, but not less than semi-annually.

3.8 Technical Support

3.8.1 Provide the U.S. Navy technical support services in support of the repair, modernization, maintenance, systems analysis of the marine gas turbine engines by the U.S. Navy. This would include technical support for the ISEA for emergent fleet events that impact operation, repair and routine maintenance on an on-demand basis.

3.8.1.1 Source of Support (SOS) matrix: The contractor shall maintain the Source of Support (SOS) matrix. This matrix identifies the OEMs, Navy support activities, private industry maintenance providers, local maintenance providers to be leveraged to support technical reach back, maintenance and supply activities for all RR gas turbine engines.

3.8.2 Technical Documentation: Provide NSWCPD access, upon request, to technical manuals, drawings, schematics, circuit drawings and other technical documentation for the gas turbine and auxiliary systems for sustainment, troubleshooting, repair, maintenance, and analysis, etc. The documentation should provide detail to the Lowest Replaceable Unit (LRU) determined by the lowest replaceable internal component, not by the repair strategy or by the software input. Depot level technical data sufficient for ISEA and TWH to understand and determine the requirements for repairs conducted in a depot facility similar to the 501K Technical Repair Standard (TRS). All documentation provided to the ISEA will be for government use only.

3.8.2.1 Technical Documentation assistance and update: In response to a request from NSWCPD as a LOE under this contract, the contractor will provide clarification to existing Technical Manuals, DWGs, software programs, etc. When such clarification indicates a requirement for update of technical documentation, the contractor will submit a recommendation to NSWCPD, via the quarterly report for development of the appropriate task order under this contract. In support of this task, the contractor shall gain access to and use the Navy Data Environment Navy Modernization (NDE-NM) for update of documentation. The contractor shall update technical manuals based on government feedback reports, OEM updates, or other identified deficiencies. Documentation shall be updated in accordance with CDRL A0007. Update to technical manuals due to the incorporation of approved configuration changes will be funded via a separate Sustainment CLIN, PCW, or Technical Instruction (TI), etc.

3.8.2.2 Technical Data Rights: The contractor will provide the appropriate technical data rights to NSWCPD for use in addressing FTAs, clarification of technical documentation, providing technical data to NSWCPD, RMCs or LCSRONs, software, etc. These data rights provided to NSWCPD will retain all intellectual property rights and will retain all appropriate proprietary markings. Under no circumstance will they be used for competitive sourcing, etc. When required for use by a competitor, The contractor will initiate the appropriate documentation with NSWCPD and if required, necessary licensing requirements.

3.8.2.3 Maintenance documentation revision and update: Maintain and update maintenance concepts, tasks and criteria for all levels of maintenance during the equipment/system life cycle. This includes recommended changes to the Planned Maintenance System (PMS), Class Maintenance Plan (CMP) and other maintenance documentation. Update to maintenance documentation due to the incorporation of approved changes will be funded via a separate Sustainment CLIN, PCW, or Technical Instruction (TI), etc.

3.8.2.4 Modernization documentation: In support of changes identified via the DMSMS process, TM review, fleet feedback reports, Field Service Reports, and other documentation, the contractor will develop Ship Change Documents (SCDs) to support Form, Fit Function (FFF) replacement and/or system modernization. SCDs and other modernization updates due to approved changes will be funded via a separate Sustainment CLIN, PCW, or Technical Instruction (TI), etc.

3.9 Provisioning Support:

3.9.1 Provide the U.S. Navy provisioning updates to update or correct Provisioning Technical Documentation (PTD) and Engineering Data for Provisioning (EDFP) for new or existing RR components/systems, changes due to obsolescence, modernization, parts demand, maintenance frequency or levels, sources of supply to include range and depth(quantity) of end items, assemblies, subassemblies, components, spare and repair parts, and support and test equipment required to operate and maintain an end item. Provisioning updates due to the incorporation of approved changes will be funded via a separate Sustainment CLIN, PCW, or Technical Instruction (TI), etc.

3.9.2 Provisioning updates: Contractor will submit PTD and EDFP IAW DoD Provisioning, Allowance and Fitting Out Support (PAFOS) manual, Chapter 4, Appendix A-K. A Failure Mode Effects and Criticality Analysis (FMECA) would also be required to provide for accurate provisioning support. Failure data would include the contractor’s collected data along with GFI data such as the NSWC Corona Material Readiness Database.

3.9.2.1 PTD consists of, but is not limited to, the technical breakdown of an end item, assembly, subassembly, or component to the lowest piece part level and the entry of that information, including but not limited to, the technical characteristics, installed quantities, and shipboard system(s) and location(s) into formatted provisioning lists.

3.9.2.2 Engineering Data for Provisioning (EDFP): Approved EDFP is required for all non-standard systems or equipment for which PTD is being acquired. It is the technical data that provides definitive identification of dimensional, material, mechanical, electrical, or other characteristics adequate for provisioning of the support items of the end article(s) on contract. EDFP consists of but is not limited to data such as specifications, standards, drawings, photographs, sketches and descriptions, and the necessary assembly and general arrangement drawings, schematics, drawings, schematic diagrams, wiring and cable diagrams, etc., or what is sometimes referred to as form, fit and function. (DI-ILSS-81289).

3.9.3 Allowance Parts List (APL) review: Contractor shall ensure that all PTD and EDFP meets all appropriate technical data requirements to ensure a complete and effective APL with recommended improvements. PTD and EDFP prepared for individual equipment or component should include technical characteristics and list the piece parts necessary for Organizational (O) and Intermediate (I) -Level support of that equipment. This includes repair and replacement parts and provides allowances for those parts required to be in the ship’s inventory for preventive maintenance as well as casualty repairs.

3.9.4 PTD preparation and submission: The contractor shall conduct provisioning functions for Form, Fit Function changes, including PTD preparation and submission via Interactive Computer Aided Provisioning System (ICAPS) compatible format when updated documentation is submitted by the contractor or its subcontractors for previously submitted Provisioning Data. Documentation shall be updated in accordance with CDRL A007.

3.10 Obsolescence Management:

3.10.1 Provide the U.S. Navy Diminishing Manufacturing Sources and Material Shortages (DMSMS) for all RRC marine gas turbine systems and components to include appropriate, joint mitigation actions by the contractor and the U.S. Navy.

3.10.2 Contractor shall monitor all interim unique MT30 LRU configurations for DMSMS.

3.10.2.1 Identification of known or suspected DMSMS issues upon discovery and all known information related to the issues.

3.10.2.2 Conducting technical, cost, and schedule assessments for various best solutions including, but not limited to, end of life buys, hardware and software changes, alternative sources of supply, alternative upper or lower assemblies, etc.

3.10.2.3 Confirmation of the feasibility of implementing the selected solution.

3.10.2.4 Cross program data integration, analysis, and assessment.

3.10.2.5 An obsolescence report, which provides overall system assessment and DMSMS issue identification and resolution status, will be provided quarterly.

3.10.3 The contractor shall submit a DMSMS resolution plan with the appropriate options and costs to resolve the obsolescence. When NSWCPD approves a resolution plan, the contractor shall submit an Engineering Change Proposal (ECP), and the appropriate PTD and EDFP, as defined in 3.9. Updates of technical documentation due to obsolescence will be funded via a separate Sustainment CLIN, PCW, or Technical Instruction (TI), etc.

3.11 Configuration Management (CM): Evaluate and provide inputs to the configuration management program to ensure control of the hardware, technical documentation and computer program configuration baselines.

3.11.1 CM changes, updates and documentation: Provide the U.S Navy all gas turbine configuration changes that would be reflected in CDMD-OA, TMs, Provisioning/APLs, Spares, Software, and other technical documentation and products. This includes government notification, per NAVSEAINST 4442.1C and documentation contained in DD Form 1692, of Configuration Change Notifications; as an example, a Class I change. It would also include all past configuration changes from the original engine baseline to present, along with all known future changes. All configuration updates would be in a format usable by the U.S. Navy and compatible with Navy databases.

3.12 Control Systems Support: Provide the U.S. Navy the processes, programs, and special tooling required to reload firmware and software on every ship in the fleet, as well as change IP addresses for all IP-mapped components, and circuit drawings for the following items to facilitate Intermediate Level repair by USN personnel: EIO, EMU, EEC, HMI, PCS, PTM. This includes access to the as-delivered software for each ship for each of the previously stated items with the information to calibrate or alter the equipment to fit in every MT30 engine position in the U.S. Navy. In addition, provide training for Intermediate Level and NAVSEA personnel.

3.13 Fleet Support services: As required by NSWCPD, RRC will provide services to review, collect, analyze, develop, and test changes identified via the above tasks. This may include the following:

3.13.1 Test Support: Support of shipboard proofing of equipment alterations for evaluation of engineering design and logistic support items. Review and recommend improvements to test procedures, test points, general and special purpose test equipment, tools, jigs, and fixtures; review adequacy of test equipment stowage; develop and propose alterations to improve stowage.

3.13.2 Waterfront Engineering Support: Provide fleet engineering assistance via NSWCPD as related to all of the above functions outlined in this SOW. This could include on-site engineering investigations to evaluate reliability, maintainability, performance availability and logistics support of the combat system/equipment.

3.13.3 Training Improvement. Assist NSWCPD in monitoring the training conducted by the Navy's training agency, including providing personnel to assist in conducting systematic audits of training activities, coordination of maintenance feedback with training inputs, and planning and review of training identification systems.

3.13.4 Navy and Commercial Repair Facilities: Develop recommendations NSWCPD for the establishment or improvement of facilities, documentation, support equipment, training and manningg, as required, to assure continuing fleet support.

3.13.5 Program reviews, conferences, meetings, etc.: As required by NSWCPD, the contractor shall provide representation in planning conferences, program reviews, and design reviews with the Type Commander, LCSRONs, RMCs, or other governmental agencies requesting support. This participation will facilitate feedback and support execution planning and status reporting related to system maintenance, failures, trends, material requirements, etc.

3.14 Metrics / System measurement: Provide for the measurement of the operational and maintenance performance of equipment/systems and logistic support items in order to determine equipment/systems design and maintenance problems.

3.14.1 Measures of Effectiveness: Metrics to measure the effectiveness of sustainment are required to ensure focus on fleet requirements, costs, etc. These can include jointly developed measurements on FTA resolution, DMSMS cases resolved, ECPs developed, TM corrections/updates, EDFP submissions, etc.

3.15 Material and Other Support: As required by NSWCPD, RRC will provide for material support for tooling, support equipment, re-design efforts, prototypes, and spares. In addition, as required by NSWCPD, RRC will engage other OEMs or sub-suppliers to improve support of existing gas turbine package equipment and/or support existing fleet requirements.

3.2 Reserved

3.3 Manufacturing Phase-Out or Discontinuation of Production, Diminishing Sources, and Obsolete Materials or Components (Note: Insert in Section C of all requirements (supply or service))

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

3.4 Diminishing Manufacturing Sources and Material Shortages Management (DMSMS) Contract Requirements (Include if applicable - Please refer to Appendix C. Examples of DMSMS Management Contract Language The Contractor shall develop and submit as part of its proposal (with an advance copy supplied to the Government at time of cost estimate submission), an Obsolescence and DMSMS Management Plan for managing the loss, or impending loss, of manufacturers or suppliers of parts and/or material required for performance of this contract.

At a minimum, the plan shall address the following:

· Means and approach for providing the Government with information regarding obsolescence and DMSMS issues

· Planned resolution of current obsolescence and DMSMS issues

· Parts list screening

· Parts list monitoring

· Receiving, processing and disseminating Government-Industry Data Exchange Program (GIDEP) DMSMS Notices

· Receiving, processing and disseminating Defense Logistics Agency (DLA) DMSMS Alerts

· Communication with and availability of information to the Government

· Means and approach for establishing obsolescence and DMSMS solutions

· Plan for conducting DMSMS predictions.

3.5 Parts Obsolescence (Insert in all requirements where the contractor's obsolescence program will be evaluated in the Solicitation (supply or service)

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

4.0 DATA REQUIREMENTS

The PIP deliverables take the form of technical data necessary to implement solutions to fleet problems, or to prevent the occurrence of potential problems. Technical data to be delivered will include configuration status account reports, design change notices, scientific and technical reports, progress reports, status reports, management reports, Request for Deviation, Request for Waiver, list of items delivered during contract performance, Engineering Change Proposals (ECPs), Manufacturing Drawings, Maintenance Instructions, Rework/Repair Procedures, and Technical Reports.

Applicable contract data requirements:

4.1 CDRL A001, Scientific and Technical Reports

4.1.1 This report shall be utilized in response to request for tasking from the USN. The Final Report shall be delivered 30 days after inclusion of government comments. If government does not provide comments within 30 days of submitting Preliminary Report, contractor shall consider Preliminary Report acceptable and is not required to re-submit report.

4.2 CDRL A002. Contractors Progress, Status and Management Reports

4.2.1 The contractor shall provide monthly status reports on each task order. The report should include funds and labor hours expended for the month and fiscal year to date, as well as estimates of projected expenditures of funds and labor hours for future months.

4.3 CDRL A003, Configuration Status Accounting (CSA) Info

4.3.1 The contractor shall provide CSA as appropriate within the Marine Gas Turbine Information System (MGTIS) and Weblog for assigned systems including, but not limited to MGT Engines, and associated Propulsion Ancillary systems and confirmed data entered into same on the as-built shipped serialization records to NSWCPD. The Contractor shall obtain and maintain a current Department of Defense (DOD) Public Key Infrastructure (PKI) certificate or current DOD Common Access Card (CAC).

4.4 CDRL A004, Engineering Change Proposals

4.4.1 Engineering Change Proposals shall be prepared in Contractor’s format and shall contain originator of request, title of change, description of proposed change, need for change, effect on delivery schedule, effected documentation, and cost to government with explanation or cost savings with offer of consideration to the government.

4.5 CDRL A005, List of Items Delivered During the Term of a Contract

4.5.1 This DID shall be required for each shipment of serial numbered components to the Navy Supply System. List can be submitted in Contractor’s format.

4.5.2 Engineering Evaluations/Reviews. The contractor shall perform engineering reviews, evaluations, investigations, and surveys. Studies may be performed at contractor facilities, governments facilities (i.e.: Land Based Engineering Site located at NSWCPD), or other non-government facilities as required. The studies shall provide information to improve, revise and/or develop new maintenance procedures, plans for future engineering and logistic efforts and define or refine inspection criteria. Each task shall be performed in accordance with the Program Management requirements.

4.6 CDRL A006, Request for Waiver and Deviation

4.6.1 Requests for Deviation shall be prepared in Contractor’s format and shall contain originator of request, identify units/components are affected, title of deviation, description of proposed deviation, need for deviation, effected documentation and extent of revision, cost to government with explanation or cost savings with offer of consideration to the government.

4.7 CDRL A007, Product Drawings and Associated Lists

4.7.1 The contractor shall develop/revise/update drawings for the Rolls-Royce propulsion equipment engines and related special support equipment and provide in electronic format (pdf, tif or jpg). Each task shall be performed in accordance with the Program Management requirements.

4.8 CDRL A008, Design Change Notices

4.8.1 This DID shall be required for Class I and II Engineering changes. The contractor shall provide copies of all newly issued and/or revised Class I and II ECPs, Deviations and Waivers, Material Review Board (MRB) actions, Design Change Notices, Service Bulletins and Compliance Reports and Records, and Parts Lists and Spare Parts Application Data Lists as revisions to these documents occur.

4.9 CDRL A009, Travel Report

4.10 CDRL A010, Quality Management System (QMS)

4.10.1 CDRL A010 shall include documentation sufficient to satisfy all aspects of Data Item Description (DID) DI-MGMT-82184. The CDRL shall be delivered in electronic format.

4.11 CDRL A011, Contractor Personnel Roster

4.11.1 The CDRL shall be delivered electronically, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.12 CDRL A012, Other Direct Costs Report

4.12.1 The CDRL shall be delivered electronically, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.13 CDRL A013, Systems Security Plan

4.13.1 The CDRL shall be delivered electronically, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

4.14 CDRL A014, Government Property Inventory Monthly Report

4.15 CDRL A015, Government Property Inventory Final Report

4.16 CDRL A016, Small Business Utilization Report

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

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

4.17 CDRL A017, Computer Software Product for Government Use

4.18 CDRL A018, Software Version Description

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 may require access to classified information up to the CONFIDENTIAL level. No classified data will be generated or stored by the Contractor. The Contractor is required to have and maintain a CONFIDENTIAL 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 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 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 (Not Applicable)

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…