15-NAT-8814 - Supplier Scheduling and Reporting Requirements Rev. 1.pdf

NAT-8814 Rev 0

Supplier Scheduling and Reporting Requirements Page 1 of 8

Controlled Document - Verify Current Revision

SUBJECT TO DOE COOPERATIVE AGREEMENT NO. DE-NE0009054

TERRAPOWER PROPRIETARY AND CONFIDENTIAL – SUBJECT TO CONFIDENTIALITY AGREEMENT

NAT-5629 Rev. 1

Verify Current Revision

REVISION HISTORY

Revision No.

Effective Date Affected

Section(s) Description of Change(s)

0 All Rev New

Document Title:

Supplier Scheduling & Reporting Requirements

Natrium Document No.:

NAT-8814

Rev. No.:

Page:

Doc Type:

Administrative Document

Target Quality Level:

N/A

Alternate Document No.:

N/A

Alt. Rev.:

N/A

Originating Organization:

TerraPower, LLC

Quality Level:

N/A

Natrium MSL ID:

Procurement

Status:

Controlled

Open Items?

No

Approval

Approval signatures are captured and maintained electronically; see Electronic Approval Records in EDMS.

Signatures or Facsimile of Electronic Approval Record attached to document.

NAT-8814 Rev 0 Supplier Scheduling and Reporting Requirements Page 2 of 8

SUBJECT TO DOE COOPERATIVE AGREEMENT NO. DE-NE0009054

1 All Restructured document and cleaned information to be more specific

NAT-8814 Rev 0 Supplier Scheduling and Reporting Requirements Page 3 of 8

TABLE OF CONTENTS

1 INTRODUCTION

2 SUPPLIER TECHNICAL PROPOSAL

3 CONTRACT AWARD & KICKOFF

4 SCHEDULE REQUIREMENTS

4.1 Level 1: Project Summary Schedule (Master Schedule)

4.2 Level 2: Control Schedule

4.3 Level 3: Detailed Schedule (expected supplier reporting level)

4.4 Level 4: Work Package Schedule

4.5 Level 5: Daily Schedule

4.6 Summary of Differences:

4.7 Minimum Level 3 Schedule Requirements

5 REPORTING CYCLE

5.1 SCHEDULE

5.2 COST

LIST OF FIGURES

No table of figures entries found.

NAT-8814 Rev 0 Supplier Scheduling and Reporting Requirements Page 4 of 8

1 INTRODUCTION

The intent of the scheduling and reporting requirements is to reduce risk, to provide an accurate accounting of project status, and to be predictive. The Supplier is responsible for establishing project controls, scheduling work, monitoring progress, keeping the Company fully updated as it pertains to the contractual scope. Key objectives of this document are to explain the following:

Establish the minimum scheduling and reporting requirements

Expectations and responsibilities (Supplier and Company)

Reporting tools and methods

Timing of deliverables & reporting cadence

Ensure supplier cost and tracking tools align monthly performance report and IMCS

Best practices in Project Controls to reduce risk, improve communications, and provide guidance for resource and cost management to ensure project delivery

2 SUPPLIER TECHNICAL PROPOSAL

A Level 2 schedule (Work scope by Phase or Discipline) design, fabrication, and delivery with appropriate schedule milestones (see Schedule Level Definition in Section 4 below) and detail to reflect the work. Level 2 detail is the minimum level of detail required with a proposal although, more detail is encouraged.

Before the contract is awarded the supplier must provide examples the Level 3 schedule methodology, ability to align to the Company cost reporting requirements (if applicable) and any other Supplier specific tracking tools wanting to be utilized for the duration of the purchase order.

3 CONTRACT AWARD & KICKOFF

A Level 3 schedule shall be developed by the Supplier following award by the Company.

The Level 3 schedule lags the Technical Proposal depending on scope size and complexity. The schedule due date will be listed in the Statement of Work but shall be received no later than 60 calendar days post contract award.

NAT-8814 Rev 0 Supplier Scheduling and Reporting Requirements Page 5 of 8

4 SCHEDULE REQUIREMENTS

This section is meant to explain the differences between schedule levels and explain the level of detail required at each reporting level for the Suppler. The schedule is expected to provide accurate progress, tracking, impacts, cost payments, and forecasting.

4.1 Level 1: Project Summary Schedule (Master Schedule)

Scope: Entire project

Detail: Very high-level overview

