NO SYSTEM DISRUPTION Sample Clauses

NO SYSTEM DISRUPTION. Customer will not use, nor allow others to use, the Service to disrupt Provider network or computer equipment owned by other Provider customers. Any static IP address must be authorized and provisioned by Provider.
AutoNDA by SimpleDocs
NO SYSTEM DISRUPTION. You may not use, or allow others to use, your account to cause disruption of the normal use of the Service by others including without limitation disrupting our backbone network, nodes, services, or any other Internet service provider or backbone provider.
NO SYSTEM DISRUPTION. Resident will not use, or allow others to use, the Service to disrupt GTHLLC's network or computer equipment owned by GTHLLC or other GTHLLC Residents. This includes, but is not limited to, improperly interfering with, inhibiting, degrading, or restricting the use and operation of the Service by others. In addition, Resident will not, or allow others to, alter, modify, service, or tamper with the GTHLLC Equipment or Service or permit any other person to do the same who is not authorized by GTHLLC.
NO SYSTEM DISRUPTION. The Customer agrees not to use the services provided by GALLOP to disrupt either the network or equipment owned by GALLOP or Subcontractors of GALLOP or equipment owned by other customers of GALLOP. Furthermore, The Customer agrees not to use the services provided by GALLOP to disrupt other Internet Service Providers, including but not limited to e-mail bombing or the use of mass- mailing programs.

Related to NO SYSTEM DISRUPTION

  • H5 Disruption The Contractor shall take reasonable care to ensure that in the performance of its obligations under the Contract it does not disrupt the operations of the Authority, its employees or any other contractor employed by the Authority.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Disruption 41.1 The Contractor shall take reasonable care to ensure that in the performance of its obligations under the Framework Agreement it does not disrupt the operations of the Authority, its employees or any other Contractor employed by the Authority. 41.2 The Contractor shall immediately inform the Authority of any actual or potential industrial action, whether such action be by their own employees or others, which affects or might affect its ability at any time to perform its obligations under the Framework Agreement. 41.3 In the event of industrial action by the Staff, the Contractor shall seek Approval to its proposals to continue to perform its obligations under the Framework Agreement. 41.4 If the Contractor’s proposals referred to in clause 41.3 are considered insufficient or unacceptable by the Authority acting reasonably, then the Authority may by notice terminate the Framework Agreement with immediate effect.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Downtime There may be downtime during the Migration. The duration of the downtime will depend on the amount of data that Agency is migrating. Axon will work with Agency to minimize any downtime. Any VIEVU mobile application will need to be disabled upon Migration.

  • Outage Repair Standard In the event of an outage or trouble in any Service being provided by a Party hereunder, the Providing Party will follow Verizon’s standard procedures for isolating and clearing the outage or trouble.

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • PRICING OF After Hours Coefficient What is your after hours coefficient for the RS Means Price Book for work performed after normal working hours?

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

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