20-0276 Draft SOW.pdf

1 | 11

STATEMENT OF

WORK/PERFORMANCE WORK

STATEMENT

SMALL ARMS TEST FIXTURE

1. INTRODUCTION

The Naval Surface Warfare Center (NSWC), Corona Division, Expeditionary Systems Engineering Division (ESED), is required to perform ballistic testing of subject Small Arms ammunition items.

2. BACKGROUND

As part of the Small Arms ammunition testing performed by ESED, specialized test equipment is used for data collection and instrumentation of specific Small Arms ammunition types. ESED currently has one system for data collection, however it is need of repair/upgrades. Also, with increased workload in Small Arms testing, a second system is required.

3. SCOPE

The scope of this contract is to upgrade current existing test equipment (Universal Receiver and Windage and Elevation Recoil mount) as well as procure an additional Small Arms ballistic test equipment system. This second system should be compatible and have interchangeable parts with the existing system. This Statement of Work (SOW) identifies the test equipment to be received and the requirements.

4. APPLICABLE DOCUMENTS

5. REQUIREMENTS

The following list specifies the requirements for this contract.

1. Repair and refurbishment of current Universal Receiver. Refurbishment of Universal

Receiver will also include upgrading to an Electromagnetic Firing System.

2. Repair/upgrade of existing Windage and Elevation Recoil mount, including new recoil stop bars, front barrel stabilizing mount, new recoil shock absorber.

3. A second new Universal Receiver with an Electromagnet Firing System. The new system must be compatible with existing system and have interchangeable parts.

4. Spare parts required for testing. Parts include firing pins, retainer plates, and shock absorbers.

N/A

2 | 11

6. GOVERNMENT FURNISHED PROPERTY

6.1 Government Furnished Material

6.2 Government Furnished Equipment

6.3 Government Furnished Information

7. DELIVERABLES

NUMBER NAME

N/A

8. ACRONYM LIST

ACRONYM DENOTATION

The Government will furnish the following items to be repaired and upgraded.

1. One (1), multi-caliber Universal Receiver

2. One (1), Windage and Elevation Recoil Mount

3 | 11

ADDITIONAL INFORMATION

A. PERIOD OF PERFORMANCE / REQUIRED DELIVERY DATES

The required delivery date is no later than 90 days after contract award.

4 | 11

STATEMENT OF

WORK/PERFORMANCE WORK

INSTRUCTIONS

Remove either “STATEMENT OF WORK” OR “PERFORMANCE WORK

STATEMENT”

HEADER

Remove “HEADER” and provide a short title that best identifies the task requirements to be performed Keep it simple – a one-liner is adequate. Make this a short phrase by which the job is generally known (e.g. RANGE SUPPORT SERVICES; THREAT ENGINEERING SUPPORT SERVICES). Procurement actions are generally referenced by this title until a contract number is assigned by the Contracts Department; therefore ensure the title is representative of the requirements.

1. INTRODUCTION

Provide just enough information for the reader to understand what is being procured and by whom (i.e. department name and code). This section should not be lengthy or include any information that is contained in other sections of the SOW/PWS.

2. BACKGROUND

This section shall help the reader get a good understanding of what is being procured and why.

When writing this section, assume that the reader does not have any knowledge or experience with the requirements of the procurement. Therefore provide historical information necessary to understand how the requirements were derived and why the requirements are needed. In addition, identify the current state of the requirements. If the requirement is part of a larger program, identify the program and the relationship of the requirement to the overall program.

Also, identify research, studies, or other efforts that contribute to the reader’s understanding of the requirement. Make sure only facts and relevant information is included. The length of this section should not exceed four paragraphs; however, it is more important to fully discuss the

5 | 11 background than it is to try to stay within length constraints. Do not include any information that is contained in other sections of the SOW/PWS.

3. SCOPE

The scope is an executive level overview of the requirements being procured under Section 5.0, REQUIREMENTS. This section should emphasize on the most important aspects of the requirements and not the details. Identify the objective or purpose of the requirements and the place of performance (location(s) where the contractor is to perform the tasking) to help the reader understand the magnitude of the effort to be performed. Generally, the scope section should be no more than two paragraphs. Do not include any information that is contained in other sections of the SOW/PWS.

4. APPLICABLE DOCUMENTS

List all documents referenced under Section 5.0, REQUIREMENTS, with which the contractor must comply in performance of the SOW/PWS (e.g. agency orders, directives, specifications, standards, and notices). It is recommended that this section not be prepared until at least a draft of the Requirements Section, Section 5, is complete as both sections are interrelated.

