Att 7_Sample SOW.docx

THIS IS A SAMPLE STATEMENT OF WORK (SOW) AND IS PROVIDED SOLELY FOR THE PURPOSE OF ASSISTING INTERESTED VENDORS IN DEVELOPING A DRAFT SOW FOR IMPLEMENTING ITS PROPOSED SOLUTION TO MEET GOVERNMENT PROGRAM OBJECTIVES. VENDORS MAY ALTER, REVISE, CHANGE, ADD, OR DELETE THIS DRAFT SOW TO ACCURATELY REFLECT ITS TECHNICAL APPROACH TO ACHIEVE ITS SOLUTION.

ABC Company Draft Statement of Work (SOW)

For

Advanced Electrochromic Manufacturing Prototype Project

DATE

1. Requirements:

1.1 General Requirements:

1.2 Specific Requirements:

The following table compares the proposed solution with the Government’s minimum final prototype threshold and overall program objectives: The following table provides the minimum threshold requirements for the final prototype and the Government’s overall EPEDP program objectives.

99%

100%

1%

200µs

10 µW/cm2

1%

5%

36 mos

No noticeable color tinting (specify CIE (u’v’) coordinates)

Continuously variable

72 hrs

100% US based

Production Rate:

· Toroidal visor (200 cm2 active area)

· Spherical goggle (40cm2 active area)

· Spectacle lens pair (27 cm2 active area)

· Toroidal visors: 20 /week

· Toroidal visors: 40 /week

· Spherical goggles:100/week

· Spectacle lens: 500/week

Mandatory

1.2.1 – Steps to accomplish the solution

1.2.2 –

1.2.3 –

2. Deliverables

2.1 Project Technical Milestones/Decision Points (DP)

The program awardee will provide the following deliverables After Receipt of Agreement (ARA) as indicated. This portion should be included in the draft SOW with further detail provided to match proposed solution. For example, if the proposed solution includes quarterly submission of advancing test samples, then the draft SOW should have a corresponding section/paragraph that correlates with each submission.

2.1.1 Project Kick-off

The Contractor shall support a project Kick-off Meeting within thirty (30) calendar days After Receipt of Award (ARA) and provide presentation charts two (2) workdays prior. The agenda shall address project scope, performance, schedule, progress, funding, metrics, risks and their mitigation, and new product opportunity analyses.

2.1.2 Project Execution Plan (2 months ARA)

The Contractor shall host the Project Execution Plan (PEP) meeting, within sixty (60) days ARA. The PEP shall include the following:

i. Introduction of Personnel (Management, Technical);

