System-Wide Cohort. YCCD salaries shall be compared with all community college districts in the State of California. There are currently seventy-one (71) other districts, not including the YCCD.
System-Wide Cohort Sample Clauses
Related to System-Wide Cohort
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.
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.
System Upgrade Facilities Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.
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.
Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.
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.
System Protection Facilities The Interconnection Customer shall, at its expense, install, operate and maintain System Protection Facilities as a part of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities. The Participating TO shall install at the Interconnection Customer's expense any System Protection Facilities that may be required on the Participating TO’s Interconnection Facilities or the Participating TO’s Transmission System as a result of the interconnection of the Large Generating Facility and the Interconnection Customer’s Interconnection Facilities.
Bandwidth the amount of data (quantified as “Mbps” or “Gbps”) made available to Customer as specified in a Service Order.
System Availability System Availability percentage is calculated as follows: Total MinutesintheMonth −Downtime System Availability%age = Total MinutesintheMonth *100 System Availability SLA (“SLA”) 99.5% System Availability percentage during each Month for productive versions Credit 2% of Monthly Subscription Fees for each 1% below SLA, not to exceed 100% of Monthly Subscription Fees Excluded Downtime Total Minutes in the Month attributable to: (i) a Scheduled Downtime for which a Regular Maintenance Window is described in Section 4 below, or (ii) any other Scheduled Downtime according to Section 4 for which the customer has been notified at least five (5) business days prior to such Scheduled Downtime or (iii) unavailability caused by factors outside of SAP’s reasonable control, such as unpredictable and unforeseeable events that could not have been avoided even if reasonable care had been exercised. Scheduled Downtime Scheduled Downtime for the applicable Cloud Services to which customer has subscribed is set forth in Section 4 below entitled “Maintenance Windows for Cloud Services”.
Sites Sites shall mean the locations set forth in the Contract Documentation.
