B08_Attachment 3 - CDRL A001 Contractors Progress Status and Management Report.pdf

CONTRACT DATA REQUIREMENTS LIST (CDRL)

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 the Morris K. Udall and Steward L. Udall Foundation, 130 S. Scott Avenue, Tucson, AZ 85701. Please DO NOT RETURN your form to either of these addresses. Send completed form to the government Issuing Contracting Officer for the Contract/PR No. in Block E.

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

TDP TM OTHER_X

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

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

A001

Contractor’s Progress, Status and Management Report

Monthly Progress Report

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

NA TOTAL PRICE

7. NOT USED 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

REQUIRED See Block 16

1st reporting period after start date

a. ADDRESSEE

b. COPIES

8. NOT USED 11. AS OF DATE 13. DATE IF SUBSEQUENT SUBM. final See Block 16 draft reg repr

16. REMARKS NCECR PM 0 1

The Contractor’s Progress, Status, and Management Report indicates the progress of work and the status of the program and of the assigned tasks, reports costs, and informs of existing or potential problem areas for the contract.

The progress report for this contract is due not later than (NLT) 10 working days following the end of each reporting period. The reporting period shall coincide with the contractor’s normal ‘monthly’ accounting and billing cycle. E-Mail addresses for distribution will be provided with the contract.

COR 1

1. Format: All reports will be developed in Microsoft Word and submitted in softcopy to the NCECR PM and COR. The document will not be locked or protected in any fashion that would prevent text to be copied or edited by the government after delivery.

(a) Report shall be written for printing on 8 1/2" X 11" standard letter size paper (Portrait orientation) although necessary attachments, figures, and sketches may be submitted on in a size/orientation that best displays the information being presented.

(b) Font shall be Times New Roman, size 12.

(c) Each page beyond the first page shall have a header identifying the site name or report title and date of report

(d) Report shall be grammatically correct.

(e) All attachments shall be identified and referenced in the text of the report.

2. Title page:

A. Title. The title shall identify the subject of the report, program name, or task.

B. Name of contractor. The name of the contractor preparing the report.

C. Contract number. The procurement instrument identification number.

D. Key person. The individual assigned to the task or who produced the report.

E. Reporting period. The dates the reporting period begins and ends.

3. Content.

(a) Description of the progress made during the reporting period;

(b) Results, positive or negative, obtained related to previously-identified problem areas, with conclusions and recommendations;

(c) Any significant changes to the contractor’s organization or method of operation or to the project management network;

(d) Problem areas affecting technical or scheduling elements, with background and any recommendations for solutions beyond the scope of the contract;

(e) Problem areas affecting cost elements, with background and any recommendations for solutions beyond the scope of the contract;

(f) log of WG / Team / Planning calls attended;

(g) Contract hours expended on this contract by task and by contractor personnel;

(h) Roll up of TDY/travel funds expended and remaining;

(i) Any other costs (ODCs, etc.) incurred for the reporting period and total contractual expenditures and remaining funds as of reporting date;

(j) Any trips and significant results;

(k) Record of all significant telephone calls and any commitments made by telephone;

(l) Plans for activities during the following reporting period;

(m) Name and telephone number of preparer of the report;

(n) Appendices for any necessary tables, references, photographs, illustrations, and charts.

15. TOTAL --------------- > 0 2

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

Mitch Chrismer 4/19/2021

UDALL Form 1423-1, FEB 2021 Previous editions are obsolete Page 1 of 5 Pages

Project Status Report Project Name:

Week To

Manager Report Date

Status Summary

Percent Complete 5% Budget Status Y

1. Key Project Performance Metrics

Budget to Actual Performance

Current Month Budget Cumulative Budget Current Month Actual Cumulative Actual

Current Month Budget less Actual Cumulative Budget less Actual Percent Deviation this Month

Percent Deviation Cumulative

Forecasts EAC (Estimate at Completion) BAC (Budget at Completion)

2.2 Project Manager’s Outlook Summary

2. Project Manager’s Report

2.1 Project Manager’s Status Summary

3. Activities/Accomplishments/Decisions This Week

3.1 Planned Activities Brought Forward - DD/MM/YY to DD/MM/YY

WBS Activity Description

1.3.2

1.3.3

1.3.4

3.4 Planned Activities For The Next Week - DD/MM/YY to DD/MM/YY

WBS Activity Description Expected Target Delivery Date

1.3.2 DD/MM/YY

1.3.3 DD/MM/YY

1.3.4 DD/MM/YY

5. Risk and Issue Logs

5.1 Issue Log

L og

N o

Description

T yp e

Resolution Strategy

Im pa ct

O w ne r

Identified

Target Resolution

Days

Overdue

Issue Type Key

B – Business P – Project D – Development

5.2 Risk Log

L og

N o

Description

T yp e

Mitigation Strategy

Se ve ri ty

Pr ob ab ili ty

O w ne r

Identified

Target

Resolution

Days Overdue

6.0 Outstanding Decisions and Sign-Offs

Decision/Sign-Off Responsibility Due

Probability Key Impact Key

High (H) – 90% Probability of risk being realized. High (H) - Critical Path Risk. If realized, the resulting issue would immediately impact cost / project delivery dates.

Medium (M) – 75% Probability of risk being realized.

Medium (M) – If realized, the resulting issue would cause slippages in deliverable release dates but would have an immediate effect on overall cost /project delivery dates.

Low (L) – 50% Probability of risk being realized. Low (L) – If realized, the resulting issue would not impact delivery dates but could impact the quality of deliverables.