Exhibit_A_SPRBL1-17-R-0008_-_Statement_of_Work.pdf

Statement of Work for Configuration Control

1. Scope. This SOW establishes contractor requirements for Configuration Control.

2. Applicable Documents:

2.1 Data Item Description.

DI-MISC-80711A Scientific and Technical Reports

2.2 Commercial Documents

MIL-HDBK-61A Configuration Management Guidance (Dated 7 Feb 2001)

3.1 Requirements for Configuration Control.

3.1.1 Configuration Baseline. The applicable Configuration Baseline (CB) for the listed Configuration Item (CI)/Computer Software Configuration Item (CSCI) is as follows:

CI/CSCI CB

5kw APU Engine (P/N: 96-9370) 96-9370

OR

5kw APU Engine (P/N: MP-028) MP-028

OR

5kw APU Engine (P/N: 432-9900) 432-9900

3.1.2 Configuration. Each CI/CSCI, as developed/built and delivered, shall conform to the cited CB and (if applicable) all subsequent CB’s that will be made contractually binding by the Procuring Contracting Officer (PCO). Configuration changes not directly effecting the configuration baseline do not require Government approval prior to incorporation, but must be documented by the contractor and shall be made available to the Government upon request. The contractor may use MIL-HDBK-61A as guidance for establishing a Configuration Management Program.

3.1.3 Departures from CB. No changes or departures from the CB are acceptable except for changes or departures which are submitted in accordance with DI-MISC-80711A and are approved by the Government Configuration Manager (C Mgr.) or Configuration Management Officer (CMO) and which are made applicable to the contract by the PCO. Configuration Control shall be effected by the Configuration Control Documents (CCDs) as follows:

3.1.3.1 Engineering Change Proposal (ECP) includes both the engineering change and the supporting documentation by which the change is described and suggested. An ECP describes changes to the CI/CSCI and associated Government documents and data that are affected by the proposed engineering change.

3.1.3.1.1 A Notice of Revision (NOR) shows the detailed changes that must be made to technical documentation, except specifications, (one NOR per document) following approval of an ECP. The NOR is submitted as part of the ECP.

3.1.3.1.2 A Specification Change Notice (SCN) is used to delineate the exact change(s) in a specification that will be distributed to users when the ECP is approved. The SCN is submitted as part of the ECP. The SCN is not used for a military or federal document, only a Request for Waiver can be used for those documents.

3.1.3.1.3 Value Engineering Change Proposal (VECP) is the same as an ECP except there are proposed cost savings for the program. The contractor shall follow the guidance in Section I of this contract for VECPs.

3.1.3.2 Request For Deviation (RFD). A RFD is a specific written authorization to depart from a particular requirement(s) of an item’s approved configuration documentation for a specific number of units or a specified period of time, either as an advance request or after the fact. The contractor shall identify the impact of the RFD on performance, operational readiness and logistics support of the affected CIs. The Government may require consideration for any RFD.

3.1.3.3 Contractor shall provide all supporting program or cost data with the CCD. The contractor shall uniquely and sequentially identify (including the use of the contract number) each ECP, VECP, NOR, SCN or RFD. The identification number should use less than 16 characters.

3.1.4 Identification of Authorized Personnel. The contractor shall identify to the PCO, Administrative Contracting Officer (ACO), and the technical office identified on the DD Form 1423 for DI-MISC- 80711A, the name(s) of the official(s) of its organization who are authorized to submit CCDs 30 Days after Contract (DAC).

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Original Form Approved OMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA. 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

5kw APU Engine

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE GROUP

Scientific and Technical Reports Configuration Control

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-MISC-80711A SOW Para 3.1.5.3 RDER-PRP-G INSERT

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION IN

LT ASREQ SEE ITEM 16 b. COPIES

SECT. B

8. APP CODE N/A 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

SEE ITEM 16

Reg

Repro

16. REMARKS: Data Item Description DI-MISC-80711A: Delete block 10 instructions entirely and follow instructions in SOW 3.1.

The contractor shall prepare and submit Configuration Control Documents in accordance with the SOW section for Configuration Control (Para 3.1) when a change to or departure from a contractual baseline document is deemed necessary.

The Government will have 30 days to review, accept, and/or comment on the draft submission. The contractor shall incorporate changes into the electronic deliverable within 30 days after receipt of Government comments. The Government will have 30 days to review, accept, and/or comment on the final submission.

Data shall be submitted and exchanged electronically in Microsoft Office 2013 suite of applications (MS Word, Excel, Power Point, Access, and Project). Alternate formats may be allowed subject to Government review and approval.

If the CDRL Data Deliverable is priced and is not NSP (Not Separately Priced), then an electronic DD Form 250 will be required via the Wide Area Workflow website in order for the contractor to receive payment for the data deliverable (see section G of the Contract). E-mail notification is required with any electronic submission.

RDER-PRP-G

PCO

ACO

QAR

15. TOTAL 0 4 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Chichung Chang

RDER-PRP-G

Electronics Engineer

1/26/2017 Mark Caringi

RDER-PRP-G

Branch Chief

1/26/2017

Based upon DD Form 1423-1, 1 Jun 90

3.1.5 Documentation. The contractor shall document by serial number each products configuration, applicable documentation, maintenance support requirements and spares in relation to the contractor’s configuration baseline. The data in use shall be available for government review and use.

3.1.6 Use of CB Data. The contractor shall assure that all necessary contractor’s activities have access to and use of the contractually specified configuration baseline(s), approved changes and departures, and effectivity data. The data in use shall be available for government review and use.