Ex_A_CDRL_DDForm1423_A009-012.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

DATA ITEM DESCRIPTION

Title: CONTRACT STATUS REPORT

Number: DI-MGMT-81991 Approval Date: 20160119

AMSC Number: N9568 Limitation: N/A

DTIC Applicable: N/A GIDEP Applicable: N/A

Office of Primary Responsibility: SH Project Number: MGMT-2015-004

Applicable Forms: N/A

Use/Relationship: Contract Status Report provides the progress of work performed and the status of all program assigned tasks, cost and information and management of existing or potential problem areas.

This Data Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID supersedes DI-MGMT-81928.

Requirements:

1. Format. The Contract Status Report shall be in a format similar to that of Figures 1, 2, and 3 of this DID.

2. Content. The report shall contain a cover sheet identifying the following:

a. Title of the report

b. Contractor’s name and address

c. Contract Number

d. Date of report and period by the report

e. Data Item Number listed on the CDRL DD FORM 1423-1

2.1 The report shall include results positive and negative related to previously identified problem areas, with conclusions and recommendations.

2.2 The Report shall include an significant changes to the Contract’s organization, method of operation, and the project management network.

2.3 The report shall identify problem areas affecting cost elements, technical or scheduling elements, and shall in background and any recommendations for solutions beyond the scope of the contract for the following items:

a. Funding issues

(1) Shortfalls

(2) Overfunding

b. Task Area Issues

Source: https://assist.dla.mil -- Downloaded: 2017-03-21T19:24Z Check the source to verify that this is the current version before use.

DI-MGMT-81991

2.4 The report shall contain cost curves showing actual projected conditions throughout the contract, any cost incurred for the reporting period and total contractual expenditures as of the reporting date.

2.5 The report shall contain Man-hours expended for the reporting period and cumulatively for the contract for the following areas:

a. Trip(s) outside the local area, site visited and purpose

b. Contract schedule status

c. Plans for activities during the following reporting period

d. Name and telephone number of signer of the report

e. Appendixes for any necessary tables, references, photographs, illustrations, and charts

2.6 The report shall contain all of the information specified in Figures 1, 2, and 3, and shall identify employee movement, color coded and highlighted in the comments column.

2.7 The report shall identify the following:

a. Title i.e.: Professional Support Services for the Program Executive Office (PEO)

Integrated Warfare System (IWS)

b. Contract Number

c. CLIN Number