Documents referenced in Section 5 of the SOW/PWS must be listed in this section. If only portions of a document apply, identify only the applicable portions in this section. Be familiar with the content of the documents listed in this section to ensure that only required documents are listed. All applicable documents must be provided with the Technical Data Package. If public links are available, provide the website address, otherwise electronic copies of the documents are required.

Do not list non-mandatory documents that are referenced for informational or guidance purposes only or documents not referenced in section 5 of the SOW/PWS. Any document being provided to the Contractor prior to or upon award of the contract should not be listed in this section; it should be listed as Government- Furnished Information (GFI).

FAR 11.2 requires that applicable documents listed “SHALL IDENTIFY EACH

DOCUMENT’S APPROVAL DATE AND THE DATES OF ANY APPLICABLE

AMENDMENTS AND REVISIONS. DO NOT USE GENERAL IDENTIFICATION

REFERENCES SUCH AS "THE ISSUE IN EFFECT ON THE DATE OF THE

SOLICITATION.”.

Example Federal Standards: The contractor is required to adhere to all applicable standards and guidelines when applicable. In the absence of named standards, Department of the Navy (DON) standards, applicable Federal Information Processing Standards (FIPS), and broadly accepted professional standards shall prevail as related to the associated industries within the task identified in Section 5.0.

6 | 11

Document Type

No./Version Title Date

DoD Instruction

5000.64 Accountability and Management of DoD-

OWNED Equipment and Other Accountable Property. Attachment (1)

2 Nov

SECNAV

M-5216.5 Department of the Navy Correspondence Manual http://doni.daps.dla.mil/secnavmanuals.aspx

March

M-5510.30 Department of the Navy Personnel Security Program, http://doni.daps.dla.mil/secnavmanuals.aspx

June 2006

M-5510.36 Department of the Navy Information Security Program http://doni.daps.dla.mil/secnavmanuals.aspx

June 2006

5. REQUIREMENTS

Enter an intro to requirements here. Canned statements below in sections 5.1-5.3 can be used, but shall be tailored to fit the requirement. This section shall identify and describe all of the requirements (tasks) that the Contractor is required to perform without stating how the requirements are to be accomplished. The level of description provided about the requirements is crucial. This does not mean there has to be a multi-volume specification for each requirement, but each requirement shall be defined with sufficient detail to avoid ambiguities and misunderstandings. It is not the Contractor’s responsibility to figure out what the Government wants; it is the Government‘s responsibility. Requirements that can only be defined in general terms do not lend themselves toward the most desirable contract type and pricing structure.

Requirements should be broken down and identified under major tasks and subtasks corresponding to the desired contract structure (i.e. Contract Line Item Numbers) and/or to ensure maximum performance and fiduciary traceability. Detailing the SOW/PWS in this manner will facilitate the development of the Independent Government Cost Estimate (IGCE) and subsequent evaluation of Offerors’ proposals. In addition, provide a summary description under each major task (level one task – e.g. 5.1 Installation Support) to summarize the requirements associated with the major task. Remember to address the following items when identifying requirements, if applicable:

Document References - There are times when it is necessary to describe that a task must be accomplished within certain specifications or standards. Citing an entire reference, without tailoring, infers that the entire reference is applicable and potentially all its references. This could cause unnecessary expenditures, therefore KNOW WHAT THE

REFERENCE SAYS – IN ITS ENTIRETY – AND TAILOR IT BEFORE YOU

INCLUDE IT AS A REFERENCE.

Data Deliverables – Ensure that each task that requires generation of a data deliverable (e.g. technical reports, financial reports, status reports) has the corresponding Contract Data Requirements List (CDRL DD Form 1423) number cited. All formal data

7 | 11 deliverables must be identified in a CDRL form. The citation shall be in parenthesis at the end of the respective paragraph such as “(CDRL A001)”. CDRL requisites including the title, content, format, frequency, and delivery requirements shall be identified in the CDRL form and not in the SOW/PWS. Material Purchases – Address if the contractor will be required to acquire material and the limitations or approval requirements for these purchases.

Travel – Identify any anticipated travel requirements and include estimated locations, number of trips, number of personnel, and estimated duration.

Data Rights – If data is required to be produced, furnished, acquired or specifically used to perform the requirements the SOW/PWS must contain terms that delineate the respective rights and obligations of the Government and the contractor regarding the use, duplication and disclosure of such data. If the proposed procurement involves consideration of patent or data rights, copyrights or license agreements, state the level of data rights required.

The length of this section will depend on the number of major tasks and subtasks and level of detail necessary to convey what is needed or the performance requirements that need to be satisfied. In order to convey the requirements more clearly, try to not exceed paragraph numbering past three levels (e.g. 5.1.5). There are no minimum or maximum page limitations.

