ATTACH 1 DRAFT SOW (20-MTE-036).pdf

SOW-PWS Page 1

DRAFT

Statement of Work (SOW) for

Navy Electric Valve Common Actuator Design Services

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Code 414, which is responsible for lifecycle management of Combat Support Systems.

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

(a) 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.

(b) 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

(c) 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.

(d) Employee Relationship:

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.

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.

SOW-PWS Page 2

(e) Inapplicability of Employee Benefits: This Contract does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

(f) Notice. 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) 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.

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 Combat Support System Branch (Code 414) of the Naval Surface Warfare Center, Philadelphia Division (NSWCPD), is the In-Service Engineering Agent (ISEA) for electric valve actuators. Electric valve actuators, henceforth will be referred to simply as actuators.

The Navy Common Actuator (NCA), under the direction of NSWCPD Code 414, is intended to be a simplistic, reliable, supportable, Navy-owned actuator design. The NCA will provide a standardized actuator design to the Navy, with the goal of increased reliability and supportability while reducing procurement and maintenance costs.

1.2 SCOPE OF WORK

The contractor shall provide engineering, technical, and project management services required for the design development of an actuator. Design documentation includes, but is not limited to, systems engineering documentation, drawings and specifications, and

SOW-PWS Page 3 technical design data. The contract shall culminate with the delivery of a developmental level Technical Data Package (TDP) per CDRL A003.

The contractor shall collaborate with NSWCPD throughout the duration of the contract for design input and direction. Where disagreements occur, NSWCPD direction shall take precedent. The NCA shall be designed with considerations for the following; use of common manufacturing techniques, industry standard commercial parts, materials selected to increase reliability, reduced operation and maintenance costs, and feasibility of organizational and intermediate level repairs.

NSWCPD shall have and retain ownership of and/or license rights to all design rights, data rights, and intellectual property rights created pursuant to and in performance of this contract, consistent with the FAR and DFARS clauses recited, referenced, or incorporated herein.

2.0 APPLICABLE DOCUMENTS

2.1 Navy Common Actuator Requirements (NCAR)

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

3.0. REQUIREMENTS

3.1 System Design Requirements

See Document 2.1 Navy Common Actuator Requirements

3.2 Meetings and Design Reviews

Regular, incremental design meetings are required in order to track and maintain design progress. Meetings and design reviews will be held at the Naval Business Center, Philadelphia, PA. Additional informal meetings and communications such as emails and conference calls may be required. On-site meetings shall be attended by all relevant members of the project team. The contractor shall be required to provide meeting minutes for all contract meetings. The contractor shall submit the required documents for Government review and concurrence prior to meetings as defined by the CDRL(s). The contractor shall coordinate scheduling the dates of required review meetings with the Government.

3.2.1 Project Kick Off Meeting

The project kick-off meeting shall be scheduled within thirty (30) days of contract award.

This on-site meeting is required to discuss the project scope, requirements, and expectations. The contractor will address any clarifications within the scope of work and any highlight coordination issues, etc. with the Government representatives. The

SOW-PWS Page 4 contractor shall examine project functions and review project requirements. The contractor and Government team will discuss the technical requirements in depth in preparation for the concept development. The project team will also discuss technical design direction and recommendations for system features based on subject matter expert experience. The meeting must be attended by relevant members of the contractor’s design team who will be working on this contract.

3.2.2 Alternative System Review (ASR) Meeting

Per CDRL 004, the project team will discuss the system design elements and evaluate the suitability / feasibility of the proposed design features.

3.2.3 Preliminary Design Review (PDR) Meeting

Per CDRL 004, the contractor shall present the initial progress submission of the selected concept design. The Government team will review and provide concurrence of the in-progress design direction.

3.2.4 Hardware Critical Design Review (HCDR) Meeting

Per CDRL 004, the contractor shall present the progress submission of the design. The Government team will review and provide concurrence of the design.

3.4 Commonality of Systems, Subsystems, and Components

Contractors are directed to use standard architectures, design guidelines, specifications, and parts from the Shelf (virtual repository of standard architectures, design guidelines, specifications, and approved parts lists for Government and contractor design) and Standard Parts Catalog (SPC) whenever practical and to request that specified parts lists and/or specifications enable enterprise commodity sourcing, when feasible.

If access is requested for purposes of responding to an RFP, the RFP number and a short description of the requirement with contact information for the Contracting Lead for the RFP should be sent to: commonality_program@navy.mil. Accounts created for this purpose will be deactivated after 60 days. If award takes place in that time the contract number and COR information should be provided to retain accounts.

Request access to the Virtual Shelf after award via Defense Acquisition University (DAU), https://acc.dau.mil/VirtualShelf, inquiries regarding issues with account creation or level of access on the Virtual Shelf should be sent via e-mail to commonality_program@navy.mil with the contract number and contact information for the COR.

https://acc.dau.mil/VirtualShelf

SOW-PWS Page 5

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

The contractor shall notify the contracting officer immediately upon determining the unavailability of obsolete materials or components. The contractor shall 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.

4. DATA REQUIREMENTS

4.1 Contract Status Report (CDRL A001)

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

4.2 Travel Report (CDRL A002)

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

4.3 Technical Data Package (CDRL A003)

4.3.1 The Technical Data Package (TDP) shall be delivered in an interim state at the Preliminary Design Review (PDR) and Hardware Critical Design Review (HCDR). See CDRL 003 for full documentation requirements.

4.4 Technical Review Presentation Package (CDRL A004)

4.4.1 The Alternative System Review (ASR) shall occur at the Government facility. The contractor shall present three (3) concept designs to the Government for comment, discussion, and selection. See CDRL 004 for full documentation requirements.

4.4.2 The Preliminary Design Review (PDR) shall occur at the Government facility. See CDRL 004 for full documentation requirements.

4.4.3 The Hardware Critical Design Review (HCDR) shall occur at the Government facility. See CDRL 004 for full documentation requirements.

4.5 Requirements Traceability Verification Matrix (CDRL A005)

4.5.1 The Requirements Traceability Verification Matrix (RTVM) shall include and track changes to scope, requirements, etc as required. See CDRL 004 for full documentation requirements.

SOW-PWS Page 6

5. SECURITY REQUIREMENTS

Not Used.

5.1 U-NNPI SECURITY REQUIREMENTS

6. PLACE OF PERFORMANCE

Contract performance will occur at the contractor facility.

7. TRAVEL

The Contractor may be required to travel from the primary performance location when supporting this requirement. The estimated number of trips is 4.

Travel in support of this requirement is anticipated to include, but may not be limited to, the following alternate performance locations:

Naval Business Center, Philadelphia, PA

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 by the COR and Contracting Officer before travel occurs. Approval may be via the Technical Instruction (TI). 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

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. The Contractor shall submit travel reports in accordance with DI-MGMT-81943 (CDRL A002).

SOW-PWS Page 7

Travel Costs

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.

8.0 GOVERNMENT FURNISHED PROPERTY

9.0 GOVERNMENT FURNISHED INFORMATION

Not Used.

10. PURCHASES

Not Used.

11. COUNTERFEIT MATERIAL PREVENTION

11.1 Electronic End-Items

11.2 Non-Electronic Materiels

12.0 NSWCPD ELECTRONIC COST REPORTING AND FINANCIAL

TRACKING (ECRAFT) SYSTEM

13.0 SPECIAL REQUIREMENTS