**Proposed Data Elements for PARS II**

Revised: January 2, 2009 -- Version 2.1

# [Overview]{.underline}

The PARS II application will collect two major types of data from DOE
Field Site and DOE Headquarters locations. The two types of data
are![](media/image1.wmf) called: (1) **Oversight and Assessment Data**
and (2) **Contractor Project Performance Data** and are designed to
provide information to support for the concepts and data elements
represented by the DOE EVMS Gold Card[^1]. A reproduction the relevant
section of the Gold Card appears to the right.

**Overhead and Assessment Data**, such as monthly assessments,
contingency, profit/fees, other direct costs, performance baseline,
milestone completion dates, contractor certification status, total
project cost and other data elements will be collected from Federal
Project Directors, Program Office Analysts and OECM Analysts using the
PARS II Oversight and Assessment module. This type of data is often
referred to as summary level data and is related to the items shown in
the red-shaded portion the DOE EVMS Gold Card.

**Contractor Project Performance Data**, such as the management reserve,
performance measurement baseline, contractor's earned value data,
schedule data, variance analysis reports and risk logs will be collected
from the site contractor's earned value management system using the PARS
II Contractor Project Performance "project upload file function". The
contractor will use this functionality, on a monthly basis, to send
(i.e., upload) files containing earned value data, schedule data,
management reserve, variance reports and risk to the PARS II server at
Headquarters These types of data elements are related to the blue-shaded
portion the DOE EVMS Gold Card.

PARS II will store both types of data in the database and will integrate
them, for reporting purposes, using the Project ID as the common data
element.

Please note that the names used to describe of database tables and data
elements in this document are based on terms commonly used by Department
of Energy federal and contractor personnel, and are based on the
language found in relevant publications such as DOE Orders, Guides,
Manuals and PARS 1 documentation. PARS II will be implemented using the
Dekker PMIS COTS product, which uses its own internal database table and
data element naming conventions. Therefore, when implemented, PARS II
may not use many of the table names and data element names described
below. However, Dekker software will be modified to provide PARS II
users with a "data aliasing" feature that translates Dekker terminology
into DOE terminology.

# [Database Tables]{.underline} {#database-tables .Style-Heading-1-+-Arial-Bold-Light-Blue}

The database for PARS II is being designed to store, for each project,
**oversight and assessment data** and **contractor project performance
data**. The database will contain many tables that can be categorized as
either Reference Tables or Data Tables. The information stored in
Reference Tables is static in nature (e.g., not updated very often) and
contains data such as Contacts, Sites, Program Office Codes, Group
Access Rights, etc. Data elements in these Reference Tables will be used
by PARS II for look-up or data validation purposes (e.g., using
drop-down boxes). Information stored in Data Tables is dynamic in nature
(e.g., is updated daily, weekly) and contains items such as the Projects
Table, Narratives Table, Earned Value Table, Budget Profile Table, etc.

The sections below describe the information contained in the Reference
Tables, the Data Tables and the entire list of data elements for PARS
II. Please note that other tables and data elements may be added to this
document as a result of information obtained from Discovery Sessions and
feedback from stakeholders.

## Reference Tables {#reference-tables .Style-Heading-2-+-12-pt-Not-Italic}

*The following list of Reference Tables will be included in the PARS II
database.*

+---+-------+---------------------------------+---+---------------------+
| 1 | Refe  | Description of Reference Table  |   |                     |
| . | rence |                                 |   |                     |
|   | Table |                                 |   |                     |
|   | Name  |                                 |   |                     |
+===+=======+=================================+===+=====================+
| 2 | Cal   | An electronic calendar within   |   |                     |
| . | endar | PARS II to be used for          |   |                     |
|   | Table | calculating schedules,          |   |                     |
|   |       | displaying months, days, years, |   |                     |
|   |       | selecting date range values on  |   |                     |
|   |       | screens, etc.                   |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 3 | Con   | The list of valid contracts     |   |                     |
| . | tract | types, such as Fixed Price,     |   |                     |
|   | Types | Cost Reimbursement. \[to be     |   |                     |
|   | Table | implemented as a dropdown box   |   |                     |
|   |       | on PARS screens\]               |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 4 | Contr | The list EV certification       |   |                     |
| . | actor | status codes that apply to the  |   |                     |
|   | EVMS  | contractor, such as: Certified, |   |                     |
|   | Cer   | Reviewed, Not Reviewed          |   |                     |
|   | tific |                                 |   |                     |
|   | ation |                                 |   |                     |
|   | S     |                                 |   |                     |
|   | tatus |                                 |   |                     |
|   | Codes |                                 |   |                     |
|   | Table |                                 |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 5 | Contr | The list of prime contractor    |   |                     |
| . | actor | names \[dropdown box\]          |   |                     |
|   | Names |                                 |   |                     |
|   | Table |                                 |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 6 | Contr | A brief list that identifies    |   |                     |
| . | actor | the type of contractor, such    |   |                     |
|   | Types | as: M&O, M&O Subcontractor      |   |                     |
|   | Table | \[dropdown box\]                |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 7 | FPD   | The list of certification level |   |                     |
| . | Cer   | codes that pertain to the FPD,  |   |                     |
|   | tific | such as: Level 4, Level 3,      |   |                     |
|   | ation | Level 2, Level 1                |   |                     |
|   | Level |                                 |   |                     |
|   | Codes |                                 |   |                     |
|   | Table |                                 |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 8 | FPD   | The list of certification       |   |                     |
| . | Cer   | status codes that apply to the  |   |                     |
|   | tific | FPD, such as: Certified, Not    |   |                     |
|   | ation | Certified, Under Review         |   |                     |
|   | S     |                                 |   |                     |
|   | tatus |                                 |   |                     |
|   | Codes |                                 |   |                     |
|   | Table |                                 |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 9 | Man   | The names and acronyms of all   |   |                     |
| . | aging | DOE Program Offices and Staff   |   |                     |
|   | Pr    | Offices, such as: EM, NNSA, NE, |   |                     |
|   | ogram | Science, MA, OCIO \[dropdown    |   |                     |
|   | Of    | box\]                           |   |                     |
|   | fices |                                 |   |                     |
|   | Table |                                 |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | Mile  | The types of milestones to be   |   |                     |
| 0 | stone | placed in the Milestone Table,  |   |                     |
| . | Types | such as Regulatory Milestones,  |   |                     |
|   | Table | Key Milestones, EM Operations   |   |                     |
|   |       | Funded Milestones, Other        |   |                     |
|   |       | Milestones                      |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | Narr  | A list of the various types of  |   |                     |
| 1 | ative | narratives that to be written   |   |                     |
| . | Types | by the FPD, OECM, Program       |   |                     |
|   | Table | Office Analyst, such as: Status |   |                     |
|   |       | Assessment, Progress            |   |                     |
|   |       | Assessment, Corrective Action   |   |                     |
|   |       | Plan, Upcoming Events,          |   |                     |
|   |       | Narrative to Achieve Green.     |   |                     |
|   |       | \[dropdown box\]                |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | Pr    | The list of codes that identify |   |                     |
| 2 | oject | the current "activity status"   |   |                     |
| . | Act   | of a project, such as: Active,  |   |                     |
|   | ivity | Completed CD4, Financial        |   |                     |
|   | Codes | Closeout, On-Hold. \[dropdown   |   |                     |
|   | Table | box\]                           |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | Pr    | The list of categories for a    |   |                     |
| 3 | oject | project, such as: stand-alone   |   |                     |
| . | Cat   | project, discrete sub-project,  |   |                     |
|   | egory | sequential segment project      |   |                     |
|   | Codes | \[dropdown box\]                |   |                     |
|   | Table |                                 |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | Pr    | The list of cities, states, and |   |                     |
| 4 | oject | zip codes where the project is  |   |                     |
| . | Loca  | located. \[dropdown box\]       |   |                     |
|   | tions |                                 |   |                     |
|   | Table |                                 |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | Pr    | The list of valid DOE Site      |   |                     |
| 5 | oject | Codes and Site Descriptions     |   |                     |
| . | Sites | where the project is located.   |   |                     |
|   | Table | \[dropdown box\]                |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | Pr    | The list of project types, such |   |                     |
| 6 | oject | as: System, Facility            |   |                     |
| . | Type  | Construction, Infrastructure    |   |                     |
|   | Codes | Improvements, Restoration,      |   |                     |
|   | Table | Disposition, etc. \[dropdown    |   |                     |
|   |       | box\]                           |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | User  | A table that lists the "access  |   |                     |
| 7 | A     | rights" available to groups of  |   |                     |
| . | ccess | users (see User Groups) who     |   |                     |
|   | R     | will use PARS II. Examples of   |   |                     |
|   | ights | access rights include: READ     |   |                     |
|   | Table | ONLY, ADD, CHANGE, DELETE.      |   |                     |
|   |       | Access rights within the Dekker |   |                     |
|   |       | COTS software extends to the    |   |                     |
|   |       | data element level. \[dropdown  |   |                     |
|   |       | box\]                           |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | User  | The list of valid user groups,  |   |                     |
| 8 | G     | such as OECM Analyst, FPD,      |   |                     |
| . | roups | Contractor Project Control,     |   |                     |
|   | Table | Contractor Project Manager,     |   |                     |
|   |       | Program Office Project Manager  |   |                     |
|   |       | and other groups. \[dropdown    |   |                     |
|   |       | box\]                           |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 1 | Users | The list of all users who may   |   |                     |
| 9 | (Cont | access PARS and contains        |   |                     |
| . | acts) | information such as: user name, |   |                     |
|   | Table | user title, user group, user    |   |                     |
|   |       | location (building, city, state |   |                     |
|   |       | zip), user work phone number,   |   |                     |
|   |       | user email address \[dropdown   |   |                     |
|   |       | box\]                           |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 2 | Color | A list of status indicators, to |   |                     |
| 0 | S     | be used on screens and reports, |   |                     |
| . | tatus | indicating the health of the    |   |                     |
|   | Indic | project. Color indicators are:  |   |                     |
|   | ators | Red, Yellow and Green and are   |   |                     |
|   |       | also associated with control    |   |                     |
|   |       | limit data elements. \[dropdown |   |                     |
|   |       | box\]                           |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 2 | Pr    | Contains the list of the valid  |   |                     |
| 1 | oject | types of upload files to be     |   |                     |
| . | U     | sent from sites, such as: X12   |   |                     |
|   | pload | EV, Time-Phased EV, Schedule,   |   |                     |
|   | File  | Variance, Management Reserve,   |   |                     |
|   | Types | Risk, Other                     |   |                     |
|   | Table |                                 |   |                     |
+---+-------+---------------------------------+---+---------------------+
| 2 | Other | To be determined during         | P | Contains a list of  |
| 2 | T     | discovery process.              | r | the various types   |
| . | ables |                                 | o | of upload files to  |
|   |       |                                 | j | be received from    |
|   |       |                                 | e | sites, such as: X12 |
|   |       |                                 | c | EV Type,            |
|   |       |                                 | t | Time-Phased EV      |
|   |       |                                 | U | Type, Schedule      |
|   |       |                                 | p | Type, Variance      |
|   |       |                                 | l | Type, Management    |
|   |       |                                 | o | Reserve Type, Risk  |
|   |       |                                 | a | Type, Other         |
|   |       |                                 | d |                     |
|   |       |                                 | F |                     |
|   |       |                                 | i |                     |
|   |       |                                 | l |                     |
|   |       |                                 | e |                     |
|   |       |                                 | T |                     |
|   |       |                                 | y |                     |
|   |       |                                 | p |                     |
|   |       |                                 | e |                     |
|   |       |                                 | s |                     |
|   |       |                                 | T |                     |
|   |       |                                 | a |                     |
|   |       |                                 | b |                     |
|   |       |                                 | l |                     |
|   |       |                                 | e |                     |
+---+-------+---------------------------------+---+---------------------+

