System Resources Clause Samples

The 'System Resources' clause defines the responsibilities and requirements regarding the hardware, software, and network infrastructure necessary for a system or service to function properly. Typically, this clause outlines which party is responsible for providing, maintaining, or upgrading these resources, and may specify minimum technical standards or compatibility requirements. By clearly allocating responsibility for system resources, this clause helps prevent disputes over performance issues and ensures that all parties understand their obligations to support the system's operation.
System Resources. Resources as defined in Bonneville’s Tiered Rates Methodology.
View SourceView Similar (11)
System Resources. Users should not use the network in such a way that would waste system resources or disrupt the use of the network by others. This includes but is not limited to excessive printing and file storage, as determined by the supervising instructor.
View SourceView Similar (4)
System Resources. System abuse includes any use of our resources that disrupts the normal use of its servers or services for others. Examples of system abuse include running excessive numbers of processes or consuming excessive amounts of CPU time, memory or disk space. Any usage of 10% or more of our system resources is an undue burden on our system and is unacceptable. If your usage ever exceeds 10% of system resources, your account may be terminated immediately and without prior notice.
View Source

Related to System Resources

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, and ▇▇- ▇▇▇-▇▇▇, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

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