System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.
Leave Usage Full shift absences on vacation, sick leave, compensating time off, or holiday in lieu taken by employees on scheduled ten-hour workshifts shall result in the deduction of ten (10) hours from employees’ accrued leave balances.
Excess Usage If during a Billing Period, In Energy is greater than zero (0), then Excess Usage for that Billing Period will be calculated. If Excess Usage is greater than zero (0), then for the Facility and any secondary account at the conclusion of that Billing Period: (i) kilowatt-hour usage will equal the value of Excess Usage and (ii) Unused Credits are equal to zero (0). If Excess Usage is equal to zero (0), then for the Facility and secondary accounts at the conclusion of that Billing Period: (i) kilowatt-hour usage is equal to zero (0) and (ii) Unused Credits are reduced by the value of In Energy, determined for that Billing Period, and that reduced value, in accordance with paragraph (C) Unused Credits of this Article IV, will remain for possible future application.
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
System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.
Bandwidth the amount of data (quantified as “Mbps” or “Gbps”) made available to Customer as specified in a Service Order.
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.