Common use of DISTRIBUTION OF REPORTS AND DELIVERABLES (REVISED MOD 104 Clause in Contracts

DISTRIBUTION OF REPORTS AND DELIVERABLES (REVISED MOD 104. (a) Provide one copy of the Monthly Project Status Report (D-2) and Contract Project Closure Report (D-22) to the contract specialist designated in Clause G.4, Contract Administration. (b) Provide one copy of Deliverables D-2 and D-22 to the individuals designated in writing as the Contracting Officer's Representative (COR) and the COR Alternate. 1. The Contractor shall submit a monthly Project Status Report (D-2) and hold monthly project review meetings with DOE for the term of the contract. The project status report should include the following information: general project highlights; ISMS status; milestone schedule/status highlights; project risks; technical issues and decisions; QA issues; status of work documents; assessments; contract status; human resource issues/employer relations; work planned; baseline change control log; general issues; baseline milestone schedule/plan; actual milestone schedule accomplishments; and injury/illness data. 2. Cost and schedule performance, milestone status, and financial status must be reported to DOE on a monthly basis using the DOE-approved work breakdown structure elements and data elements for control of project performance. Reports must also include variance analyses and corrective action plans that integrate cost, schedule, and scope if variances exceed DOE- approved reporting thresholds. Analysis of cost and schedule trends, financial status, baseline change control activity, allocation of management reserve, potential problems, and critical issues, and project risks will also be reported. 3. Contractors must submit monthly project performance data no later than CD-2 for projects having a total project cost greater than or equal to $20M. The required project performance data include: ANSI/EIA-748 earned value; earned value time-phased incremental cost and quantity, management reserve; schedule; variance analysis; and risk management data. For firm fixed price contracts, the required project performance data include: schedule activity and relationship, and cost and quantity data (budget, actual, ETC, and EAC) by WBS and OBS. Data must be submitted electronically via the Project Assessment and Reporting System II (PARS II) in accordance with the current version of the “Contractor Project Performance Upload Requirements” document maintained by OECM. Unless OECM has granted a temporary exemption, all requested data must be submitted. The U-233 Project is exempt from reporting risk analysis. Data must be uploaded in PARS-II no later than the last workday of every month, or as otherwise stipulated by the OECM, and must be current as of the previous month’s accounting period closed. Reporting by the contractor may be required earlier than CD-2 as specified by the Contracting Officer. In order to meet the Environmental Management Headquarter’s Schedule for data transfer from PARS-II to IPABS, the earned value data at a minimum must be uploaded in PARS-II by the eighth business day before the end of each month. 4. Schedules shall incorporate a Critical Path Method, and a master project schedule utilizing Primavera P6 software system shall be maintained. 5. Distribution of periodic reporting requirements electronically in addition to a limited formal hardcopy submission is encouraged. 6. A complete, updated forecast of the project cost and schedule for each WBS shall be employed quarterly; and monthly in-depth reviews of cost and progress shall be held with DOE. Estimates at completion and contingency analysis will be used to indicate the financial health of the project. Status information will be provided, as well as an itemization of project concerns and pending changes. 7. Technical performance analyses and corrective action plans must be reported to DOE for variances to the project baseline objectives resulting from design reviews, and component system tests.

Appears in 2 contracts

Sources: Contract, Contract