Ex_A_CDRL_DDForm1423_A005-008.pdf

DD FORM 1423, AUG 96

CONTRACT DATA REQUIREMENTS LIST

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 440 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 the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

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

TDP ________ TM _______ OTHER _________________________

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

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page ____ of ____ Pages

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 5010.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 data 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 on 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 data 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 administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I 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 content, 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 (BACK), AUG 96

Task Order (TO) STI Assessment Report – Working Aid – 1 March 2017

TO STI Assessment Report

IAC: _________________ Contract Number: _____________ Date: _____________

Reporting Period: __________________

IAC Director IAC Technical Point of Contact

Name: __________________________________ Name: _____________________________

Phone/FAX:______________________________ Phone/FAX:_________________________

Email: __________________________________ Email: _____________________________

COR:

Name:_____________________________

Phone:_____________________________

FAX:_____________________________

Delivery Order #

Status* (open/closed/ inactive)

Ceiling Value

% Ceiling Expended

Date Closed

Final TR Complete (yes/no)

Total STI Required By TO

Total STI Produced Under TO to date

STI Uploaded to DTIC

STI Not Suited for Upload to DTIC**

* Inactive TOs require a detailed explanation of the reason for their inactive status, as well as an assessment of the prospect for the future of the TO (i.e., will it become active; if so, when?)

** Due to classification above SECRET and inability to produce sanitized deliverable or SF298 at SECRET or below (other reasons for not uploading to DTIC must be approved by the DTIC IAC PM)

*** Note: report all TOs, both open and closed; TO shall be reported as “archived” (gray background and move to bottom of list), once all of the following conditions are met:

· Status = closed

· Final TR Complete = yes

· Total STI Produced = STI Uploaded to DTIC + STI Not Suited for Upload to DTIC

1.

Format

a. Please use the above format for reporting

2. Content

a. Content of the STI assessment report should cover all TO Delivery Orders under the same report, with each TO listed on a separate line within the report, per the above format

b. Please report all currently open TOs, as well as any TOs that were open as of the effective date of the revised SOP that first implemented the TO STI Assessment Report requirement (1 July 2009)

i. For TOs closed prior to 1 July 2009, no reporting is required

ii. For TOs closed subsequent to 1 July 2009, reporting is required

iii. For all open TOs, reporting is required

c. Specific definitions of each column are as follows:

i. Delivery Order

1. Please use Task Order number (from the DD Form 1155)

ii. Status

1. Open TOs may be classified as either active or inactive

a. If open and active, please report as “open”

b. If open and inactive, please report as “inactive”

i. Inactive refers to those TOs on which PoP remains, but all funding received has been expended

ii. For inactive TOs, please indicate whether we are expecting additional funding and, if so, when; if no additional funding is expected, inactive TOs are candidates for close-out

2. For closed TOs, please only report those TOs that closed after 1 July 2009

iii. Ceiling Value

1. Ceiling value (total potential value) of TO, as indicated in TO Task Order award

iv. % Ceiling Expended

1. Funds expended divided by ceiling value of each TO

v. Date Closed

1. If TO is closed, identify date DD250 was signed by COR

2. If DD250 has not yet been signed, then TO is still considered open, even if all deliverables have been submitted and PoP has ended

vi. Final TR Complete

1. Has final Technical Report been formally accepted by the COR

a. Acceptance occurs via signature on SF298 or in the TEMS Web Services interface

b. Indicate “Yes” or “No”

vii. Total STI Required by TO

1. Total number of contract deliverables that are considered/expected to be of STI nature (this number will not change)

2. Report all STI deliverables listed on the contract, even if the TO is not fully funded

viii. Total STI Produced Under TO to date

1. Report all STI deliverables formally accepted by the COR

a. Acceptance occurs via signature on SF298 or in the TEMS Web Services interface

2. For STI deliverables with classification or distribution restrictions that preclude upload to DTIC, a sanitized deliverable or sanitized SF298 may be substituted

3. Include STI deliverables that are listed on the TO, as well as ad hoc STI deliverables requested by the RA and already accepted by the COR

a. Acceptance occurs via signature on SF298 or in the TEMS Web Services interface

4. Upon COR acceptance of an STI deliverable, the IAC should make every effort to upload the deliverable into DTIC (via entry into the TEMS Web Services interface) in an expeditious manner, making current STI available to a broad audience

5. IACs should coordinate a mutually agreeable schedule with their COR to ensure review of all deliverables on a quarterly basis, at a minimum; review may occur more frequently, if mutually agreed by the IAC and COR

ix. STI Uploaded to DTIC

1. Report all STI deliverables that have been uploaded to the TEMS Web Services interface as of the date of the report

a. Include only STI deliverables produced and delivered by the IAC under performance of the subject TO

b. Include STI deliverable uploaded during the reporting period, as well as STI deliverables uploaded previously

2. Note: when entering data into the TEMS Web Services interface, for deliverables produced under a TO, please be sure to include the Delivery Order number in the designated field; the TEMS Web Services interface ensures entry in the proper format

x. STI Not Suited for Upload to DTIC

1. If an STI deliverable is not suited for DTIC (due to classification or distribution restrictions) and a sanitized copy or abstract cannot be produced suitable for DTIC, report the deliverable as “not suited for DTIC”

2. DTIC can only accept STI classified SECRET or below (SECRET records are loaded into DTIC Online Classified; unclassified records are loaded into DTIC Online Access Controlled - DOAC)

3. Every effort should be made to produce a sanitized copy of deliverables originally classified above SECRET, or to produce and upload an SF298 classified SECRET or below

4. For IACs that do not have the ability to upload classified STI, if you have deliverables or abstracts of deliverables classified SECRET that are suited for upload to DTIC, please coordinate with your PMA for potential submission to DTIC for upload, on a case-by-case basis

5. Note: for all classified IAC STI included in DTIC Online Classified, any record entered after July 2009 should have a sanitized metadata record produced and included in DOAC (via creation of the record in the TEMS Web Services interface); be sure to follow all applicable IAC, DTIC, and DoD policies and procedures

3. General Clarification

a. Report distribution is to the PMA and COR, per the TO SOP

b. The IAC PMO requests the report by the 23rd calendar day of the month after the end of each quarter (i.e., Jan 23, Apr 23, Jul 23, and Oct 23)

c. The IAC PMO recognizes that the term “deliverable” is subject to interpretation. The STI Assessment Report is focused on deliverables considered of sufficient STI value for upload to DTIC

i. A good rule of thumb is to ask if the potential “deliverable” would be valuable to share with the broader technical community; if the answer is “yes,” then consider it an STI deliverable for the purpose of this report; if the answer is “no,” then do not consider it for this report.

ii. Also, reference the TEMS Data Providers Guide for clarification on what constitutes STI and is appropriate for upload to DTIC

d. The purpose for tracking the # of actual STI deliverables against the # of STI deliverables identified in the contract is to ensure we are providing at least as much STI to the broader community as originally contracted. However, rather than simply tracking the specific deliverables listed on the contract, the IAC PMO recognizes that the RA may substitute ad hoc deliverables for those listed. In short, this report measures STI delivered and made publicly available against STI procured via IAC contracts.

i. The IAC PMO recognizes that upon completion of a TO, especially if the TO is not fully funded, total STI produced may be less than total STI required.

ii. For the above reason, we have included a column to document how much of the ceiling value of the TO has been expended to date

1. The IAC PMO recognizes that, even if 50% of ceiling has been expended, it is likely that less than 50% of STI deliverables have been produced, since many deliverables may be scheduled for later phases of TO completion; however, funding expended is one factor in setting expectations for STI production, especially for TOs that close without being fully funded