Default Progress Data Sample Clauses

Default Progress Data. Actual Start and Finish dates shall not be automatically updated by default mechanisms that may be included in the CPM scheduling software systems.
AutoNDA by SimpleDocs
Default Progress Data. Actual Start and Finish dates shall not be automatically updated by default mechanisms that may be included in the CPM scheduling software systems. Out-of-Sequence Logic The Contractor shall correct all incorrect logic relationships in the schedule update to eliminate any out-of-sequence logic. The Contractor shall make all changes in the logic or other adjustments found to be incorrect by JEA. Electronic Schedule Naming and Formatting JEA will provide guidance on schedule name designation to be used. The Contractor shall not submit any two schedules with the same file name. Electronic Project Schedule Files Electronic schedule files shall be in “.xer” format compatible with Oracle Primavera P6. Electronic narrative files shall be in readable PDF format (not scanned). Printed Project Schedules PDF or printed schedules shall be no larger than 11”x17” in landscape format and no more than one page wide. PDF or printed schedules should show Activity ID, Activity Name, Original Duration, Remaining Duration, Start, Finish and Total Float columns. The Xxxxx Chart shall show bars for Actual Work, Remaining Work, Critical Remaining Work, Current Bar Labels, Milestones, Project Baseline and Baseline Milestone. The Data Date line shall also be displayed on the Xxxxx Chart. The header of PDF or printed schedules shall contain the project name, the run date and the data date at a minimum. The footer shall contain a Xxxxx Chart legend, page number, total pages number and active filters at a minimum.

Related to Default Progress Data

  • Quarterly Progress Reports The goal of this task is to periodically verify that satisfactory and continued progress is made towards achieving the objectives of this Agreement on time and within budget. The objectives of this task are to summarize activities performed during the reporting period, to identify activities planned for the next reporting period, to identify issues that may affect performance and expenditures, and to form the basis for determining whether invoices are consistent with work performed. The Recipient shall: • Prepare a Quarterly Progress Report which summarizes all Agreement activities conducted by the Recipient for the reporting period, including an assessment of the ability to complete the Agreement within the current budget and any anticipated cost overruns. Progress reports are due to the CAM the 10th day of each January, April, July, and October. The Quarterly Progress Report template can be found on the ECAMS Resources webpage available at xxxxx://xxx.xxxxxx.xx.xxx/media/4691. Product: • Quarterly Progress Reports

  • Monthly Progress Reports During the Construction Period, the Concessionaire shall, no later than 7 (seven) days after the close of each month, furnish to the Authority and the Independent Engineer a monthly report on progress of the Construction Works and shall promptly give such other relevant information as may be required by the Independent Engineer.

  • Contractor Default Failure of the Contractor, which has neither been remedied nor waived, to perform or otherwise to comply with the terms of the Construction Contract.

  • Default Authorized User a. Breach by Authorized User An Authorized User’s breach shall not be deemed a breach of the Centralized Contract; rather, it shall be deemed a breach of the Authorized User’s performance under the terms and conditions of the Centralized Contract.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Monthly Progress Report This report shall include a description of the activities during the reporting period and the activities planned for the ensuing reporting period. The first reporting period consists of the first full month of performance plus any fractional part of the initial month. Thereafter, the reporting period shall consist of each calendar month. The Contractor shall submit a Monthly Progress Report on or before the 15th calendar day following the last day of each reporting period and shall include the following: Title Page: The title page for this report shall include the contract number and title; the type of report and period that it covers; the Contractor’s name, address, telephone number, fax number, and e-mail address; and the date of submission.

  • Cyber incident damage assessment activities If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

  • Progress Reports The Recipient shall submit to the OPWC, at the OPWC's request, summary reports detailing the progress of the Project pursuant to this Agreement and any additional reports containing such information as the OPWC may reasonably require.

  • Progress Report 10.1 If required, you shall submit progress reports in connection with the Service (“Report”) on at least a monthly basis, or as we may require. The Report shall include a summary of the activities and accomplishments during the previous reporting period.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!