Purpose: Provides an overall timeline and major deliverables or phases.

Components: Key project phases and major milestones (e.g., project initiation, design phase completion, major approvals, project completion).

Audience: Senior management, stakeholders, and executives.

Example: Project start, major design completion, testing start, project end.

4.2 Level 2: Control Schedule

Scope: Major project deliverables and phases

Detail: High-level, but more detailed than Level 1

Purpose: Guides the project management team by outlining key phases and critical paths.

Components: Major work packages, phase gates, and intermediate milestones.

Audience: Project managers and senior team members.

Example: Detailed design completion, procurement start, major subsystem installations.

4.3 Level 3: Detailed Schedule (expected supplier reporting level)

NAT-8814 Rev 0 Supplier Scheduling and Reporting Requirements Page 6 of 8

Scope: Work packages and specific deliverables

Detail: More granular, showing tasks and activities within each major deliverable.

Purpose: Provides a detailed plan for the project execution.

Components: Task breakdowns, dependencies, resource assignments, and more granular milestones.

Audience: Project team members and functional managers.

Example: Detailed tasks for each subsystem, integration testing phases, procurement milestones.

4.4 Level 4: Work Package Schedule

Scope: Individual work packages and activities

Detail: Very detailed, including individual tasks, durations, and resources.

Purpose: Facilitates day-to-day management and tracking of project tasks.

Components: Specific tasks, assigned resources, durations, start and finish dates, and detailed dependencies.

Audience: Team leads, project coordinators, and individual contributors.

Example: Specific engineering tasks, testing protocols, procurement of specific items, individual installation tasks.

4.5 Level 5: Daily Schedule

Scope: Individual tasks and activities

Detail: Most detailed level, down to daily tasks and assignments.

Purpose: Manages daily operations and ensures individual tasks are completed on time.

Components: Daily work activities, specific task assignments, timesheets, and daily check-ins.

Audience: Individual team members and supervisors.

Example: Daily work assignments, task checklists, daily progress updates.

NAT-8814 Rev 0 Supplier Scheduling and Reporting Requirements Page 7 of 8

4.6 Summary of Differences:

Level 1: Entire project, broad phases, senior management focus.

Level 2: Major deliverables, high-level tasks, project management focus.

Level 3: Detailed tasks, work packages, project team focus.

Level 4: Individual work package details, specific activities, team lead focus.

Level 5: Daily tasks, individual assignments, day-to-day operations focus.

4.7 Minimum Level 3 Schedule Requirements

A. Ability to show critical path and associated driving activity details.

B. Baselined and approved by the Company prior to beginning work.

a. Schedule has been approved through the Company specified deliverables management system.

C. Be available in electronic format when requested by the Company. Preferred software is Primavera Project Management or Microsoft Project, but other scheduling tools are acceptable if it fulfills the Level 3 Schedule Requirements. Schedules must be delivered on the required cadence in the native file and a PDF version.

D. Start and Finish Constraints should only be used in rare situations and are discouraged.

E. Should be baselined after the initial schedule approval has been received. The baseline dates must be in alignment with any contractual deliverable dates that specified in the SOW.

F. Include approved changes and show schedule impacts when applicable.

G. Schedule status must be taken as specified in the statement of work, but not less than once per month.

H. Schedule shall be cost-loaded (activities and/or Milestones) and equal contract value (to include any approved changes). If the schedule cannot be cost loaded, the Supplier must demonstrate to the Company Program Management Office sound methodology for tracking performance. The company must review and approve of the methodology.

I. Include third-party activities when applicable (deliveries, inspections, coatings, etc.).

J. Planned and Earned values from the schedule must correspond to the Cost Report data.

5 REPORTING CYCLE

5.1 SCHEDULE

NAT-8814 Rev 0 Supplier Scheduling and Reporting Requirements Page 8 of 8

Schedule updates will typically be received every week or every other week, but no less than one per month. The exact reporting cadence is found in the supplier SOW.

5.2 COST

Supplier Project Status Report is required within 5 business days of month end close of the supplier.

Note: All supplier cost types are required to submit a monthly performance report. The format of the monthly performance report will differ depending on the type of contract. Cost type contracts must submit the Cost-Plus Monthly Report, and the CP-Time Phased Forecast portion of NAT- 12844. Fixed Price contracts must submit the Firm Fixed Price Report portion of NAT-12844

END OF DOCUMENT