SLEP_CDRLs_Exhibit_B_11Jan16.pdf

PREFACE TO CONTRACT DATA REQUIREMENTS LIST (CDRL) (DD FORM 1423)

1. The contractor shall develop and deliver only that data agreed to by the Government in the Exhibit(s) and data items deliverable under any contract clause. The contractor may suggest changes to deliverable data listed in the Exhibit(s) but all changes shall include an explanation. If the contractor elects to suggest changes, the contractor shall use Data Item Descriptions (DIDs) listed at http://www.dodssp.daps.mil, in ASSIST to convey format and content preparation instructions. The use of DIDs by the Contractor is required by the Government to comply with Public Law 104.13, the Paperwork Reduction Act of 1995 as amended. Additional information on the use of DIDs is contained in paragraph 3.0 below. Any additional data proposed by the contractor shall be presented in the format illustrated by CDRLs identified in the Exhibit(s).

2. Delivery media for data shall be digital whenever possible, however no data identified with distribution statement "B" through "F" shall be transmitted over the commercial Internet or equivalent unless password/ID protected and encrypted by a government approved program. Information may also be provided via onsite reviews, technical interchange meetings, telecommunications conferencing, or other means in lieu of formal submissions considered adequate by the contractor and agreed to by the Government.

3. If the contractor proposes the use of a commercial or contractor unique process as part of the Single Process Initiative (SPI), the contractor unique process documentation shall be provided in the response to the solicitation unless previously approved under the SPI. If the proposed process results in the delivery of data in a specific format and/or content and no DID listed in ASSIST is suitable, the contractor shall develop a One Time (OT) DID for each type of data and submit an electronic version with the corresponding CDRL Sequence Number. MIL-STD- 963B may be used as a preparation guide. If the OTIME DID is determined to be acceptable, the contractor shall electronically transmit the DID to the CO using Microsoft Word. If the DID is approved by HQ AFMC, the OTIME DID and the contractor unique process shall become part of the contract as an attachment to the applicable CDRL. In selecting a DID from ASSIST, the contractor should consider that each DID represents the maximum allowable information to be delivered for any one type of data. Information in the DID has been approved as written by the Office of Management and Budget and cannot be expanded upon, only reduced

4. As part of the response to the solicitation, the offeror shall provide an estimated cost and supporting rational for each item of data listed on the CDRL (CDRL items are identified individually by the sequence number appearing in Block 1 of each CDRL). Price Group definitions are contained on the last page of this CDRL package (Form 1423 Reverse JUN 90).

a. The offeror shall complete Blocks 17 and 18 of the DD Form 1423 and include the estimated number of pages plus estimate the number of man-hours (broken down by skill category) attributable to the preparation and delivery of the data.

NOTE: These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required.

b. The offeror is encouraged to submit recommendations, suggested changes, or alternate proposals with the response (right hand margin of the CDRL or a separate sheet may be used).

5. The following comments are provided as clarification to the CDRL:

Block 1: Data Item Number: An identification number assigned to each individual item of data.

Block 2: Title: The exact title taken from the Data Item Description (DID) (DD Form 1664).

Block 3: Subtitle: Used to further identify the title or as a continuation line for a long title. Also used to differentiate the same data item description used more than one time on the same contract.

Block 4: Authority: The identification number assigned to the Data Item Description (DID) (DD Form 1664) number, military specification number or military standard number listed in ASSIST or one-time DID number that defines data content and format requirements.

a. A letter immediately following the number indicates a revision to the DID.

b. A DID may be tailored. Tailoring is the process of focusing on obtaining only minimum essential technical data and data rights for each acquisition. Tailoring instructions e.g., instructions that specify those portions of the DID or other acquisition document that are not applicable to the acquisition, will be specified in BLK 16 of the CDRL.

