Exhibit A_CDRL A001 - Status Report.pdf
PDF 206 KB Posted
- Attached to
- Pavement Condition Inspections FY25
- Solicitation number
- FA805125Q4002
About this file
This document is a Contract Data Requirements List (CDRL) for a Monthly Status Report (MSR) associated with the PCI Studies FY25 contract. The CDRL (DD Form 1423-1) outlines specific reporting requirements for a monthly status report to be submitted to the Air Force Civil Engineer Center (AFCEC/COAP).
Key details include monthly submission by the 5th calendar day of each month, electronic submission in MS-Office compatible format, and a comprehensive reporting structure. The report must include a summary of project status, milestone/task progress, technical accomplishments, contract deliveries, testing results, future plans, and any new problems encountered. The report is to be submitted in 8.5 x 11 inch format, with specific sections covering milestone status, contract performance, effort expended, testing data, model completion progress, and outstanding problems with their resolutions.
View the file
Other files
Show all 13
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DD FORM 1423-1, FEB 2001
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
PREVIOUS EDITION MAY BE USED.
Form Approved OMB No. 0704-0188
The 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 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
G. PREPARED BY H. DATE I. APPROVED BY J. DATE
Page of Pages
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
16. REMARKS (Continued)
DD FORM 1423-1, FEB 2001 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-1 (BACK), FEB 2001
| data_item: A001 |
| title: Monthly Status Report (MSR) |
| sub: N/A |
| auth: DI-MGMT-80368A |
| ref: PWS 4.1 |
| req_ofc: AFCEC/COAP |
| dd250: LT |
| appcode: N/A |
| dist: D |
| freq: Monthly |
| asof: As of Award |
| firstsub: See BLK 16 |
| subsub: See BLK 16 |
| addressee1: AFCEC/COAP (COR) |
| draft1: 0 |
| reg1: 1 |
| repro1: 0 |
| addressee2: 772 ESS/PKD (CO) |
| draft2: 0 |
| reg2: 1 |
| repro2: 0 |
| addressee3: |
| draft3: |
| reg3: |
| repro3: |
| addressee4: |
| draft4: |
| reg4: |
| repro4: |
| addressee5: |
| draft5: |
| reg5: |
| repro5: |
| addressee6: |
| draft6: |
| reg6: |
| repro6: |
| addressee7: |
| draft7: |
| reg7: |
| repro7: |
| addressee8: |
| draft8: |
| reg8: |
| repro8: |
| addressee9: |
| draft9: |
| reg9: |
| repro9: |
| addressee10: |
| draft10: |
| reg10: |
| repro10: |
| addressee11: |
| draft11: |
| reg11: |
| repro11: |
| addressee12: |
| draft12: |
| reg12: |
| repro12: |
| addressee13: |
| draft13: |
| reg13: |
| repro13: |
| addressee14: |
| draft14: |
| reg14: |
| repro14: |
| addressee15: |
| draft15: |
| reg15: |
| repro15: |
| addressee16: |
| draft16: |
| reg16: |
| repro16: |
| addressee17: |
| draft17: |
| reg17: |
| repro17: |
| addressee18: |
| draft18: |
| reg18: |
| repro18: |
| addressee19: |
| draft19: |
| reg19: |
| repro19: |
| addressee20: |
| draft20: |
| reg20: |
| repro20: |
| addressee21: |
| draft21: |
| reg21: |
| repro21: |
| addressee22: |
| draft22: |
| reg22: |
| repro22: |
| addressee23: |
| draft23: |
| reg23: |
| repro23: |
| addressee24: |
| draft24: |
| reg24: |
| repro24: |
| addressee25: |
| draft25: |
| reg25: |
| repro25: |
| addressee26: |
| draft26: |
| reg26: |
| repro26: |
| addressee27: |
| draft27: |
| reg27: |
| repro27: |
| addressee28: |
| draft28: |
| reg28: |
| repro28: |
| addressee29: |
| draft29: |
| reg29: |
| repro29: |
| addressee30: |
| draft30: |
| reg30: |
| repro30: |
| addressee31: |
| draft31: |
| reg31: |
| repro31: |
| addressee32: |
| draft32: |
| reg32: |
| repro32: |
| addressee33: |
| draft33: |
| reg33: |
| repro33: |
| addressee34: |
| draft34: |
| reg34: |
| repro34: |
| addressee35: |
| draft35: |
| reg35: |
| repro35: |
| addressee36: |
| draft36: |
| reg36: |
| repro36: |
| addressee37: |
| draft37: |
| reg37: |
| repro37: |
| addressee38: |
| draft38: |
| reg38x: |
| repro38: |
| total_draft: 0 |
| total_reg: 2 |
| total_repro: 0 |
| remarks: 1. Reference documents. None. |
2. Format. The Status Report shall be in the following format.
2.1. Identification. The data indicated below shall be contained on a title page or on the first page of the report.
a. Title/identification of the system/component/program/project.
b. Type of report (e.g., monthly, interim, final).
c. Period covered by the report.
d. Contract number.
e. Preparing activity or contractor’s title.
f. Security classification, when required.
g. Distribution Statement.
2.2. Page size. The report shall be on 8 ½ by 11 inch (metric A4) paper.
3. Content. The report shall contain the following:
3.1. Summary. The summary shall include a brief statement of the overall project status, covering the accomplished technical activities and development, objectives of efforts, summary results of efforts, identification of major problems/deficiencies with impact, and recommended solutions.
3.2. Body of report. The Status Report shall contain the following items, where applicable:
3.2.1. Milestone/task status. The status of each milestone/task as defined by the performance work statement or contract, as applicable:
a. A statement as to whether or not the program/project/task is on schedule; if not, the effort planned to meet the schedule shall be indicated. Include an overall status of each milestone, task, or unit of work. Include update schedule sheets, milestone charts, or task synopsis sheets identifying phase of task and percentage of completion of each task, technical instruction, or order.
b. A comparison of achieved end-product performance capabilities projected against contract baseline values, requirements, or allocations.
c. Effort expended on each task to date, and a brief description of technical developments and accomplishments.
d. Key dates in any testing program and description of tests performed and significant test results. If applicable, a description of the amount and type of down time on the equipment or system under test.
e. A list of all models completed and a brief description of each item. For models in process, provide estimated dates for model completion.
f. A narrative of outstanding problems existing as of the previous status report, and their resolution status.
| group: |
| total_price: |
| prep_name: |
| line_item: TBD |
| exhibit: A |
| xtdp: Off |
| xtm: Off |
| othercat: MGMT |
| system: PCI Studies FY25 |
| ctr_no: TBD |
| contr: TBD |
| remarksb: g. New problem areas encountered or anticipated, their effect on the overall work |
effort/project and steps being taken to remedy problem situations.
h. Significant results of conferences, trips, or directives for the Contracting officer’s representatives.
i. Any other information which may cause significant changes in the program schedule.
3.2.2. Future plans. Summary of future plans, recommendations and proposals both for the next reporting period and for any long term plans.
3.2.3. Itemized man-hours and costs. Itemized man-hour and cost expenditure incurred for the reporting period by category and task, total contractual expenditures, and funds remaining as of the reporting date.
3.2.4. Contract deliveries status. The status of each deliverable end item, including data deliverables, as required by the contract. Provide item and contract identification, shipping/transmittal data, acceptance status, security classification, and schedule due date information.
3.2.5. Report preparer. Name of person(s) preparing report and telephone number(s).
3.3. Appendices. Appendices where applicable, for tables, references, charts, or other descriptive material. Each appendix shall be identified and referenced in the appropriate area of the report.
Additional Remarks:
BLK 9: The contractor shall mark all the data IAW DoDI 5230.24 and the following Distribution B. Distribution authorized to U.S Government Agencies only (reason)(date of determination). Other requests for this document shall be referred to AFCEC/COAP, 139 Barnes Drive Suite 1, Tyndall AFB, FL 32403
BLK 12 and 13: Report must be submitted by the 5th calendar day of each month. If the 5th calendar day falls on a weekend or federal holiday, submit the report on the next working day.
BLK 14: Submit electronically in the format compatible with MS-Office for Windows.
4. END OF DI-MGMT-80368A
| Page2: |
| Reset: |
| prep_date: |
| app_by: |
| app_date: |
| Page: |
| of_pages: |
| app: Adobe Professional 8.0 |
File details come from the government source that posted it. Updated .