d. Latest Contract Modification (# and Date)

e. Period of Performance

f. Reporting Period

g. Contractor’s POC

h. Government PM

i. Government COR

2.9 Financial/Labor Data. The report shall also include the following:

a. Contract Value

b. Funded to date

c. Cost of work performed during period (period to be defined as CY)

d. Planned travel for the upcoming Calendar Month to include location, number of contractor personnel and purpose

e. Actual: Monthly Hours Burned by each contractor/employee

f. Invoice Date/Amount/Number

3.0 Summary: The report shall contain a summary by Project, Work Area and Technical

Instruction.

3.1 A Description of the progress made during the reporting period, the value-added tasks performed by the prime contractor shall be specifically addressed, key and non-key personnel shall be clearly identified when work is performed by a subcontractor and key and non-key personnel performing the tasks shall be identified.

3.2 The status of all assigned deliverables, including title, CDRL number, due date, date delivered, Contractor point of contact and title of deliverable(s) shall be included.

3.3 The report for each contract period shall include a cumulative list of all deliverable items provided.

Task Sub-task Nr. Task Description Customer Name/Employee

Labor or ODCs (Fully

Burdened) Value Funded to Date

Funding

Required to End of CY

(Cost)

Required to End of CY

(Fixed Fee)

Required to

End of CY

(Total)

ACTUAL: Mthly

Hours Burned Invoice Number Invoiced Amount Invoiced To Date

Date Sub-contractor invoice approved by Corp

Recent Actual

Payments to Sub-

Contractor

Red indicates costs have exceeded funding

Yellow indicates costs are close to exceeding funding.

1.1 1.1.1

NMCI, NAVSEA CIO and Enterprise primary coordinator Jane Doe Labor

ODCs

1.1.2 Assist in Strategic Planning John Smith Labor

1.1.3 Portfolio Management. John Doe Labor

3.1 3.1.1 ACTD Operations Specialist support John Doe Labor

Totals

FINANCIAL/LABOR HOUR DATA BY TASK- FIGURE 1

WORK COMPLETED BY TASK

CLIN/SLIN ACRN PR Number Ref Doc/ACRN MOD Appropriation Subhead OBJ PARM RFM AAA TT PPA Project Unit Funded Expended Balance

Totals $ - $ - $ -

Grand Totals $ - $ - $ -

WORK COMPLETED BY CLIN/SLIN - FIGURE 2

STAFFING PLAN - FIGURE 3

NAME/EMPLOYEE LABOR TASK AREA CONTRACTOR / COMPANY GOVERNMENT FTE HOURS COMMENT

CATEGORY SUPPORTED SUBCONTRACTOR NAME SITE

Task 1 -

Task 2 -

Task3 -IWS Technical - Provide Support to PEO IWS Advanced Technology

End of DI-MGMT-81991

Literature Search

Instructions for Completing a Literature Search:

The initial literature search is performed by the Government during the development of the task order (TO) PWS (pre-award) and is used in shaping the PWS. Literature searches are performed to identify what, if any, STI already exists relative to the new TO effort being pursued. The results of the intial pre-award search will be shared with the TO contractor at the post-award Orientation conference. Thereafter, the contractor's annual searches are to be performed in DTIC Online Access Controlled (DOAC), IAC Quad Charts (within DoD Techipedia), and any other database/system deemed pertinent by the contractor and will build upon the results of the initial literature search. Contractors should rely on their keen search skills, which should blend strategic "keywords" and/or "strings of keywords" during their searches. In situations where an initial search yields too many hits, the contractor should refine their search criteria and search again (e.g., "HH-60G Pave Hawk and survivability" may yield too many hits - - "HH-60G Pave Hawk survivability AND RPGs" may be necessary). In circumstances such as this, please include only the final search term(s) that were used. Identifying and building upon an existing knowledge base is critical to the IAC Program. The contractor, in performing the TO, is expected to fill gaps in the STI literature base as it performs the TO. The completed literature search template is a deliverable as stated in the TO PWS.

Filling Out the Literature Search Template (below) Step 1: Identify strategic keywords and/or a string of keywords to use during your search. (Note: You must have at least one keyword or one string of keywords per PWS task; searches need not be performed for mandatory tasks 1 [post-award orientation/kick-off] and 2 [gap analysis].)

Step 2: Search DOAC using the keywords identified in Step 1. DOAC searches should cover the entire database, not just the IAC documents. Enter the number of returns for each search (separately) under Total Hits/DOAC.

Step 3: Analyze the results from your search and identify any relevant STI (this should be a subset of the number of total hits). Enter the number of relevant results under Relevant STI/DOAC.

Step 4: Enter any relevant comments related to your search Step 5: Repeat Step 2-4 for DoDTechipedia and any other database/systems deemed pertinent by the IAC; identify other databases in the comments field. (Note: Searches in DoDTechipedia should search all IAC Quad Charts, not just the Quad Charts associated with the IAC performing the TAT. Access to IAC Quad Charts is granted on an individual basis; contact the IAC PMO to request access.)

Literature Search Template (with sample entries)

Total Hits Relevant STI

SOW Paragraph Final Search Term(s) DOAC IAC Quad Other DOAC IAC Quad Other Comments

SOW Task 3.3 HH-60G Pave Hawk Survivability AND RPG 11 0 0 0 0 0 No relevant STI currently exists in relation to Task 3.3

SOW Task 3.4 RQ-1 Predator Survivability AND RPG 27 2 0 3 0 0 Article in the Fall 2005 Aircraft Survivability Newsletter discussing lessons learned related to RQ-1 Predator Survivability and RPG attacks during the GWOT.

SOW Task 3.5 RQ-1 Predator Impact Sensors GWOT 53 2 3 0 0 0 No relevant STI currently exists in relation to Task 3.5

Gap Analysis

Instructions for Completing a Gap Analysis:

The contractor shall maintain close coordination with Basic Center Operations (BCO) personnel/resources, to ensure task order (TO) performance builds on the breadth of the BCO knowledge base. TO performance provides an opportunity to validate BCO research/Scientific and Technical Information (STI) in a specific, operational context. Further, TO operational requirements provide real-time assessment of areas where STI is most needed. This report documents the relevance of BCO STI resources in supporting TO requirements, as well as to identify potential gaps in the BCO knowledge base based on TO requirements. The gap analysis builds on the STI literature search performed under the previous tab. The gap analysis is performed annually, as stated in the TO PWS. It identifies, by PWS task, how much STI (gathered from DOAC, IAC Quad Charts in DoDTechipedia, and other sources) has been actually used to inform the work performed under the current TO. Provide the number of relevant STI search results (from the literature search, or subsequent post-award searches) that was actually employed in executing the PWS task. For each search term, highlight noteworthy examples of how STI significantly contributed to the performance of that particular task . For each task, identify any perceived gaps in the knowledge base (e.g., the task required information on XYZ, but the literature search did not turn up STI on XYZ). These "STI Gaps" serve as a signal for the BCO that they may need to build knowledge in XYZ (i.e., establish focused STI collection for "XYZ"), especially as the BCO notices trends where similar entries are made in this column across multiple task orders.

Filling Out the Gap Analysis Template (below) Step 1: Copy and paste the results from the literature search into the first 9 columns of the Gap Analysis template.

Step 2: In each row, identify how much STI has been actually employed in executing the SOW tasks under the current TAT; this will be a subset of "Relevant STI" discovered during the literature search. In cases where additional STI was discovered post-award, insert a new row to record the gap analysis data (enter SOW paragraph, but leave columns B through I blank).

Step 3: In the "Comments on STI Used" section, highlight noteworthy examples of how the STI significantly contributed to the performance of that particular task.

Step 4: Identify any perceived gaps in the knowledge base and enter them into the "STI Gaps" section. Perceived gaps occur when the task required information on a particular topic, but the literature search did not uncover any STI on that topic. A gap may also occur on a topic not covered by the literature search, but for which the information need became apparent during task execution.

Gap Analysis (with sample entries)

Total Hits Relevant STI Gap Analysis

PWS Paragraph Search Term DOAC IAC Quad Other DOAC IAC Quad Other Comments STI Used Comments on STI Used STI Gaps

PWS Task 3.3 HH-60G Pave Hawk Survivability AND RPG 11 0 0 0 0 0 No relevant STI currently exists in relation to Task 3.3 0 n/a • no STI found on main search term, "HH-60G Pave Hawk Survivability AND RPG"

PWS Task 3.4 RQ-1 Predator Survivability AND RPG 27 2 0 3 0 0 Article in the Fall 2005 Aircraft Survivability Newsletter discussing lessons learned related to RQ-1 Predator Survivability and RPG attacks in Iraq/Afghanistan. 3 • previous case studies on RPG attacks against RQ-1 Predator used to develop updated tactics for pilots • found no data on equipment recovery in event of downed RQ-1 Predator due to RPG attack

PWS Task 3.5 RQ-1 Predator Impact Sensors GWOT 53 2 3 0 0 0 No relevant STI currently exists in relation to Task 3.5 0 n/a • no STI found on main search term, "RQ-1 Predator Impact Sensors GWOT"