c. More than one data item may be used to construct a specific data requirement. Each data item will be separately listed on the CDRL and CDRL BLK 16 will be used to show the relationship (for example, “Combine with contract data item DI-X-XXX for submission”, or “Data prepared in accordance with DI-X-XXX”).

Block 5: Contract Reference: A cross-reference to the associated contract tasking document (Statement of Work, Appendix “A” and/or “B”, procurement specification, etc.) which causes the data to be generated. Appropriate document identifiers and paragraph numbers will be used.

Block 6: Requiring Office: the office responsible for advising on the technical adequacy of the data.

http://www.dodssp.daps.mil/

Block 7: DD Form 250 Required: Designation of the location for government inspection and acceptance of the data. One of the following codes will be used, depending on how the data is to be delivered:

CODE INSPECTION ACCEPTANCE

SS *Source (DD Form 250) *Source (DD Form 250)

DD Destination (DD Form 250) Destination (DD Form 250)

SD *Source (DD Form 250) Destination (DD Form 250)

DS Destination (DD Form 250) * Source (DD Form 250)

LT Letter of Transmittal only

N/A No inspection or acceptance required.

XX Inspection and acceptance requirement specified elsewhere in the contract.

*Source indicates contractor’s facility.

a. Unless noted otherwise in CDRL BLK 16, the activity to perform destination acceptance will be the first addressee in CDRL BLK 14.

b. When DD Form 250 is required, it shall be submitted for final deliveries only. All submissions prior to final delivery, i.e., outlines, drafts, preliminary, or review copies, etc., shall be submitted by letter of transmittal.

Block 8: Approval Code: All data are subject to Government approval however, selected data will require advance approval of a preliminary, draft, outline or review prior to being distributed as final copies to the addressees listed in Block 14 of the DD Form 1423. The letter “A” appearing in Block 8 of the DD Form 1423 will designate such data.

Block 9. Distribution Statement Required: If a Distribution Statement is required, enter appropriate Distribution Code in this block. The distribution of technical data containing US technology with military or space application must be controlled. All data including software that is regulated by Title 22 CFR (Code of Federal Regulations) Parts 120-130, known as the International Traffic in Arms Regulation, and contractor proprietary data shall be safeguarded from export and unauthorized dissemination IAW Title 22 U.S.C (United States Code) 2571 et. seq., or Executive Order 12470, Air Force Instructions (AFI) 61-204 and when transmitted electronically, AFI 33-129. No data identified with distribution statement "B" through "F" shall be transmitted over the commercial Internet or equivalent unless password/ID protected and encrypted by a Government approved program. The following Distribution Statements when identified as a requirement on the CDRL shall be affixed to deliverable data in a conspicuous position. Enter in BLK 16, the information required for the contractor to complete the distribution statement (fill in reason), (date of determination) and (DoD controlling Office). When the contracting agency cannot determine the correct statement, the contractor may be tasked to recommend one of the statements listed in Attachment 2 to this Preface.

Distribution Code Statement

A Approved for public release; distribution is unlimited

B Distribution authorized to U.S. Government agencies (fill in reason) (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

C Distribution authorized to U.S. Government agencies and their contractors (fill in reason) (date of determination).

Other requests for this document shall be referred to (insert controlling DoD office).

D Distribution authorized to Department of Defense and U.S. DoD contractors only (reason) (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

E Distribution authorized to DoD Components only (fill in reason) (date of determination). Other requests shall be referred to

(insert controlling DOD office)

F Further dissemination only as directed by (insert controlling DoD office) (date of determination) or higher DoD authority.

All printed and electronic, including digital, technical documents that are determined to contain export-controlled technical data shall be marked as shown below:

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.)

or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

Unclassified documents marked with Distribution Statements B, C, D, E, or F shall be marked with the destruction notice shown below:

“DESTRUCTION NOTICE - For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

Classified documents marked with Distribution Statements B, C, D, E, or F shall be marked with the destruction notice shown below:

“DESTRUCTION NOTICE - Follow the procedures in DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), section 5-705, or DoD 5200.1-R, Information Security Program, Chapter VI.

