System Output Sample Clauses

System Output. Customer acknowledges and agrees that: (i) the Output from the System will vary from time to time; (ii) System Owner provides no warranty or guarantee of any particular level of Output of the System; (iii) during any Utility billing period during the term of this Agreement, Customer’s Utility charges for the Customer Meters may exceed the Net Metering Credits attributable to Output of the System for such billing period (for example, if Customer’s electricity usage exceeds the Output of the System); (iv) Customer is solely responsible for paying any and all Utility charges in excess of the Net Metering Credits allocated to Customer; and (v) System Owner is not a utility or an electricity provider and does not assume any regulatory or statutory obligations of a utility or electricity provider.
Sample 1Sample 2
AutoNDA by SimpleDocs
System Output. Customer acknowledges and agrees that: (i) the Output from the System will vary from time to time and that (ii) System Owner provides no warranty or guarantee of any particular level of Output of the System; (iii) during any Utility billing period during the term of this Agreement, Customer’s Utility charges for the Customer Meters may exceed the Net Metering Credits attributable to Output of the System for such billing period (for example, if Customer’s electricity usage exceeds the Output of the System); (iv) Customer is solely responsible for paying any and all Utility charges in excess of the Net Metering Credits allocated to Customer; and (v) System Owner is not a utility or an electricity provider and does not assume any regulatory or statutory obligations of a utility or electricity provider. System Owner will make a reasonable attempt to inform Customer in advance of any planned outages by sending an e-mail to the following address: [TOWN TO INSERT].
Sample 1
System Output. (a) System Owner’s estimate of the Estimated Year One Output was prepared by or on behalf of System Owner using the National Renewable Energy Laboratory’s PVWatts program or otherwise using practices and methods generally accepted within the solar power industry with respect to solar systems similar to the System.
Sample 1
System Output. During the Service Term, the System is estimated to have an approximate annual generating capacity of 102,106 kWh. Customer acknowledges and agrees that: (i) the Output from the System will vary from time to time; (ii) Service Provider is not providing any warranty or guarantee of any particular level of Output of the System; (iii) during any Utility billing period during the term of this Agreement, Customer’s Utility charges for the Customer Meters may exceed the Net Metering Credits attributable to Output of the System for such billing period (for example, if Customer’s electricity usage exceeds the Output of the System); (iv) Customer is solely responsible, at its cost and expense and through its Utility, for paying any and all Utility charges in excess of the Net Metering Credits allocated to Customer or when the System is not in operation; and (iv) Service Provider is not a utility or an electricity provider and does not assume any regulatory or statutory obligations of a utility or electricity provider.
Sample 1
System Output. Customer acknowledges and agrees that: (i) the Output from the System will vary from time to time; (ii) System Owner may reasonably interrupt or reduce Output for purposes of inspection, maintenance, repair, replacement, construction, installation, removal or alteration of equipment used to produce Output and that, other than in the case of emergency, the System Owner will give Customer notice at least five (5) business days prior to such interruption;
Sample 1
System Output. 2.6.1 When exported, videos of a particular camera or tile view of cameras for a given period of time shall be stitched together into a single video file for ease of viewing.
Sample 1

Related to System Output

  • System Operations Each party, at its own expense, shall provide and maintain the equipment, software, services and testing necessary to transmit Data Communications to, and receive Data Communications from the parties’ respective Receipt Computers.

  • 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 Operation The Parties shall adhere to any applicable operational requirements of PJM necessary to protect the integrity of the transmission system within the PJM Control Area and the transmission systems of interconnected control areas, and shall satisfy any and all PJM, RFC and NERC criteria, when applicable. The DS Supplier shall also adhere to any applicable operational requirements of the Company necessary to protect the integrity of the Company’s local distribution system.

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

  • System Timeout The system providing access to PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must provide an automatic timeout, requiring re-authentication of the user session after no more than 13 twenty (20) minutes of inactivity.

  • Outputs 8. The objectives and outcomes of this Agreement will be achieved through a range of outputs. The outputs include the:

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

Time is Money Join Law Insider Premium to draft better contracts faster.