##  Data Tables {#data-tables .Style-Heading-2-+-12-pt-Not-Italic}

*The table below lists and describes each the Data Table.*

+---+-----------+--------------------------------------------------------+
| 1 | Data      | Description of Table                                   |
| . | Table     |                                                        |
|   | Name      |                                                        |
|   |           |                                                        |
+===+===========+========================================================+
| 2 | At        | The electronic file or files "attached" by the         |
| . | tachments | operator during a data entry session, to include       |
|   | Data      | documents such as: assessments, safety documents,      |
|   |           | project approval documents, project plans, project     |
|   |           | design documents, etc.                                 |
+---+-----------+--------------------------------------------------------+
| 3 | Audit Log | Log files, available to the PARS System Administrator, |
| . | File Data | that show history transactions associated with data    |
|   |           | entry and internal workings of the system. With regard |
|   |           | to all PARS data entry functions, log files must show  |
|   |           | who-changed-what-and-when. There will be several       |
|   |           | different types of audit log files.                    |
+---+-----------+--------------------------------------------------------+
| 4 | Budget &  | A table containing, for each fiscal year, the funding  |
| . | Funding   | request and sources of funding to be used by the       |
|   | Profile   | project. Data elements include the project's           |
|   | Data      | Performance Baseline and funding sources from the DOE  |
|   |           | Integrated Priority List, OMB and Congress. The makeup |
|   |           | of the Budget Profile table for PARS II is currently   |
|   |           | being discussed at OECM.                               |
+---+-----------+--------------------------------------------------------+
| 5 | C         | Contains information about each contractor's EVMS      |
| . | ontractor | certification status / level / date of certification.  |
|   | EVMS      |                                                        |
|   | Cert      |                                                        |
|   | ification |                                                        |
|   | Status    |                                                        |
|   | Data      |                                                        |
+---+-----------+--------------------------------------------------------+
| 6 | FPD       | Contains current and historical information on the     |
| . | Cert      | FPD's certification process, showing current status,   |
|   | ification | certification level and status dates (history).        |
|   | Status    |                                                        |
|   | Data      |                                                        |
+---+-----------+--------------------------------------------------------+
| 7 | KPP Data  | A table that contains a list of all the KPPs for the   |
| . |           | project, including the KPP ID, KPP Description and KPP |
|   |           | Narrative                                              |
|   |           |                                                        |
+---+-----------+--------------------------------------------------------+
| 8 | Milestone | A table that contains data for the milestones and      |
| . | Data      | critical decisions to be associated with each project  |
|   |           | and includes the following data elements: Milestone    |
|   |           | ID, Milestone Name, Milestone Type (e.g., CD, Key, EM, |
|   |           | Other), Milestone Narrative, Milestone Planned Date,   |
|   |           | Milestone Actual Date.                                 |
+---+-----------+--------------------------------------------------------+
| 9 | N         | This table contains written text for each type of      |
| . | arratives | narrative (see Narrative Types Table), as written by   |
|   | Data      | the FPD, Program Office Analyst, OECM Analyst. Each    |
|   |           | narrative must also be associated with the fiscal      |
|   |           | year, fiscal month and calendar date that the          |
|   |           | narrative was written. This table must also identify   |
|   |           | the Type of Narrative and name and title of the author |
|   |           | who wrote the narrative.                               |
+---+-----------+--------------------------------------------------------+
| 1 | Pe        | A history file of changes made to the Performance      |
| 0 | rformance | Baseline, containing the Baseline Change Number,       |
| . | Baseline  | Baseline Change Title, Baseline Change Date, Approval  |
|   | (PB)      | Authority, Narrative, etc. The table also includes a   |
|   | Change    | snapshot of selected data elements that were a part of |
|   | Data      | the PB, such as Contingency, Profit/Fee, Indirect      |
|   |           | Costs and the Contractor's Baseline Budget.            |
+---+-----------+--------------------------------------------------------+
| 1 | Pe        | A history file of changes made to the contractor's     |
| 1 | rformance | Performance Measurement Baseline, containing the       |
| . | Me        | Baseline Change Number, Baseline Change Title,         |
|   | asurement | Baseline Change Date, Approval Authority, Narrative,   |
|   | Baseline  | etc. The table also includes a snapshot of selected    |
|   | (PMB)     | data elements that were a part of the PMB, such as     |
|   | Change    | Management Reserve, WBS-Level BCWP, ACWP, BAC and      |
|   | Data      | others.                                                |
+---+-----------+--------------------------------------------------------+
| 1 | Project   | This table holds all of the various types of upload    |
| 2 | Upload    | files that were received from contractors and          |
| . | File Data | identifies the type of upload file, the date received, |
|   |           | and other information. Some upload files can be large  |
|   |           | in size (e.g., 100MB)                                  |
+---+-----------+--------------------------------------------------------+
| 1 | Projects  | The master table containing all projects in the PARS   |
| 3 | Data      | II database. Each project record in the database will  |
| . |           | have data elements such as: Project ID, Project        |
|   |           | Description, Project Acronym, Project Site Code,       |
|   |           | Managing Office Code, Project Status, Project Location |
|   |           | and will be linked to many other tables in the         |
|   |           | database.                                              |
+---+-----------+--------------------------------------------------------+
| 1 | Risk Log  | This table contains the Risk Log data, for the         |
| 4 | Data      | project, that was collected from the contractor via    |
| . |           | the upload process.                                    |
|   |           |                                                        |
+---+-----------+--------------------------------------------------------+
| 1 | Other     | To be determined during discovery process.             |
| 5 | Tables    |                                                        |
| . |           |                                                        |
|   |           |                                                        |
+---+-----------+--------------------------------------------------------+