Block 10: Frequency: The frequency for submitting the data will be indicated by use of one of the following codes:

DAILY - Daily ANNLY - Annually WEKLY - Weekly SEMIA - Each 6 months BI-WE - Each 2 weeks OTIME - One time MTHLY - Monthly ONR/R - One time & revisions BI-MO - Each 2 months R/ASR - As required QRTLY - Quarterly *ASREQ- As required 2TIME - Two separate submittals DFDEL -Deferred delivery ONE/P One-time preliminary draft

* When ASREQ is used in Block 10, 12, or 13, an explanation of the requirement will be entered in Block 16.

Block 11: As of Date: If the data will be submitted only once, the entry in this field will be the cut-off-date as follows: year/month/day. If the data will be input on a recurring basis, which has been set by item 10, the entry will show the number of days between the cut-off date and the end of the input period. As an example, if the data are to be submitted 15 days before the end of the input period, the entry will be 15. If the data are to be submitted at the end of the input period, the entry will be 0. If necessary, BLK 16 will be used to explain further.

Block 12. Date of First Submission. The entry will be Year/month/day. If delivery of the data depends on the initiation of a specific event or milestone, the event or milestone will be identified. If the contract start date is unknown, the entry will be the number of days the data is due after contract start e.g. 3RD (Days after Contract). If this date is not known or needs more clarification, BLK 16 will be used to explain further. If the data are subject of deferred deliver “DFDEL” will be used. In all cases when an acronym is created to identify an event or milestone, the acronym will be further defined in BLK 16 if not elsewhere in the contract.

