Month Progress, Status and Management Report #1

Monthly Progress, Status and Management Report #

Project Title

Monthly Progress, Status, and Management Report #

Issued: Month Day, Year

Covering the Period: Month Day, Year through Month Day, Year

(Financial information through Month Day, Year)

Period of Performance for Current Phase: Month dd, yyyy to Month dd, yyyy

Period of Performance for Program: Month dd, yyyy to Month dd, yyyy

DARPA Program Manager:

Prepared by: Name, Title

Company, Laboratory, or Institution Name

Address Line 1

Address Line 2

Place, State Zip

Email Address

Phone

Team Contact Information Sheet

Primary Organization:

PM

Name

Phone

Mobile

Email

PI

Name

Phone

Mobile

Email

Key Team Member #3

Name

Phone

Mobile

Email

…

Key Team Member #N

Name

Phone

Mobile

Email

Subcontractor #N (Name of Organization)

Key Team Member #1

Name

Phone

Mobile

Email

Key Team Member #N

Name

Phone

Mobile

Email

Program Overview

· Contract/OT vehicle, Phase number, and/or Task Order;

· Current period of performance from effective start date of contract through the latest end date of the awarded phase(s) as per contract documents;

· Expected period of performance from effective start date of contract through the latest end date of all phases;

· Description and scope of project. The description should stand on its own outside of the context of a monthly report, as it may be used to fulfill requests about the contract.

A good summary should not require many edits as the program progresses through the development phases. Most edits will occur at phase endings, e.g., changing tense for a phase description, and perhaps, adding key findings, as a phase is completed, and updating text to be consistent with any updates to the SOW for the new phase.

Progress Since Last Report and Status

Begin with the summary. In a paragraph or two, provide a summary of the program progress compared to the last reporting period. Include a discussion of all activities identified in section ‘Planned Activities for Next Period’ of the previous report. Note that planned activities that did not occur and unplanned activities that did occur also should be explained.

Following the summary, include the table depicted below. Identify significant achievements and challenges encountered during the reporting period by task/subtask numbers delineated in the SOW. Subtask numbering and reporting is encouraged, particularly if provided in the SOW. Also:

· In the Program Progress column, report the most significant progress (achievements, difficulties, and/or set-backs) since the last report (not since program start), measured against program milestones and schedule.

· In the Last Report Status column, verify/update the color code status (see below) to match the previous reporting period and provide the number of months (mo) or weeks (wks) behind or ahead of the last program plan and schedule approved by the COR.

· In the Current Report Status column, set the color code status and the number of months (mo) or weeks (wks) behind or ahead of the last program plan and schedule approved by the COR.

· When a task/subtask is completed, insert the word “Completed” in front of the number of months (mo) or weeks (wks) behind or ahead of the approved program plan at the time the task was completed >

Tasks

Program Progress

Last ReportStatus

CurrentReport Status

1.0

Brief description of task objective

Brief bullets or statements focusing on key accomplishments for the current month

1 moahead

Completed 1 moahead

2.0

Take ABC measurements using bench top apparatus ###

We have made a lot of progress in performing measurements with the bench top apparatus ###, but still have difficulty in acquiring the needed materials – see below.

2 mobehind

3 mobehind

3.0

Task overview

…

3.1

Sub task …

…

3.2

Sub task …

Subcontract delivered subsystem XYZ and

On schedule

1 wkahead

4.0

…

…

5.0

Status color code definitions: R= Task completion at risk, Y= Milestones/Deliverables at risk, G=Task proceeding as planned, B=Task Completed.

Progress Details:

Task 1: … Detail progress or set-backs for each task, as appropriate. You do not need to list tasks for which no action was involved over the reporting period, unless it is related to a set-back or difficulty.

Task 2:

Task 3: …

Task 3.1:

Task 3.2:…

Quantitative Performance Metrics Status

Performance Metric Description

Goal/Objective

Estimated Completion Date

Current Status

Key Issues: Technical, Budget, and Schedule

Issue

Status/Response

T/B/S

Impact

1

Example: Vendor had delay in obtaining starting materials

CLOSED - Materials received and schedule has adequate contingency

S

6/10/11: Issue resolved without impact

2

Work in characterization lab delayed due to water leak

OPEN - Repairs in progress, minimal impact

T,S

1 week delay in results. Contingency adequate

3

Lead engineer retiring

OPEN - Posting out, temp. help available

S

Milestone 5 delayed by 1 months

Impact type: T/B/S means Technical, Budget and/or Schedule;Severity Color Code: R=Project likely at risk, Y= Milestones/Deliverables likely at risk, G=Milestones/Deliverables slightly at risk, B=Issue resolved.

Issue Details:

Issue 1:

Issue 2: …

Issue 3: …

Funding Profile:

Monthly Travel

Trip Destination & Dates

Purpose of Trip

Significant ODCs for Phase(s) in Progress:

Significant ODCs

Item

Cost (in $1000)

Committed (Y/N)

Total

Planned Activities for Next Month

Planned Activities for Next Month

Phase and Task

Planned Activities

I.1

Brief description of task

I.2

I.3

II.1

II.2

Details for Planned Activities

Contract Schedule Status

Program Gantt Chart:

The Contractor shall notify the COR in a timely manner when the Gantt is no longer valid due to changes to the baseline. The Contractor should submit a recommended Gantt update to the COR and may submit it through a Monthly Report, as desired. However, the proposed Gantt shall be clearly labeled as “proposed”. Gantt charts should be formerly reviewed and approved at the beginning of each phase.

Similarly, the Contractor cannot unilaterally extend the period of performance. A period of performance extension requires a contract modification.

Milestone Table:

Milestone

(examples below as suggestions)

Estimated Completion

Date & Status

Notes

1

Significant procurement or acquisition critical to completing phase

April 2019

2

Progress Review A (may have multiple ones per phase, depending on duration)

June 2019

3

Completion of significant Tasks or Subtasks within current phase

4

Deliver Widget A, Phase I Final Report, etc.

5

Complete Phase I

September 2019

See Task A under Section 2 and Key Issue B under Section 4

…

Add as many for the current phase as necessary

Status: R= Milestone will miss estimated completion date, Y= Milestones at risk/behind schedule, G=Milestone on track for estimated completion date, B=Milestone Completed.

Publications, Conference Presentations, Intellectual Property, & Students

· Provide a list of peer-reviewed publications that are in press or have been published, any oral or poster presentations given at a recognized scientific or technical conference, and any patents filed under the project.

· For software development projects, report the number of software licenses that have been distributed per government fiscal year of the project.

· Report any awards given in recognition of scientific achievement (i.e. R&D 100)

· Please populate the table below for postdocs/students supported by (i.e. funded directly by award) and students involved in (i.e. not directly supported but participating) the project broken out by government fiscal year.>

Fiscal Year (FYxx)

Number of Faculty

Number of Postdocs Supported

Number of Students Supported

Number of Students Involved

Organizational Status

Additional Information

2 of 11

Monthly Progress, Status and Management Report #