##  Data Elements {#data-elements .Style-Heading-2-+-Not-Italic}

The table in this section identifies the data elements that are proposed
for use by the PARS II **Overhead and Assessment** and **Contractor
Project Performance** modules.

For familiarity, the table makes use of the format used by the "PARS
Data Input Requirements Document" (published by Project Performance
Corporation, March 25, 2006). The table shows how and data elements will
be entered during the life cycle of the project. Cells in the table are
color coded to identify the conditions for update, such as "required
monthly, required annually, required at special event. The column
headings and rows listed in the Proposed Data Elements for PARS II Table
are arranged in the following manner:

-   **Column 01** -- **Row:** contains the row number for the table;

-   **Column 02** -- **Ref:** contains the name of the system or
    document from which the data element was sourced. Reference codes
    are: ART (from the ART database), PDIR (PARS Data Input Requirements
    document), NEW (from discussions with Dekker, John Makepeace,
    others), PMET (Performance Metrics defined by OECM in March 2007;

-   **Column 03** -- **Data Group**: contains the data group or data
    classification code for the data element;

-   **Column 04** -- **Table Name:** contains the name of the PARS II
    database table to which the data element belongs;

-   **Column 05** -- **Data Element Name:** contains the name of the
    data element, along with examples of data to be used (for some data
    elements);

-   **Column 06** -- **Data Dictionary Description:** contains the
    commonly used definition for the data element;

-   **Column 07** -- **Data Type:** describes the data elements type,
    such as alphanumeric, numeric, date;

-   **Column 08** -- **Data Length:** defines the data element's field
    length, in characters;

-   **Column 09** -- **List of Values**: shows the list of data items
    (e.g., data values) that belong to the data element;

-   **Column 09** -- **List of Values**: shows the

-   **Column 10** -- **Comment:** contains a brief comment that can be
    used for multiple purposes;

-   **Column 11** -- **Responsible:** contains the name of the group
    responsible for entering values into this data element. Group codes
    names are: PO (Program Office), FPD (Federal Project Director), OECM
    (OECM Analyst), CONTR (Contractor);

-   **Column 12** -- contains instructions on how the data should be
    entered as the project is approved at CD-0;

-   **Column 13** -- contains instructions on how the data should be
    entered as the project moves from CD-0 to approval at CD-1;

-   **Column 14** -- contains instructions on how the data should be
    entered as the project moves from CD-1 to approval at CD-2;

-   **Column 15** -- contains instructions on how the data should be
    entered as the project moves from CD-2 to approval at CD-3;

-   **Column 16** -- contains instructions on how the data should be
    entered as the project moves from CD-3 to approval at CD-4;

-   **Column 17** -- contains instructions on how the data should be
    entered as the project moves from CD-4 to approval at Close-out.

Use the legend (below) to interpret the symbols and information in
color-coded cells found in the Proposed Data Elements for PARS II Table.

**Legend for Table "Proposed Data Elements for PARS II"**

  -------------------------------------------------------------------------
  **Legend for    
  Understanding   
  How Data        
  Elements Should 
  Be Processed**  
  --------------- ---------------------------------------------------------
  Required        An update to this data element is required when the
  (Special Event) Special Event indicated occurs

  Required        An update to this data element is required at the end of
  (Annually)      each fiscal year.

  Required        A monthly update is required (during the 3^rd^, 4^th^
  (Monthly)       week of the following month).

  Required        Input is required when the Critical Decision has been
                  approved.

  Update Required An update is required when the Critical Decision has been
                  approved.

  As Needed       Update this data element at any time in the project life
                  cycle (as needed).

  When Condition  An update to this data element is required when a change
  Occurs          occurs to a related data item, such as activity status.

  **\*\***        Double asterisk (\*\*) Life Cycle Costs for EM Operations
                  funded projects

  **\*\*\***      Triple Asterisk (\*\*\*) Not required for EM Operations
                  funded projects

  **PMB**         Data elements flagged with the PMB superscript will be
                  included in the Performance Measurement Baseline (PMB).

  **PB**          Data elements flagged with the PB superscript will be
                  included in the Performance Baseline (PB).
  -------------------------------------------------------------------------

Proposed Data Elements for PARS II

<table>
<colgroup>
<col style="width: 1%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 12%" />
<col style="width: 18%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 7%" />
<col style="width: 6%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 4%" />
</colgroup>
<thead>
<tr class="header">
<th><ol type="1">
<li></li>
</ol></th>
<th>Ref</th>
<th>Data Group</th>
<th><p>Table</p>
<p>Name</p></th>
<th><p>Data Element</p>
<p>Name</p></th>
<th>Data Dictionary Description</th>
<th><p>Data</p>
<p>Type</p></th>
<th><p>Data</p>
<p>Length</p></th>
<th><p>List of</p>
<p>Values</p></th>
<th>Comments</th>
<th>Responsible</th>
<th>CD-0</th>
<th>CD-1</th>
<th>CD-2</th>
<th>CD-3</th>
<th>CD-4</th>
<th>Closeout</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><ol start="2" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Identity</td>
<td>Project</td>
<td><strong>Project ID <sup>PB &amp; PMB</sup></strong></td>
<td><p>The DOE Project Identification Code (e.g., 97-D-102) for
construction and engineering design projects as reported in the OMB A-11
Exhibit 300 or the program budget submission. This field is used to
identify the project record and to link the project record to other
tables in the database.</p>
<p>EM projects Project IDs may include PBS# and Project#.</p>
<p>For tracking Category “2” projects that will be tracked as discrete
subprojects add suffix #A, #B, etc. to the Project ID.</p>
<p>For tracking Category “3” projects (For tracking performance of each
Near-Term segment of EM projects) add suffix *1, *2, etc. to the Project
ID.</p></td>
<td>A/N</td>
<td>25</td>
<td>N/A</td>
<td>Input once</td>
<td>PO</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="3" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Identity</td>
<td>Project</td>
<td><strong>Project Name <sup>PB &amp; PMB</sup></strong></td>
<td>The official name of the project as approved by the Acquisition
Executive. (e.g., National Ignition Facility).</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td>Input once</td>
<td>PO</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="4" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Identity</td>
<td>Project</td>
<td><strong>Project Acronym</strong></td>
<td>The acronym or abbreviated name for the project (e.g., NIF).</td>
<td>A/N</td>
<td>15</td>
<td>N/A</td>
<td>Input once</td>
<td>PO</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="5" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Scope</td>
<td>Project</td>
<td><strong>Project Description</strong></td>
<td>A brief description of the project’s scope, schedule and
budget.</td>
<td>A/N</td>
<td>1000</td>
<td>N/A</td>
<td>Input once</td>
<td>PO</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="6" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Identity</td>
<td>Project</td>
<td><strong>Project Type <sup>PB &amp; PMB</sup></strong></td>
<td><p>This data element consists of two parts:</p>
<p>The first part of the data element asks for the</p>
<p>type of building, structure or device to be built, restored or
decommissioned, such as System; Facility Construction; Infrastructure
Improvements; Restoration; Disposition; Information Technology;
Plant.</p>
<p>The second part of the data element asks if the project is a: (1)
Non-nuclear Facility (the default), (2) Nuclear Facility, or (3) Not
applicable</p></td>
<td>A/N</td>
<td>25</td>
<td><p>System;</p>
<p>Facility Construction; Infrastructure Improvements; Restoration;
Disposition; Information Technology;</p>
<p>Plant.</p></td>
<td>Input once</td>
<td>PO</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="7" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Identity</td>
<td>Project</td>
<td><strong>Project Size</strong></td>
<td><p>The relative size of the project, as expressed in dollars, such
as:</p>
<p>- <strong>Major System</strong> = TPC &gt; $750 million or EM Cleanup
Project &gt; $1 Billion) or</p>
<p><strong>Non-Major System</strong> = TPC &lt; $750 million or EM
Cleanup Project &lt; $1 Billion)</p>
<p>System of Interest – a special designation applied to the project by
the Deputy Secretary</p></td>
<td>A/N</td>
<td>50</td>
<td><p>Major System = TPC &gt; $750 million or EM Cleanup Project &gt;
$1 Billion),</p>
<p>Non-Major System = TPC &lt; $750 million or EM Cleanup Project &lt;
$1 Billion)</p>
<p>System of Interest</p></td>
<td>Needed – JM?</td>
<td>PO</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="8" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Identity</td>
<td>Project</td>
<td><strong>Project Category</strong> <strong><sup>PB &amp;
PMB</sup></strong></td>
<td><p>The internal designation of the project in the database, such as
Stand Alone Project, Subproject, Project Segment, as defined below.</p>
<p><strong>1. Stand-Alone Projects:</strong> Most of the projects fall
into this category. The system will have one record for each such
project. The project Critical Decisions may be phased or the project may
initially be a Design Project that transitions to a Construction
Project.</p>
<p><strong>2. Projects with Discrete Sub-Projects:</strong></p>
<p>Projects with discrete sub-projects are managed in smaller
sub-projects for status reporting and budget requests. CD-0 and CD-4
milestones are same for the entire project but the CD-1 through CD-3
dates could be independent. Further each sub-project could have its own
CD-4 (4A, 4B etc). Project, Sub-Project A, Sub-Project B</p>
<p>- PARS will have as many records in the system as the number of
subprojects.</p>
<p>- All subprojects will have the same Project ID but will have an
additional subproject identifier with # suffix. As an example, if the
main project had a project ID of 01-D-416, the sub-projects would have
Ids such as 01-D-16#A, 01-D-16#B etc.</p>
<p>- A Project can be subdivided into sub-projects at any time. When a
project is subdivided, information prior to the breakup will be tracked
as the first sub-project record.</p>
<p>- Generally each sub-project will also have its own separate funding
table in the Project Data Sheet.</p>
<p><strong>3. Projects with Project Segments:</strong></p>
<p>This category of projects includes EM Operations Funded projects that
may have</p>
<p>multiple segments over time, based on new contracts that will be
completed in sequential segments. Each contract-term is represented as a
segment of the life-cycle baseline.</p>
<p>- Eventually PARS will have as many records in the system as the
number of Project Segments.</p>
<p>- Each record will carry the cumulative EV data forward to the next
segment. This will</p>
<p>allow the tracking of life-cycle performance as well as measurement
of each new</p>
<p>contractor’s performance</p>
<p>- All Project Segments will have the same project ID followed by an
‘*’ as a separator</p>
<p>and a numeric segment identifier. (e.g. 2035: SR-0013* 1].</p>
<p>- Each Project Segment will have its own Critical Decisions 1 through
4.</p>
<p>- Upon completion, each completed Project Segment will have its own
Closeout</p>
<p>details.</p></td>
<td>A/N</td>
<td>25</td>
<td>Stand Alone, Subproject, Project Segment</td>
<td><p>OECM Discussion</p>
<p>Needed for Subprojects and Segments - JM</p></td>
<td>PO</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="9" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Identity</td>
<td>Project</td>
<td><strong>Project Activity Status</strong></td>
<td>The current activity status of the project, to be selected from one
of the following items: Active, Completed at CD-4, Financial Closeout,
Cancelled, On-Hold, Other. If “On-Hold” or “Other” is selected, a brief
narrative is required</td>
<td>A/N</td>
<td>25</td>
<td>Active, Completed CD-4, Financial Closeout, Cancelled, On-Hold,
Other.</td>
<td></td>
<td>PO</td>
<td><mark>Required</mark></td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
</tr>
<tr class="odd">
<td><ol start="10" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Identity</td>
<td>Project</td>
<td><strong>Project Activity Status Narrative</strong></td>
<td>A narrative that explains why the project was placed “On-Hold” or in
the “Other” activity status.</td>
<td>A/N</td>
<td>255</td>
<td></td>
<td></td>
<td>PO</td>
<td><mark>Required</mark></td>
<td>When “Activity Status” Changes</td>
<td>When “Activity Status” Changes</td>
<td>When “Activity Status” Changes</td>
<td>When “Activity Status” Changes</td>
<td>When “Activity Status” Changes</td>
</tr>
<tr class="even">
<td><ol start="11" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Resp.</td>
<td>Project</td>
<td><strong>Managing Program Office</strong> <strong><sup>PB &amp;
PMB</sup></strong></td>
<td>The alphanumeric code that represents the DOE Program Office
responsible for providing oversight.</td>
<td>A/N</td>
<td>25</td>
<td><p>EM</p>
<p>NNSA</p>
<p>SC</p>
<p>Others</p></td>
<td>Input once</td>
<td>PO</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="12" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>TPC at CD-0 (low)</strong> ($K) **</td>
<td>The low end of the total project cost range as approved at
CD-0.</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Input once</td>
<td>FPD</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="13" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>TPC at CD-0 (high</strong>) ($K) **</td>
<td>The high end of the total project cost range as approved at
CD-0.</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Input once</td>
<td>FPD</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="14" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Schedule</td>
<td>Milestone</td>
<td><strong>Milestone ID</strong></td>
<td>The unique and sequential identification code for each milestone.
This ID make is easier to track and sort milestones. Examples (1, 2, 3,
Reg-1, Reg-2, etc)</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td>Input once</td>
<td>FPD</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td><mark></mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="15" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Schedule</td>
<td>Milestone</td>
<td><strong>Milestone Type</strong></td>
<td><p>There are several types of milestones:</p>
<p>1. Critical Decision Milestones,</p>
<p>2. Regulatory Milestones,</p>
<p>3. Other Key Milestones,</p>
<p>4. EM Operations Funded Projects to Designate the Start Date of a New
Near Term Project Segment Milestones</p></td>
<td>A/N</td>
<td>50</td>
<td>Critical Decision Milestones, Regulatory Milestones, Other Key
Milestones, EM Operations Funded Projects Milestones.</td>
<td>DOE O 413.3A p.25</td>
<td>FPD</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td><mark></mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="16" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Schedule</td>
<td>Milestone</td>
<td><strong>Milestone Name</strong></td>
<td>The official name or title of the milestone. If the Milestone Type
was “1” then pick the Critical Decision from the pull-down menu and then
input an extension (A, B) if the CD will occur in phases. For other
types of milestones, enter the official milestone name.</td>
<td>A/N</td>
<td>256</td>
<td>N/A</td>
<td>DOE O 413.3A p.25</td>
<td>FPD</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td><mark></mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="17" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Schedule</td>
<td>Milestone</td>
<td><strong>Milestone Date Planned</strong></td>
<td>The planned date in which the milestone or critical decision is
expected to be met</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td>DOE O 413.3A p.25</td>
<td>FPD</td>
<td><mark>Required</mark></td>
<td><mark></mark></td>
<td><mark></mark></td>
<td><mark></mark></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="18" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Scope</td>
<td>KPP</td>
<td><strong>Key Performance Parameter ID <sup>PB </sup></strong></td>
<td>The unique sequential numeric identifier for each KPP.</td>
<td>N</td>
<td>3</td>
<td>N/A</td>
<td>Input once</td>
<td>OECM</td>
<td><mark>Required</mark></td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="19" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Scope</td>
<td>KPP</td>
<td><strong>Key Performance Parameter Description
<sup>PB</sup></strong></td>
<td><p>Narrative that describes the characteristics, functions,
requirements or design basis that, if changed, would have a major impact
on the facility or system performance, schedule, cost and/or risk, or
the ability of the interfacing project to meet its mission
requirements.</p>
<p>A KPP may be a performance, design, or interface requirement. Update
KPPs as the project progresses through planning and design
stages.</p></td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td>Required</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="20" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Schedule</td>
<td>Milestone</td>
<td><strong>Milestone Date Actual</strong></td>
<td><p>The date that the milestone or critical decision was met.</p>
<p>For projects initiated prior to DOE O 413.3 for which no formal CD- 0
was approved enter the date (2/1/yyyy) when first submitted in the
President’s budget request.</p></td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td colspan="6">Required (when critical decision or milestone is
achieved)</td>
</tr>
<tr class="even">
<td><ol start="21" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Status</td>
<td>Milestone</td>
<td><strong>Milestone Approved By</strong></td>
<td>The name of the approving authority for the milestone or critical
decision.</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td colspan="6">Required (when critical decision or milestone is
achieved)</td>
</tr>
<tr class="odd">
<td><ol start="22" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Status</td>
<td>Milestone</td>
<td><strong>Milestone Narrative</strong></td>
<td>Narrative that describes key activities or deliverables related to
the preparation for the milestone or critical decision. Include any
current issues or actions.</td>
<td>A/N</td>
<td>256</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td colspan="6">Required (when critical decision or milestone is
achieved)</td>
</tr>
<tr class="even">
<td><ol start="23" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Status</td>
<td>Attachment</td>
<td><strong>Project Attachment Title</strong></td>
<td>The title of electronic document to be attached to the project.
Examples include CD Approval, ESAAB Brief, etc)</td>
<td>A/N</td>
<td>255</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td>Required <a href="#fn1" class="footnote-ref" id="fnref1"
role="doc-noteref"><sup>1</sup></a></td>
<td>Upd Reqd <a href="#fn2" class="footnote-ref" id="fnref2"
role="doc-noteref"><sup>2</sup></a></td>
<td>Upd Reqd <a href="#fn3" class="footnote-ref" id="fnref3"
role="doc-noteref"><sup>3</sup></a></td>
<td>Upd Reqd <a href="#fn4" class="footnote-ref" id="fnref4"
role="doc-noteref"><sup>4</sup></a></td>
<td>Upd Reqd <a href="#fn5" class="footnote-ref" id="fnref5"
role="doc-noteref"><sup>5</sup></a></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="24" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Status</td>
<td>Attachment</td>
<td><strong>Project Attachment File Name</strong></td>
<td>The computer filename of the attachment. Example: Project ABC123-4
CD Approval 20091021</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td>Required</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="25" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Status</td>
<td>Attachment</td>
<td><strong>Project Attachment URL</strong></td>
<td>The hyperlink address of the attachment, once it has been stored on
the PARS II or OECM Document Control Server.</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td>Required</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="26" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>Prior Year Work for EM-C</strong> ($k)</td>
<td>Prior year work, in dollars, for EM Construction projects.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discussion Needed</td>
<td>OECM</td>
<td>Required</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="27" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>Near Term Baseline Work for EM-C</strong> ($k)</td>
<td>Near term baseline work, in dollars, for EM construction
projects.</td>
<td>N</td>
<td>12</td>
<td>Range of dollars???</td>
<td>Discussion Needed</td>
<td>OECM</td>
<td>Required</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="28" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>Out Year Planning Estimate Range for EM-C</strong></td>
<td>Out year planning estimate range, in dollars for EM construction
projects.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discussion Needed</td>
<td>OECM</td>
<td>Required</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="29" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>Life Cycle Cost for EM-C</strong></td>
<td>Life cycle cost for EM construction project.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discussion Needed</td>
<td>OECM</td>
<td>Required</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td>Upd Reqd</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="30" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Resp.</td>
<td>Project</td>
<td><strong>Federal Project Director Assigned to Project <sup>PB &amp;
PMB</sup></strong></td>
<td>The name of the federal project Director assigned to the
project.</td>
<td>A/N</td>
<td>50</td>
<td><p>Dropdown from Contacts</p>
<p>(FPDs only)</p></td>
<td></td>
<td>PO</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="31" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>Date of Project Status</strong></td>
<td><p>The fiscal year (MM/YYYY) and calendar month for reporting status
or writing assessments. This data element is updated by the author
before writing or updating monthly status information.</p>
<p>MM/YYYY</p></td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="32" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>FPD Status Assessment</strong></td>
<td>A brief progress report on the current project status. Report on
recent developments, comments, clarifications, or concerns relating to
the project. Report any issues that need to be addressed at the Program
and/or the Department level (e.g., risks encountered that will
potentially require contingency held by DOE, assumptions in the project
baseline that are not valid and could result in potential delays or cost
overruns).</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="33" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>FPD Status Assessment Indicator
<mark>(R/Y</mark>/<mark>G)</mark>)</strong></td>
<td>A color assigned to the red, yellow, green performance indicator
that indicates the overall condition of the assessment.</td>
<td>Object</td>
<td>1</td>
<td>R, Y, G</td>
<td></td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="34" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>FPD Corrective Action Plan</strong></td>
<td>A narrative from the FPD that describes the corrective action plan
expected to bring the project back on schedule, cost or other
parameter.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td><p>Needed? – JM</p>
<p>(DOE O 413.3A Attachment 2, P1)</p></td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="35" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>FPD Project Upcoming Events ID</strong></td>
<td>A unique, sequential number that identifies the specific narrative,
in order, for each of the upcoming events.</td>
<td>N</td>
<td>3</td>
<td>N/A</td>
<td>OK-JM</td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="36" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>FPD Project Upcoming Events Narrative</strong></td>
<td>Brief narrative that describes an upcoming event that should be
brought to the attention of senior DOE management. This narrative to be
shown on the DepSec Report.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td>OK-JM</td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="37" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>FPD Forecasted Month to Achieve Green</strong></td>
<td>The calendar year and month that the FPD believes that issues will
be resolved and the project will return to a status of “green”.
MM/YYYY</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="38" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>FPD Forecasted Completion Date</strong></td>
<td>The data that the FPD expects the project to be completed.
mm/dd/yyyy</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="39" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>FPD Forecasted Total Project Cost (TPC)</strong> ($K)</td>
<td>The FPD’s estimate for Total project Cost</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="40" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>PO Status Assessment</strong></td>
<td>A brief progress report on the current project status. Report on
recent developments, comments, clarifications, or concerns relating to
the project. Report any issues that need to be addressed at the Program
and/or the Department level (e.g., risks encountered that will
potentially require contingency held by DOE, assumptions in the project
baseline that are not valid and could result in potential delays or cost
overruns).</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>PO</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="41" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>PO Status Assessment Indicator
<mark>(R/Y</mark>/<mark>G)</mark>)</strong></td>
<td>A color assigned to the red, yellow, green performance indicator
that indicates the overall condition of the assessment.</td>
<td>Object</td>
<td>1</td>
<td>R,Y,G</td>
<td></td>
<td>PO</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="42" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Status Assessment</strong></td>
<td>A brief narrative that documents the current OECM assessment. OEC
will use this data element to explain the color-coded assessments (Red,
Yellow, Green) and other information as shown on the Monthly Report to
the Deputy Secretary,.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="43" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Status Assessment Indicator
<mark>(R/Y</mark>/<mark>G)</mark>)</strong></td>
<td>A color assigned to the red, yellow, green performance indicator
that indicates the overall condition of the assessment.</td>
<td>Object</td>
<td>1</td>
<td>R,Y,G</td>
<td></td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="44" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Progress Assessment</strong></td>
<td>Narrative from the OECM identifying progress made towards
Green.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td>Needed? – JM</td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="45" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Progress Assessment Indicator
<mark>(R/Y</mark>/<mark>G)</mark>)</strong></td>
<td>A color assigned to the red, yellow, green performance indicator
that indicates the overall condition of the assessment.</td>
<td>Object</td>
<td>1</td>
<td>R,Y,G</td>
<td>Needed? - JM</td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="46" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Overall Assessment</strong></td>
<td>A narrative of the OECM’s final and overall assessment of the
project for the reporting period. This narrative goes on the DepSec
Report.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="47" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Forecasted Month to Achieve Green</strong></td>
<td>The calendar year and month that the OECM believes that issues will
be resolved and the project will return to a status of “green”.
MM/YYYY</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="48" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Forecasted TPC</strong> ($k)</td>
<td>The OECM Analyst’s estimate for Total Project Cost</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="49" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Forecasted Construction Completion Date at
CD-4</strong></td>
<td><p>The OECM Analyst’s estimate for construction completion date at
CD-4.</p>
<p>MM/DD/YYYY</p></td>
<td>Date</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="50" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Status</td>
<td>Assessments</td>
<td><strong>OECM Analyst Detailed Comments</strong></td>
<td>A detailed narrative, kept by the OECM Analyst that contains ongoing
narrative about the project. This data should not be made available for
reporting.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td colspan="5">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="51" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Identity</td>
<td>Sites</td>
<td><strong>Project Site Code <sup>PB &amp; PMB</sup></strong></td>
<td><p>The alphanumeric abbreviation for Project Site (e.g., LLNL for
Lawrence Livermore National Laboratory). Please note that sites have
only been set up for DOE facilities where projects are located. Field
and Operation offices are not considered "physical sites."</p>
<p>The site code table also contains a description for the site
(Lawrence Livermore National Laboratory).</p>
<p>If a project has multiple sites, chose “Multiple” and include the
site names in the project description.</p></td>
<td>A/N</td>
<td>15</td>
<td>Dropdown</td>
<td>Input once</td>
<td>FPD</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="52" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Identity</td>
<td>Locations</td>
<td><strong>Project Location <sup>PB &amp; PMB</sup></strong></td>
<td><p>The project location data element consists of four separate data
elements: area, city, state and zipcode.</p>
<p>Enter Local area description, and the City, State, and Zip Code where
project is located. Local area description is the location within a site
(e.g., TA3 at Los Alamos, H Area at SRS). The data will be entered in
four fields.</p></td>
<td>A/N</td>
<td>256</td>
<td>N/A</td>
<td>Input once</td>
<td>FPD</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="53" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Resp.</td>
<td>Contractors</td>
<td><strong>Prime Contractor Name <sup>PB &amp; PMB</sup></strong></td>
<td>The name of the prime contractor responsible for overall management
of the project when selected after CD-1. Select the dropdown value
“Unknown” if contractor has not been selected.</td>
<td>A/N</td>
<td>50</td>
<td><p>Dropdown</p>
<p>Name</p>
<p>Name</p>
<p>Name</p>
<p>Unknown</p></td>
<td></td>
<td>FPD</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="54" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Resp.</td>
<td>FPD Certification</td>
<td><strong>FPD Certification Current Status</strong></td>
<td>The current EVMS certification status of the FPD. See dropdown.</td>
<td>A/N</td>
<td>25</td>
<td>Certified, not certified, under review</td>
<td></td>
<td>OECM</td>
<td></td>
<td>Required</td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
</tr>
<tr class="even">
<td><ol start="55" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Resp.</td>
<td>FPD Certification</td>
<td><strong>FPD Certification Level</strong></td>
<td>The current EVMS certification level of the FPD. See Dropdown</td>
<td>A/N</td>
<td>100</td>
<td>Level 4: TPC exceeding $400 million (M) • Level 3: TPC greater than
$100M and equal to or less than $400M • Level 2: TPC greater than $20M
and equal to or less than $100M • Level 1: TPC greater than $5M and
equal to or less than $20M [A history file that shows the certification
level number and the date in which it was achieved].</td>
<td></td>
<td>OECM</td>
<td></td>
<td>Required</td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
</tr>
<tr class="odd">
<td><ol start="56" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Resp.</td>
<td>FPD Certification</td>
<td><strong>FPD Certification Dates and Levels (History
File)</strong></td>
<td>A list of historical records that shows one record for each
certification event for the FPD; identifying the certification level and
the date of the certification.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td></td>
<td>Required</td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
<td>As Needed</td>
</tr>
<tr class="even">
<td><ol start="57" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Resp.</td>
<td><p>Contractor</p>
<p>Certification</p></td>
<td><strong>Contractor EVMS Certification Status</strong></td>
<td>The contractor’s EVMS certification status.</td>
<td>A/N</td>
<td>25</td>
<td><p>Certified, Reviewed,</p>
<p>Not reviewed</p></td>
<td></td>
<td>OECM</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="58" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Resp.</td>
<td><p>Contractor</p>
<p>Certification</p></td>
<td><strong>Contractor EVMS Certification Date</strong></td>
<td>The date that the contractor was certified.</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>OECM</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="59" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>TPC at CD-1 (low) (</strong>$K<strong>)</strong> **</td>
<td>An estimate, at the low side of the range in dollars, of the Total
Project Cost at CD-1</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="60" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>TPC at CD-1 (high)</strong> ($K<strong>)</strong> **</td>
<td>An estimate, at the high side of the range in dollars, of the Total
Project Cost at CD-1</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="61" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Schedule</td>
<td>Project</td>
<td><strong>Estimated Completion Date at CD-1 (high)</strong></td>
<td>The FPD’s estimate, expressed as a date on the high side of the
range, for project completion date, taken at CD-1 approval.</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="62" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Budget Request</td>
<td>Budget</td>
<td><strong>Budget Fiscal Year</strong></td>
<td>The fiscal year of the President’s Congressional Budget request
(CRB). (YYYY)</td>
<td>Date</td>
<td>4</td>
<td>N/A</td>
<td>Discuss redesign with Cindy Seiter and Jim Fountain</td>
<td>OECM</td>
<td></td>
<td colspan="4" rowspan="8"><p>Required (Annually)</p>
<p>After Budget Submission to Congress)</p></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="63" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Budget Request</td>
<td>Budget</td>
<td><strong>Budget Source</strong></td>
<td><p>The source of data for the budget profile, such as the DOE
Integrated Priority List, OMB,</p>
<p>Congress, or the Performance Baseline</p>
<p>.</p></td>
<td>A/N</td>
<td>256</td>
<td><p>Dropdown List of Values:</p>
<p>DOE Integrated Priority List, OMB,</p>
<p>Congress, Performance Baseline</p></td>
<td>Discuss redesign with Cindy Seiter and Jim Fountain</td>
<td>OECM</td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="64" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Budget Request</td>
<td>Budget</td>
<td><strong>TEC (Design)</strong> ($K) ***</td>
<td>The total Preliminary Engineering Design funding in the Budget
Request.</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Discuss redesign with Cindy Seiter and Jim Fountain</td>
<td>OECM</td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="65" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Budget Request</td>
<td>Budget</td>
<td><strong>TEC (Long Lead Items)</strong> ($K) ***</td>
<td>Total funding requested for long lead time items.</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Discuss redesign with Cindy Seiter and Jim Fountain</td>
<td>OECM</td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="66" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Budget Request</td>
<td>Budget</td>
<td><strong>TEC (Construction)</strong> ($K<strong>)</strong> ***</td>
<td>Enter the Total Estimated Construction cost estimated for the
project. (Note: this will be inclusive of any LLI funds).</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Discuss redesign with Cindy Seiter and Jim Fountain</td>
<td>OECM</td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="67" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Budget Request</td>
<td>Budget</td>
<td><strong>OPC Excluding D&amp;D</strong> ($K)</td>
<td>Enter total Other Project Costs (e.g. Pre-Conceptual Design and
Start-up).</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Discuss redesign with Cindy Seiter and Jim Fountain</td>
<td>OECM</td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="68" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Budget Request</td>
<td>Budget</td>
<td><strong>D&amp;D Costs</strong> ($K)</td>
<td>Enter the total cost for D&amp;D associated with the construction
project</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Discuss redesign with Cindy Seiter and Jim Fountain</td>
<td>OECM</td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="69" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Budget Request</td>
<td>Budget</td>
<td><strong>Operations</strong> ($K)</td>
<td>If the project includes operations, enter the total life cycle
Operations Cost. Operations costs are for plant operations and are not
to be confused with operations funds required as “OPCs” for line-item
projects. (Many EM clean-up projects will only have Operations costs).
This does not include operations costs after CD-4.</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Discuss redesign with Cindy Seiter and Jim Fountain</td>
<td>OECM</td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="70" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>TPC at CD-2 (LCC for EM)</strong> ($K) **</td>
<td>The approved TPC at CD-2. For EM operations funded project this will
be the total life-cycle cost of the project.</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Discuss with Mel Frank - JM</td>
<td>OECM</td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="71" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>TPC Near-Term (EM PBSs Only)</strong> ($K) **</td>
<td>The approved Near-Term TPC based on the Contract Performance
Baseline for EM operations funded projects.</td>
<td>N</td>
<td>12</td>
<td></td>
<td>Discuss with Mel Frank - JM</td>
<td>OECM</td>
<td></td>
<td></td>
<td colspan="2"><p>Required</p>
<p>(whenever new contract is awarded)</p></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="72" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Schedule</td>
<td>Project</td>
<td><strong>Estimated Completion Date at CD-2 (high)</strong></td>
<td>The FPD’s estimate for project completion date, expressed as a date
on the high side of the range, at CD-2 approval</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="73" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Original Contractor Management Reserve</strong> ($K)</td>
<td><p>The initial or original amount of Management Reserve set aside
for the project by DOE.</p>
<p>Enter if the contractor has a management reserve. For EM operations
funded projects the MR will be for the current Near-Term project
segment.</p></td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="74" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Original DOE Cost Contingency</strong> ($K)</td>
<td><p>The initial or original amount set aside by DOE for Cost
Contingency.</p>
<p>DOE Cost Contingency is the reserve budget held by DOE. For EM
operations funded projects this contingency will be for the entire PBS
and consistent with the project baseline validated at CD-2.</p></td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="75" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Original DOE Schedule Contingency</strong></td>
<td><p>The original amount of schedule contingency, expressed in days,
set aside for the project by DOE.</p>
<p>Schedule Contingency is the total float in calendar days planned for
this project. For EM operations funded projects schedule contingency
will be for the entire PBS and</p>
<p>Will be consistent with the project baseline validated at
CD-2.</p></td>
<td>N</td>
<td>4</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="76" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Original Contractor Fee/Profit</strong> ($k)</td>
<td>The initial or original amount of Fee or Profit, expressed in
dollars, set aside by DOE for the project.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discuss – JM</td>
<td>FPD</td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="77" type="1">
<li></li>
</ol></td>
<td>PMET</td>
<td>Project Schedule</td>
<td>Project</td>
<td><strong>Actual Construction / Execution Start Date</strong></td>
<td>The date that construction started for the project.</td>
<td>D</td>
<td>10</td>
<td>N/A</td>
<td>Requested by Paul Bosco 2007</td>
<td>FPD</td>
<td></td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="78" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>TPC at CD-3 (LCC for EM)</strong> ($K) **</td>
<td>The FPD’s estimate for Total Project Cost, expressed in dollars, at
CD-3 approval.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discuss EM – JM</td>
<td>FPD</td>
<td></td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="79" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Schedule</td>
<td>Project</td>
<td><strong>Estimated Completion Date at CD-3 (high)</strong></td>
<td>The FPD’s estimate for project completion date, as expressed as a
date on the high side of the range, at CD-3 approval.</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="80" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>ETC – Bottoms Up ($K) <sup>PMB</sup></strong></td>
<td><p>The bottoms up estimate to complete the project, as expressed in
dollars.</p>
<p>ETC is the latest bottoms-up estimate of the remaining work. ETC
includes remaining contingency and management reserve but does not
include profit or fee. For EM projects ETC will be for the contract
period and will not include DOE held contingency.</p></td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discuss – JM</td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3" rowspan="2">Required (Annually)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="81" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>ETC - Bottoms U – Date <sup>PMB</sup></strong></td>
<td>The date that the bottoms up estimate to complete exercise was
made.</td>
<td>Date</td>
<td>10</td>
<td>N/A</td>
<td>Discuss – JM</td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="82" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>BCWS Profile</strong> ($K)
<strong><sup>PMB</sup></strong></td>
<td><p>Budgeted Cost of Work Scheduled (BCWS) or Planned Value (PV) is
the budget for the planned scope that is scheduled to be accomplished
during the month. Enter</p>
<p>monthly BCWS through project completion. BCWS must flow from the
approved baseline at CD-2.</p></td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="83" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>BAC</strong> ($K) <strong><sup>PMB</sup></strong></td>
<td>Enter the Budget at Completion (BAC), expressed in dollars, The BAC
must equal the total of all BCWS Profile entries for the entire life
cycle of the project, BAC can be calculated or can be entered manually
to validate the integrity of the BCWS profile.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discuss - NCA</td>
<td><p>OECM</p>
<p>or Calculated</p></td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="84" type="1">
<li></li>
</ol></td>
<td>New</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>WBS Level Number <sup>PMB</sup></strong></td>
<td>The alphanumeric code that identifies the level of activity within
the Contractor’s WBS at which EVMS is calculated.</td>
<td>A/N</td>
<td>25</td>
<td>N/A</td>
<td>Discuss NCA</td>
<td>Automatic</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="85" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value <a href="#fn6" class="footnote-ref" id="fnref6"
role="doc-noteref"><sup>6</sup></a></td>
<td>Upload File</td>
<td><strong>Monthly BCWP</strong> ($K)
<strong><sup>PMB</sup></strong></td>
<td>The Budgeted Cost of Work Performed (BCWP) or the Earned Value (EV)
for the indicated period. This is the total budget for the scope that
was actually accomplished during the month.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="86" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Cumulative BCWP</strong> ($K)
<strong><sup>PMB</sup></strong></td>
<td>The BCWP amount, expressed in dollars for the cumulative reporting
period, summarized from the contractor’s WBS.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>Calculated</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="87" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Monthly ACWP</strong> ($K)
<strong><sup>PMB</sup></strong></td>
<td>Cost (AC) for the indicated period. ACWP is the cost actually
incurred for the work accomplished during the month and is based on
actual expenses accrued and not from financial reports.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="88" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Cumulative ACWP</strong> (K<strong>)
<sup>PMB</sup></strong></td>
<td>The ACWP amount, expressed in dollars for the cumulative reporting
period, summarized from the contractor’s WBS.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>Calculated</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="89" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Contractor Indirect Costs</strong> ($K)
<strong><sup>PMB</sup></strong></td>
<td>All monthly indirect costs allocated to the contract.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td><p>Discuss – NCA</p>
<p>DOE M 413.3-1 P.12-8</p></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="90" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Cost Variance Narrative</strong></td>
<td><p>The contractor’s written narrative of cost variance, as sourced
from the control account level of the contractor’s WBS.</p>
<p>Give specific and most significant causes of variances, corrective
actions being implemented, and recovery times. The narrative explanation
must be clear, brief to the point and written to be understood by senior
management – No abbreviations or acronyms are to be</p>
<p>used. If the previously entered BCWS profile was changed for any
reason an explanation must be provided in this narrative.</p></td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="91" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Schedule Variance Narrative</strong></td>
<td><p>The contractor’s written narrative of schedule, as sourced from
the control account level of the contractor’s WBS.</p>
<p>Give specific and most significant causes of variances, corrective
actions being implemented, and recovery times. The narrative explanation
must be clear, brief to the point and written to be understood by senior
management – No abbreviations or acronyms are to be</p>
<p>used. If the previously entered BCWS profile was changed for any
reason an explanation must be provided in this narrative.</p></td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="92" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Earned Value Narrative</strong></td>
<td><p>The contractor’s written narrative of earned value, as sourced
from the control account level of the contractor’s WBS.</p>
<p>Give specific and most significant causes of variances, corrective
actions being implemented, and recovery times. The narrative explanation
must be clear, brief to the point and written to be understood by senior
management – No abbreviations or acronyms are to be</p>
<p>used. If the previously entered BCWS profile was changed for any
reason an explanation must be provided in this narrative.</p></td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="93" type="1">
<li></li>
</ol></td>
<td>NEW</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Risk Register Log</strong></td>
<td>The contractor’s risk log, as sourced from the contractor’s
scheduling system.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="94" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Upload File</td>
<td><strong>Contractor Management Reserve Used This Period</strong>
($K)</td>
<td>The amount of Management Reserve, expressed in dollars, used this
period.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="95" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Remaining Contractor Management Reserve</strong> ($K)
<strong><sup>PMB</sup></strong></td>
<td>The remaining amount of Management Reserve, expressed in
dollars.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>Calculated</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="96" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>DOE Cost Contingency Used This Period</strong> ($K)</td>
<td>The amount of Cost Contingency, expressed in dollars, used this
period</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="97" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Remaining DOE Cost Contingency</strong> ($K)
<strong><sup>PB</sup></strong></td>
<td>The remaining amount of Cost Contingency, expressed in dollars.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>Calculated</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="98" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>DOE Schedule Contingency Used This Period</strong> (in
days)</td>
<td>Enter if Schedule Contingency (the total float in days planned for
this project) was used.</td>
<td>N</td>
<td>4</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="99" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Remaining DOE Schedule Contingency</strong> (days)
<strong><sup>PB</sup></strong></td>
<td>The remaining number of days of Schedule Contingency.</td>
<td>N</td>
<td>4</td>
<td>N/A</td>
<td></td>
<td>Calculated</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="100" type="1">
<li></li>
</ol></td>
<td>New</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Contractor Fee/Profit Used This Period ($K)</strong></td>
<td>The amount of Contractor Fee/Profit, expressed in dollars, used this
period</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discuss – JM</td>
<td>FPD</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="101" type="1">
<li></li>
</ol></td>
<td>New</td>
<td>Earned Value</td>
<td>Project</td>
<td><strong>Remaining Contractor Fee/Profit ($K)
<sup>PB</sup></strong></td>
<td>The remaining Contractor Fee/Profit.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td>Discuss – JM</td>
<td>Calculated</td>
<td></td>
<td></td>
<td colspan="3">Required (Monthly)</td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="102" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PB Baseline Change</td>
<td>PB Change</td>
<td><strong>Performance Baseline Version Number
<sup>PB</sup></strong></td>
<td>The baseline change number from the change control log. This number
is designed to make it easier to track and sort baseline changes.</td>
<td>N</td>
<td>2</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3" rowspan="8">Required whenever a change to the
Performance Baseline is approved.</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="103" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PB Baseline Change</td>
<td>PB Change</td>
<td><strong>Performance Baseline Title <sup>PB</sup></strong></td>
<td>The title given to the baseline change, such as Congressional
Baseline.</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="104" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PB Baseline Change</td>
<td>PB Change</td>
<td><strong>Performance Baseline Approval Date
<sup>PB</sup></strong></td>
<td>The date that the PB was approved by the approving official.
MM/DD/YYYY</td>
<td>Date</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="105" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PB Baseline Change</td>
<td>PB Change</td>
<td><strong>Performance Baseline Approving Official Name
<sup>PB</sup></strong></td>
<td>The name of the approving official that approved the PB.</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="106" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PB Baseline Change</td>
<td>PB Change</td>
<td><strong>Performance Baseline Change Submission Date
<sup>PB</sup></strong></td>
<td>The date that the request for the change to the PB was made.
mm/dd/yyyy</td>
<td>Date</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="107" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PB Baseline Change</td>
<td>PB Change</td>
<td><strong>Performance Baseline Change Directed? (Y/N)
<sup>PB</sup></strong></td>
<td>A flag (Yes/No) that indicates if the change to the PB was directed
by DOE.</td>
<td>Y/N</td>
<td>1</td>
<td><p>Yes</p>
<p>No</p></td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="108" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PB Baseline Change</td>
<td>PB Change</td>
<td><strong>Performance Baseline Change in Cost</strong> ($K)
<strong><sup>PB</sup></strong></td>
<td>If the baseline change accompanies a change in cost, enter the
dollar value of the approved change (positive or negative)</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="109" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PB Baseline Change</td>
<td>PB Change</td>
<td><strong>Performance Baseline Change in Schedule
<sup>PB</sup></strong></td>
<td>If the baseline change accompanies a change in schedule, enter the
calendar days of approved change (positive or negative) that the
schedule will be extended or reduced.</td>
<td>N</td>
<td>6</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="110" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PMB Baseline Change</td>
<td>PMB Change</td>
<td><strong>Performance Measurement Baseline Version Number
<sup>PMB</sup></strong></td>
<td>The baseline change number from the change control log. This number
is designed to make it easier to track and sort baseline changes.</td>
<td>N</td>
<td>2</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td colspan="3" rowspan="8">Required whenever a change to the
Performance Baseline is approved.</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="111" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PMB Baseline Change</td>
<td>PMB Change</td>
<td><strong>Performance Measurement Baseline Title
<sup>PMB</sup></strong></td>
<td>The title given to the baseline change, such as Congressional
Baseline.</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="112" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PMB Baseline Change</td>
<td>PMB Change</td>
<td><strong>Performance Measurement Baseline Approval Date
<sup>PMB</sup></strong></td>
<td>The date that the PMB was approved by the approving official.
MM/DD/YYYY</td>
<td>Date</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="113" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PMB Baseline Change</td>
<td>PMB Change</td>
<td><strong>Performance Measurement Baseline Approving Official Name
<sup>PMB</sup></strong></td>
<td>The name of the approving official that approved the PMB.</td>
<td>A/N</td>
<td>50</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="114" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PMB Baseline Change</td>
<td>PMB Change</td>
<td><strong>Performance Measurement Baseline Change Submission Date
<sup>PMB</sup></strong></td>
<td>The date that the request for the change to the PMB was made.
mm/dd/yyyy</td>
<td>Date</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="115" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PMB Baseline Change</td>
<td>PMB Change</td>
<td><strong>Performance Measurement Baseline Change Directed? (Y/N)
<sup>PMB</sup></strong></td>
<td>A flag (Yes/No) that indicates if the change to the PMB was directed
by DOE.</td>
<td>Y/N</td>
<td>1</td>
<td><p>Yes</p>
<p>No</p></td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="116" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PMB Baseline Change</td>
<td>PMB Change</td>
<td><strong>Performance Measurement Baseline Change in Cost</strong>
($K) <strong><sup>PMB</sup></strong></td>
<td>If the baseline change accompanies a change in cost, enter the
dollar value of the approved change (positive or negative)</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><ol start="117" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>PMB Baseline Change</td>
<td>PMB Change</td>
<td><strong>Performance Measurement Baseline Change in Schedule
<sup>PMB</sup></strong></td>
<td>If the baseline change accompanies a change in schedule, enter the
calendar days of approved change (positive or negative) that the
schedule will be extended or reduced.</td>
<td>N</td>
<td>6</td>
<td>N/A</td>
<td></td>
<td>CONTR</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><ol start="118" type="1">
<li></li>
</ol></td>
<td>PDIR</td>
<td>Project Scope</td>
<td>KPP</td>
<td><strong>KPP Scope Narrative at Completion
<sup>PB</sup></strong></td>
<td>A brief narrative done at the completion of the project that
verifies the completed scope against the approved scope. KPPs at CD-4
must equal KPP’s at CD-2.</td>
<td>A/N</td>
<td>4000</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Required</td>
<td></td>
</tr>
<tr class="even">
<td><ol start="119" type="1">
<li></li>
</ol></td>
<td>ART</td>
<td>Project Cost</td>
<td>Project</td>
<td><strong>Actual Cost at Financial Close-out</strong> ($K)
<strong><sup>PB</sup></strong></td>
<td>Enter the final cost of the project when final financial closure is
obtained.</td>
<td>N</td>
<td>12</td>
<td>N/A</td>
<td></td>
<td>FPD</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Required</td>
</tr>
</tbody>
</table>
<aside id="footnotes" class="footnotes footnotes-end-of-document"
role="doc-endnotes">
<hr />
<ol>
<li id="fn1"><p>Project attachments at CD-0 include the Pre-Conceptual
Planning documents, Mission Needs Statement, Tailoring Strategy
document, Mission Validation Independent Project Review document,
Program Requirements document (required for NNSA only).<a href="#fnref1"
class="footnote-back" role="doc-backlink">↩︎</a></p></li>
<li id="fn2"><p>Project attachments at CD-1include the Conceptual Design
Report, Acquisition Strategy, Preliminary Project Execution Plan,
Project Data Sheet, Environmental documents, High Performance
Sustainable Building Consideration documents, Preliminary Security
Vulnerability Assessment, Cyber Security Plan (for IT projects),
Conceptual Safety Design Report, Preliminary Hazard Analysis Report,
Preliminary Safety Validation Report.<a href="#fnref2"
class="footnote-back" role="doc-backlink">↩︎</a></p></li>
<li id="fn3"><p>Project attachments at CD-2include the Performance
Baseline document, the revised Project Execution Plan, Performance
Baseline Validation Independent Review document, Independent Cost
Estimate, Preliminary Design document, Project Data Sheet, Preliminary
Safety Design Report, Hazard Analysis Report, Preliminary Security
Vulnerability Assessment Report, Preliminary Safety Validation Report,
national Environmental Policy Act documentation.<a href="#fnref3"
class="footnote-back" role="doc-backlink">↩︎</a></p></li>
<li id="fn4"><p>Project attachments at CD-3include the revised Project
Execution Plan, revised Performance Baseline, and revised Project Data
Sheet, Independent Review for Construction or Execution Readiness,
Preliminary Safety Analysis Report, the revised Hazard Analysis Report,
Preliminary Security Vulnerability Assessment Report, Safety Evaluation
Report.<a href="#fnref4" class="footnote-back"
role="doc-backlink">↩︎</a></p></li>
<li id="fn5"><p>Project attachments at CD-4 include the Checkout,
Testing and Commissioning Plan, the Project Transition to Operations
Plan, the revised Quality Assurance Plan, Safety Analysis Report,
Construction Project Safety and Health Plan, Hazard Analysis Report,
Security Vulnerability Assessment Report, Cyber Security Plan (for IT
projects), Safety Evaluation Report, Final Project Closeout Report,
Lessons Learned Report, Operational documentation, Key Performance
Parameters Verification Report.<a href="#fnref5" class="footnote-back"
role="doc-backlink">↩︎</a></p></li>
<li id="fn6"><p>Projects with a Total Project Cost (TPC) greater than or
equal to $20 million requires entry of Earned Value data elements<a
href="#fnref6" class="footnote-back" role="doc-backlink">↩︎</a></p></li>
</ol>
</aside>

[^1]: DOE Guide 413.3-10, Appendix B-1, May 6, 2008