Block 13: Date of Subsequent Submission: If the data will be required to be submitted more than once the dates will be entered. If a draft is required, the date the final document is to be submitted will be entered. (If this event would cause the data list to become classified, the field will be left blank. ‘for example Not later than 15 days before start of production, 45 days before launch e., If an acronym is used to identify an event or milestone, the acronym will be further defined in BLK 16 if not elsewhere in the contract.

Block 14a Addressees: Each addressee will be identified by office symbol, contractor initials or DOD Handbook H-4 code numbers and command initials; in this case a list explaining the codes will be attached. If the data are not to be delivered to the government or to associate contractors, appropriate instructions will be entered either in BLK 14a or BLK 16.

Block 14b. Copies: The number and type of copies (regular and reproducible to be received by each addressee will be entered in these fields). If reproducibles are required, the type of reproduction request will be specified e.g. offset, mat, vellum, negative, floppy disk, magnetic tape, aperture card etc. either in these fields or defined further in BLK 16.

Block 15 Total: This entry will be the total number of copies (regular and/or reproducible) for one delivery. If distribution fluctuates, the use of Not To Exceed (NTE) will be used.

Block 16 Remarks: This block will be used to explain:

a. Tailored features of the DID.

b. Items 1 through 15 when required.

c. Any resubmittal schedule or special conditions involved in updating data submitted for government approval.

d. The BLK 9 distribution statement when deemed appropriate by the contracting agency.

6. The following Organizational Cross Reference List shall be used in conjunction with the CDRLs to determine actual addressees for distribution of data. The ORG number will be entered in lieu of an address on the CDRL and will be a part of the CDRL package.

Changes to the list will be identified by an asterisk next to the ORG number and a revision date to the list.

ORG1= AFNWC/NDW

8601 Frost Avenue (Bldg 20203) Kirtland AFB, NM 87117 Attention: WS3 SLEP PM E-Mail Address: afnwc.ws3workflow@kirtland.af.mil and Briana.Lee.2@us.af.mil

ORG2 =AFNWC/PZNK

8500 Gibson Blvd. SE, Bldg. 20202 Kirtland AFB, NM 87117 Attention: WS3 SLEP Contracting Officer E-Mail Address: jayne.faris.1@us.af.mil and honey.smalls.1@us.af.mil

ORG3 =AFNWC/FM

1551 Wyoming Blvd. SE Kirtland AFB, NM 87117 Attention: WS3 SLEP FM rep E-Mail Address: afnwc.fmworkflow@kirtland.af.mil

ORG4 =USAFE/A10NM

E-Mail Address: usafe.a10nmmaintenancebranch@ramstein.af.mil

ORG5 = OLRAM

E-mail Address: olram.workflow@us.af.mil

ORG6 = AFNWC/NDET

Attention: Benjamin Salinas 2000 Wyoming Blvd. SE Kirtland AFB, NM 87117-5617 E-mail: benjamin.salinas@us.af.mil

ORG7 = TBD (WS3 SLEP Testing Agency)

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

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:

0001, 0002, 0005, 0010, B

TDP_________TM__________OTHER ___X_____

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

WS3 Service Life Extension Program

(SLEP)

TBD

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

B001

Software Development Plan

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

TOTAL PRICE

DI-IPSC-81427A SOW para 2.1.1.4 and 2.1.1.4.1 AFNWC/NDW

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION 14. DISTRIBUTION

DD BLK 16 BLK 16 b. COPIES

8. APP CODE D 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Draft Final

A N/A BLK 16

Reg

Repro

16. REMARKS: CHANGES TO OFFICE SYMBOLS, WHEN NECESSARY, SHALL

BE MADE BY THE CO/ACO WITHOUT REVISIONS TO THE CDRL.

CDRL B001 is applicable only if software development is required as part of this contract.

BLOCK 9:

Distribution Statement D: (see page 2 & 3 for distribution statement, warning, and destruction notices)

BLOCKS 10, 12 &13:

Contractor shall submit a draft Software Development Plan (SDP) NLT 20 business days prior to PDR.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SDP incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

Contractor shall submit final SDP NLT 20 business days prior to CDR.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SDP incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

BLOCK 14:

Electronic submittal in Microsoft Office product or compatible software approved by Government; PDF is not acceptable.

ORG 1

ORG 2

15. TOTAL 1 2

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

John Hedenberg SLEP Systems Engineer

AFNWC/NDWA

9 Nov 2015

Robert Buchanan SLEP Program Manager

LM 11-30

(1 Data Item)

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.

B

TDP_________TM__________OTHER ___X_____

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

B002

Software Quality Assurance Report

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

TOTAL PRICE

DI-QCIC-81795 SOW para 2.1.1.6 and 2.1.1.6.1 AFNWC/NDW

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

a. ADDRESSEE

Draft Final

BE MADE BY THE CO/ACO WITHOUT REVISIONS TO THE CDRL.

CDRL B002 is applicable only if software development is required as part of this contract.

BLOCK 9:

Contractor shall submit a draft Software Quality Assurance Report (SQAP) NLT 20 business days prior to PDR.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SQAP incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

Contractor shall submit final SQAP NLT 20 business days prior to CDR.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SQAP incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

BLOCK 14:

John Hedenberg

SLEP Program Manager

9 Nov 15

(1 Data Item)

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.

B

TDP_________TM__________OTHER ___X_____

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

B003

Software Requirements Specification

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

TOTAL PRICE

DI-IPSC-81433A SOW para 2.1.1.10 AFNWC/NDW

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

a. ADDRESSEE

Draft Final

BE MADE BY THE CO/ACO WITHOUT REVISIONS TO THE CDRL.

CDRL B003 is applicable only if software development is required as part of this contract.

BLOCK 9:

Contractor shall submit a draft Software Requirements Specification (SRS) NLT 20 business days prior to the Preliminary Design Review (PDR).

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SRS incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

Contractor shall submit final SRS NLT 20 business days prior to CDR.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SRS incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

BLOCK 14:

John Hedenberg

SLEP Program Manager

(1 Data Item)

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.

B

TDP_________TM__________OTHER ___X_____

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

B004

Software Design Description

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

TOTAL PRICE

DI-IPSC-81435 SOW para 2.1.1.1 and 2.1.1.10 AFNWC/NDW

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

a. ADDRESSEE

Draft Final

BE MADE BY THE CO/ACO WITHOUT REVISIONS TO THE CDRL.

CDRL B004 is applicable only if software development is required as part of this contract.

BLOCK 9:

Contractor shall submit a draft Software Design Description (SDD) NLT 20 business days after CDR.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SDD incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

Contractor shall submit final SDD NLT 20 business days prior to CT of the SIL.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SDD incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

Contractor shall deliver subsequent submissions of the SDD based on changes to the software during testing (SIL and First Article testing). Contractor shall submit subsequent submissions NLT 20 business days after a completed test event. Government will be allowed 10 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SDD incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

BLOCK 14:

John Hedenberg

SLEP Program Manager

AFNWC/NDWA

(1 Data Item)

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.

B

TDP_________TM__________OTHER ___X_____

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

B005

Software Product Specification

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

TOTAL PRICE

DI-IPSC-81441A SOW para 2.1.1.10 AFNWC/NDW

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

a. ADDRESSEE

Draft Final

BE MADE BY THE CO/ACO WITHOUT REVISIONS TO THE CDRL.

CDRL B005 is applicable only if software development is required as part of this contract.

BLOCK 9:

Contractor shall submit a draft Software Product Specification (SPS) NLT 40 business days after CDR.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SPS incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

Contractor shall submit final SPS NLT 20 business days prior to completion of SIL Contractor Testing.

Government will be allowed 20 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SPS incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

Contractor shall deliver subsequent submissions of the SPS based on changes to the software during testing (SIL and First Article testing). Contractor shall submit subsequent submissions NLT 20 business days after a completed test event. Government will be allowed 10 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised SPS incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

BLOCK 14:

John Hedenberg

SLEP Program Manager

AFNWC/NDWA

(1 Data Item)

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.

B

TDP_________TM__________OTHER ___X_____

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

B006

Software Test Report (STR)

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

TOTAL PRICE

DI-IPSC-81441A SOW para 2.1.1.1 and 2.1.3.5 AFNWC/NDW

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

DD ASREQ BLK 16 b. COPIES

a. ADDRESSEE

Draft Final

BE MADE BY THE CO/ACO WITHOUT REVISIONS TO THE CDRL.

CDRL B006 is applicable only if software development is required as part of this contract.

BLOCK 9:

Contractor shall submit a Software Test Report (STR) NLT 15 business days after any contractor qualification test performed on the software.

Government will be allowed 15 business days after receipt from contractor to review for approval/disapproval/comments. Contractor shall submit revised STR incorporating Government comments, if applicable, NLT 10 business days after receipt from Government.

BLOCK 14:

John Hedenberg

SLEP Program Manager

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DOD 5010.12-M for detailed instructions)

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package; TM- Technical Manual; Other - other category of data such as “Provisioning,” “Configuration Management”, etc.

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-Explanatory (to be filled in after contract award).

Item F. Self-Explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CDRL was prepared.

Item I. Signature of CDRL approval authority.

Item J. Date CDRL was approved.

Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.

Item 2. Enter title as it appears on data acquisition document cited in Item 4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5012.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the date item (e.g. Statement of Work paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement of the data (ref: DoDD 5230.24)

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of-date of date item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15. Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in items 12 and 13; Explanation of reproducible copies in Item 14; Desired medium for delivery of the data item.

FOR THE CONTRACTOR

Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and such as "Provisioning," "Configuration Management", etc.

Estimated Price - Costs to be included under Group are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of control, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.

d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data. These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract

DD FORM 1423-2 Reverse, JUN 90 *U.S. Government Printing Office: 1990-260-987:84440