Planned Change Management Sample Clauses

Planned Change Management. (a) Change Management procedures will be utilized to manage any planned network activities, which involve changes to the Network and will result in a planned outage or service degradation. An assessment will be undertaken on each change to determine the scope of the planned activity which in turn will define the hours that the activity can take place. THREATENING  Has potential to affect service  Changes allowed in maintenance window 00:01 to 06:00 TURNDOWN  A Service disruption or Network outage  Changes allowed in maintenance window 02:00 to 06:00
AutoNDA by SimpleDocs

Related to Planned Change Management

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

  • Change Management Process If Customer or Oracle requests a change in any of the specifications, requirements, Deliverables, or scope (including drawings and designs) of the Professional Services described in any Statement of Work, the party seeking the change shall propose the applicable changes by written notice. Within forty-eight (48) hours of receipt of the written notice, each party’s project leads shall meet, either in person or via telephone conference, to discuss and agree upon the proposed changes. Oracle will prepare a change order describing the proposed changes to the Statement of Work and the applicable change in fees and expenses, if any (each, a “Change Order”). Change Orders are not binding unless and until they are executed by both parties. Executed Change Orders shall be deemed part of, and subject to, this Addendum. If the parties disagree about the proposed changes, the parties shall promptly escalate the change request to their respective senior management for resolution.

  • Construction Change Directives 7.3.1 A Construction Change Directive is written order prepared by the Architect and signed by the Owner and Architect, directing a change in the Work and stating a proposed basis for adjustment, if any, in the Contract Sum, or Contract Time, or both. The Owner may by Construction Change Directive, without invalidating the Contract, order changes in the Work within the general scope of the Contract consisting of additions, deletions or other revisions, the Contract Sum and Contract Time being adjusting accordingly.

  • Crisis Management This coverage shall include the costs of managing the public relations outfall from most data breach scenarios.

  • Project Management Plan 9.1.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and Good Industry Practice.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • Construction Change Directive A written order prepared and issued by the District, the Construction Manager, and/or the Architect and signed by the District and the Architect, directing a change in the Work.

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least sixty (60) days advanced preliminary written notice and at least thirty (30) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

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