Primavera) Sample Clauses

Primavera). The Department may make reasonable requests during the Project for changes to the format or for further explanation of information provided. Submission of updates showing that Substantial Completion or Final Completion of the Project will be achieved later than the applicable scheduled completion date shall not constitute requests for extension of time and shall not operate to change the scheduled completion date(s). The Department’s receipt of, and lack of objection to, any schedule update showing Substantial Completion or Final Completion later than the dates agreed upon in the Project Schedule shall not be regarded as the Department’s agreement that the Design-Builder may have an extension of time, or as a waiver of any of the Department’s rights, but merely as the Design-Builder’s representation that, as a matter of fact, Substantial Completion or Final Completion of the Project may not be completed by the agreed upon date in the Project Schedule. Changes to the scheduled completion dates may be made only in the circumstances and only by the methods set forth in this Agreement.

Primavera). The Recipient shall provide the necessary project management files developed using Primavera to DOE. The Primavera files shall include work breakdown structure, resource loaded schedules, and milestones. Relevant supporting information, such as assumptions and calculations, shall be provided to facilitate analysis and due diligence for project management purposes. Other requirements shall include: a. A baseline (target) Project resource loaded schedule (including earned values) is due at the initiation of Phase II. b. All baseline and updated schedules are to be provided in a format that is readable with Oracle Primavera P6 Version 7.0, as an exported (.xer) file. These schedules shall be fully resource- loaded, and percent completion shall be shown as “Schedule % Complete”, as well as “Physical % Complete” where appropriate. The schedule is not required to be cost-loaded in Primavera. c. Background and supporting documentation is also required to be submitted with the baseline schedule and with each update schedule when an item below is changed, to include, but not limited to, the following: i. Oracle Primavera layout (.plf) file; ii. The summary document describing the principle changes made to the update; iii. A list of the Project schedule calendar(s) used, and how constructed;

Primavera). “Activity Codes” or comparable shall be utilized to segregate schedule activities into the following categories, as a minimum. All activities are required to have an Activity Code value for each of the following listed categories:

Primavera). The following capitalised terms used in this Schedule have the meanings given to them in the proprietary computer software known as “Primavera P6 or higher Primavera Project Management software”, produced by Primavera Systems, Inc:  Activity;  Activity ID;  Actual Dates;  Calendar;  Constraint;  Critical;  Critical Path;  Critical Path Network;  Early;  Float;  Free;  Lag;  Late;  Lead;  Logic;  Logic Link;  Milestone;  Network;  Percent Complete.  Planning Unit;  Predecessor;  Remaining Duration;  Successor; and  Total Float.