This section should not include information that is more appropriate in other sections of the SOW/PWS, the solicitation, or the resulting contract. For example, it should not include evaluation criteria or proposal preparation instructions.

If different funding appropriations (e.g., Operation and Maintenance Navy (O&MN), Shipbuilding and Conversion, Navy (SCN)) will be used to fund tasking then each task applicable to the specific appropriation needs to be separated into its own requirement – even though it may be closely related to, and integral with, other efforts. Separating requirements has some disadvantages, but the advantages outweigh the disadvantages as identified below:

Disadvantages

Lengthens the SOW/PWS and subsequent contract/order

Requires more administration for all parties due to the increased number of tasks

Advantages

Enables the customer to use multiple funding appropriations

Increases traceability of funding (even from the same sponsor) and expenditures against that funding

Decreases the risk of creating an Anti-Deficiency Act

Facilitates monitoring of task expenditures and task performance

8 | 11

Prevents payments being executed using the wrong appropriations (ACRNs).

Example:

The following section specifies the task requirements for the [contract].

5.1 Production Support

5.1.1 Conduct independent review of XX production programs to identify requirements consistent with directives governing the acquisition of system and equipment.

5.1.2 Using acquisition plans, existing hardware contracts and inherent lead-time items, construct schedules for inclusion in documentation for weapon system and equipment acquisitions. (CDRL A001)

5.1.3 Based on production program schedules as well as weapon system configurations, formulate technical documentation for these programs itemizing all supplies, data and services to be obtained. (CDRL A002)

5.2 Foreign Military Sales (FMS) Support

5.2.1 Compare actual deliveries with contract schedules for Military Departments (MILDEP) and

FMS.

5.2.2 Track components and deliverable end items, and compile monthly acceptance reports and quarterly production reports. Consolidate delivery schedules by fiscal year, weapons, components, support equipment and manufacturer.

5.2.3 Provide impact statements when deviations or changes occur and alternative recommendations when required to maintain individual program production integrity. (CDRL A003)

5.3 MILDEP Support

5.3.1 Identify unique MILDEP requirements for the system, its components and associated equipment, based on MILDEP production planning and production support requirements.

5.3.2 Compare current MILDEP acquisition plans and project directive with MILDEP delivery and performance requirements to identify firm and provisioned requirements by component and associated support equipment.

5.3.3 Prepare production documentation for input into the applicable Management Information System (MIS).(CDRL A004)

9 | 11

6. GOVERNMENT FURNISHED PROPERTY

6.1 Government Furnished Material

Enter GFM to be provided here. If not applicable, enter “N/A”

6.2 Government Furnished Equipment

Enter GFE to be provided here. If not applicable, enter “N/A”

6.3 Government Furnished Information

Enter GFI to be provided here. If not applicable, enter “N/A”

7. DELIVERABLES

Enter an intro to Deliverables and list CDRLs in table below. If not applicable, enter “N/A” and delete table. Canned statement below can be used, but shall be tailored to fit the requirement. See section XYZ for the instructions on how to develop a CDRL.

The contractor shall provide deliverables as described in the SOW and CDRLs. Format and delivery schedule for deliverables shall be outlined in CDRLs.

Number Name

A001 Schedule

A002 Technical Report

A003 Impact Statement

A004 Production Report

8. ACRONYM LIST

List all acronyms used in the body of the SOW/PWS. Enter acronyms in table below. If not applicable, enter “N/A” and delete the table.

ACRONYM DENOTATION

10 | 11

11 | 11

THIS PAGE CONTAINS NECESSARY INFORMATION FOR THE PROCUREMENT

ACTION THAT IS PLACED IN OTHER SECTIONS OF THE CONTRACT

B. PERIOD OF PERFORMANCE / REQUIRED DELIVERY DATES

For a Service Procurement: Provide the desired POP. For a Supply Procurement: Provide a RDD for each item in the form of number of days, months, etc. (e.g. 30 days after award). If not applicable, enter “N/A”.

C. PLACE OF PERFORMANCE

Required for a Service Procurement – State the location(s) of where the work will be performed.

If not applicable, enter “N/A”.

D. SHIPPING ADDRESS

Required for a Supply Procurement - State the activity name, DODAAC, address, city and state of the location where the material/equipment is to be delivered. If not applicable, enter “N/A”.

E. INSPECTION AND ACCEPTANCE

Required for both Supply and Service Procurements – State who will be conducting the inspection and acceptance and when and where the inspection and acceptance will be conducted, as applicable.

F. TECHNICAL POINT OF CONTACT

Required for contracts that do not require a COR appointment. Provide the contact information (name, code, phone number, email address) of the requestor(s) that have cognizance over the procurement. If not applicable, enter “N/A”.