ii. Company Business Plan and synergies with this (OASD(IBP) project;

iii. Current and Planned Product Roadmap;

iv. Plan of Action and Milestones (POAM),

v. Performance metric-based approach for expanding domestic manufacturing capabilities and improving technical performance,

vi. Supply chain for current products;

vii. Plans to on-shore any items not currently available from a US based source.

2.1.3 Design and Manufacturing Plan (3 months ARA)

The Contractor shall provide Design and Manufacturing Plan of their approach toward the agreed upon deliverables to the Government within three (3) months ARA. The focus of the design and manufacturing plan shall include but not limited to:

a. Design to include the solution of the prototype:

i. Solution of the prototype/product with all the requirements in 3.2

ii. Improvement (if any) to meet the objectives

iii. U.S.-Based Supply chain and Materials

iv. Non-U.S.-based Supply Chain and Materials

v. Software & Hardware

vi. Technical Risks, Supply Chain risks and Mitigation plans

b. Manufacturing plan, processes, and target of production rate:

i. Facility

ii. Equipment

iii. Supply chain capability and resilience

iv. Target production capability

v. Manufacturing technology Risks, Supply Chain risks and Mitigation plans

2.1.4 Monthly Progress Reports and Quarterly Project Management Reviews (PMR)

The Contactor shall provide a written Monthly Progress Report limited to 20 pages of text/figures/tables describing: (a) technical and manufacturing achievements since the prior month, (b) plans for next month, and (c) a discussion of any issues. A written Monthly Progress Report is not required in months in which a Quarterly PMR is conducted.

Starting in the third month ARA the Contractor shall support either virtually or in person Quarterly PMR meetings throughout the life of the agreement. The Quarterly PMR read-ahead materials will be submitted to the government 7 business days before the meetings. The PMR shall cover the state of the project execution plan (milestones completed), progress on deliverables, the quality of monthly status reports, funding status, schedule (Gantt chart), comparison of current performance metrics vs. prototype thresholds/program objectives, and other pertinent information.

2.1.5 Test Article Sets

Solutions shall identify multiple sets of Test Articles for submission to the government for testing to validate the progression of the prototype throughout development. This shall identify the Test Article type, quantity and timeline for each submission. The Government preference is for increasing quantities (minimum quantity of four (4)) of test articles at six (6) month intervals until delivery of the final prototype quantities. The first set test article submitted will establish the baseline EDEPD performance for the manufacturer. The manufacturer shall provide test reports of these articles which include all the requirements listed in the SOW. The report shall include the baseline TRL of this set.

2.1.6 Final Set of Test Articles

Depending on the offered solution, the final set of test articles shall include 20 Toroidal visors and/or 35 Spherical goggles and/or 200 Spectacle lens to demonstrate the manufacturing capabilities and prove the processes using US-based qualified sources of supplies. The report shall include the manufacturer’s test reports that meet or exceed all the requirements listed in the SOW. The report shall include the Government expected TRL and MRL for this set.

(24 months ARA) Final Reports

a. Technical report of the prototypes/products to include:

i. Certification of MRL/TRL with Government

ii. Test Reports

iii. US-based suppliers with production capabilities, and

iv. Equipment used

b. Manufacturing capabilities and processes reports

2.1.7 Other Deliverables

3. Government Rights in Technical Data and Computer Software

The Government requires Government Purpose Rights (GPR) in all technical data (including computer software documentation) and computer software developed under any OT associated with this effort, for, at most, a five-year period. The five-year period, or such other period as may be negotiated, will commence upon execution of the OT that required development of the technical data (including computer software documentation) and computer software. Upon expiration of the five-year (or other negotiated period), the Government desires unlimited rights in the technical data (including computer software documentation) and computer software. Printed deliverable (e.g., printed hardcopies, .doc, web-based html, etc.) will be labeled accordingly and contain all appropriate markings associated with the distribution classification.

All technical data, intellectual property and non-commercial off the shelf (non-COTS) software will be provided with a minimum of GPR.

Any commercial or COTS shall be provided with a transferable license that allows distribution of the software and transfer of the license to any Government agency or DoD vendor for any prototype project related purpose. All software licensing shall include a minimum term of five years of use. All software shall be provided with any available major upgrades, minor updates, security patches and technical support for the entire PoP. When the addition of new software or hardware is proposed for the system or developed under this solicitation with Government funding or partial Government funding, the vendor shall ensure that sufficient rights in technical data to include (software and hardware) are procured to enable the Government to maintain and modify the system using Government personnel and/or third-party vendors. Government approval is required for exceptions to GPR.

In its solution, the vendor for any OT awarded in accordance with this RFS shall analyze feasible non-proprietary solutions and incorporate such solutions into its proposed solution when practicable. This preference for non-proprietary solutions applies to any technical data (including computer software documentation) and computer software developed or delivered under the OTA. The vendor shall clearly state all assumptions made during development of its proposal.

The vendor shall provide a data rights assertion table, Attachment 2, for all technical data (including computer software documentation) and computer software to be developed or delivered under the OTA. The data rights assertion table shall identify at the lowest segregable level the technical data (including computer software documentation) and computer software to be developed or delivered under the OTA, the vendor’s assertion as to the Government’s rights in each item of technical data (including computer software documentation) and computer software, the basis for such assertion, and the name of the person asserting any restrictions.

For any technical data (including computer software documentation) or computer software in which the vendor asserts the Government will have less than Government purpose rights, the vendor shall provide the open source, commercial, or other license it asserts is applicable. The vendor’s assertions, including any assertions of its sub-vendors or suppliers must be submitted as an attachment to its Solution Paper. The tables must be completed in the format set forth in the attachment, dated and signed by an official authorized to contractually obligate the vendor. If additional space is necessary, additional pages may be included. There is no page limit for the Data Rights Assertions Tables, and they do not count against the proposed technical solution page limitation.