Service Production System Uptime Sample Clauses

Service Production System Uptime. The system is required to be available twenty-four (24) hours per day, seven (7) days a week, measured on a monthly basis, during which the District actually has the ability to access the Services. This uptime metric along with others should be delivered to the CPS business / department owner monthly or dynamically
AutoNDA by SimpleDocs
Service Production System Uptime. The Focus VMS shall be available twenty-four (24) hours per day, seven (7) days a week, measured on a monthly basis, during which CPS actually has the ability to access the Focus VMS. This uptime metric along with others must be delivered to the CPS business/department owner monthly or dynamically.

Related to Service Production System Uptime

  • Transmission System Operation The NTO shall be responsible for ensuring that all actions related to the operation, maintenance and modification of its facilities that are designated as NTO Transmission Facilities Under ISO Operational Control and NTO Transmission Facilities Requiring ISO Notification are performed in accordance with the terms of this Agreement, all Reliability Rules and all other applicable reliability rules, standards and criteria, all operating instructions, ISO Tariffs, and ISO Procedures.

  • PROPANE GAS SYSTEM SERVICE AREA If the Property is located in a propane gas system service area owned by a distribution system retailer, Seller must give Buyer written notice as required by §141.010, Texas Utilities Code. An addendum containing the notice approved by TREC or required by the parties should be used.

  • 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.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5.1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct. Interconnection Service does not necessarily provide the Interconnection Customer with the capability to physically deliver the output of its Large Generating Facility to any particular load on the CAISO Controlled Grid without incurring congestion costs. In the event of transmission constraints on the CAISO Controlled Grid, the Interconnection Customer's Large Generating Facility shall be subject to the applicable congestion management procedures in the CAISO Tariff in the same manner as all other resources.

  • Energy Resource Interconnection Service (ER Interconnection Service).

  • Unbundled Sub-Loop Concentration System (USLC 2.9.1 Where facilities permit and where necessary to comply with an effective Commission order, BellSouth will provide <<customer_name>> with the ability to concentrate its sub-loops onto multiple DS1s back to the BellSouth Central Office. The DS1s will then be terminated into <<customer_name>>’s collocation space. TR-008 and TR303 interface standards are available.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

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