Load Profiles Clause Samples

The Load Profiles clause defines the expected patterns and quantities of energy usage or demand over specific periods. It typically outlines how energy consumption is measured, recorded, and forecasted, often using historical data or agreed-upon estimates to establish baseline usage profiles for a facility or customer. By clearly specifying these usage patterns, the clause helps both parties anticipate energy needs, allocate costs accurately, and manage supply commitments, thereby reducing the risk of disputes over consumption levels and ensuring efficient energy planning.
Load Profiles. 5.1 During the term of this Agreement, the Company intends to post average customer load profile information, for classes that will utilize load profiling to its AEP Ohio website, Customer Choice web page, Load Profile link. These profiles are for informational purposes only and the Company makes no representations or warranties of any kind regarding either the availability or use of such load profiles.
View SourceView Similar (13)
Load Profiles. For Customers who do not have Interval Metering, the Company will provide load profiles for various classes of customers from the Company’s load research. Such load profiles will be developed in the manner as approved by the Commission. These load profiles may be updated on a periodic basis throughout the duration of this Agreement. Such updated information shall be provided to the Supplier when available.
View SourceView Similar (6)
Load Profiles. 5.1 During the term of this Agreement, the Company intends to post average customer load profile information, for classes that will utilize load profiling to its website at ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇. These profiles are for informational purposes only and the Company makes no representations or warranties of any kind regarding either the availability or use of such load profiles.
View SourceView Similar (3)
Load Profiles. The following load profiles will be used for load estimation: The customers' actual load profiles will be used for time of use (TOU) customers whose meters are remotely read on a daily basis. The proxy day historical load profiles from the previous year will be used for the remainder of TOU customers. The rate class average and strata load profiles derived from 1992 load research data will be used for all non-TOU customers. Each non-TOU customer will be assigned to a rate class average or a rate class strata load profile based on the customer's historical usage. A Customer Adjustment Factor (CAF) will be calculated for each customer to reflect the difference between the customer's historical usage and the usage under the load profile assigned to that customer. The criteria for the assignment to load profiles and the calculation of CAF's is described in detail in Attachment 1. The 1992 rate class average and strata load profiles are in EXCEL spreadsheets posted on Boston Edison's internet web site, "▇▇▇.▇▇▇▇▇▇▇.▇▇▇". A proxy day in the preceding year and another in 1992 will be selected using proprietary software developed by LODESTAR Corporation. The proxy day selection algorithm finds the day, in the historical period being searched, that had a territory load profile that most closely matches the previous day territory load profile in both shape and amplitude. The user specifies the calendar period that can be searched, the day(s) of the week that can be considered and how close in hours the peak hour in the previous day must be to the peak hour of the proxy day. TOU customers' historical load profiles from the previous year's proxy day will be retrieved from the TOU customer historical database. The rate class average and strata load profiles for the proxy day will be retrieved from the 1992 load research database. Rate class total load profiles for the proxy day will be retrieved from the 1992 load research database. The rate class total load profiles will be calibrated to reflect 1997 sales.
View Source
Load Profiles. The following load profiles will be used for load estimation: The customers' actual load profiles will be used for time of use (TOU) customers whose meters are remotely read on a daily basis. The proxy day historical load profiles from the previous year will be used for the remainder of TOU customers. The rate class average and strata load profiles derived from 1992 load research data will be used for all non-TOU customers.
View Source
Load Profiles. For Customers who do not have Interval Metering, the Cooperative will provide load profiles for various classes of customers from the Cooperative’s load research. Such load profiles will be developed in the manner as approved by the Commission. These load profiles may be updated on a periodic basis throughout the duration of this Agreement. Such updated information shall be provided to the Supplier when available.
View Source
Load Profiles. Concerning the Suonenjoki case, the heat consumption and the electricity consumption of the 163 buildings were considered. Each building had a different hourly heat and electricity consumption for the year 2016. To create the most suitable multi modal energy system for the investigated area, the load profiles of every building have to be known. For this reason, a load profile for every building was measured, simulated or assumed. In this chapter the steps to get the heat and the electricity load profile of each building will be presented. At first, the electricity consumption will be investigated. The most reliable consumption data are measured data. For buildings, whose electricity load profiles were measured and provided by VTT, these profiles were used for the energy system design. Additionally VTT also simulated the electricity consumption of several buildings. These calculated data were used for buildings, whose electricity consumption was not measured. For the remaining buildings the electricity load profiles were assumed. As already mentioned in Chapter 3.1.1, there was a quantity of buildings that include more than only one building. For these, special assumptions had to be made, because only one electricity load profile was measured or simulated. For the building numbers 11, 35, 44 and 47, it was assumed that the given electricity consumption is a summarized consumption for the included buildings. So to calculate, for example, the electricity demand of the buildings 11a and 11b, the summarized consumption of 11 was counted down on the floor area of building 11a and 11b. For building number 59, it was assumed that the given profile is assigned to building 59a. The consumption of building 59b was supposed to be proportional to building 59a because both of them are Apartment buildings. The proportional factor is the quotient between the floor areas of building 59b and 59a. Concerning the building numbers 78, 89, 116, 131 and 134, the assumption was made, that the given profiles belong to the buildings 78a, 89a, 116a, 131a and 134a. The profiles of the buildings 78b, 89b, 116b, 131b, 131c and 134a were not available. When these assumptions are taken into account, the different buildings can be separated into three groups. One of them consists out of buildings that electricity consumptions were measured. Another group contains all buildings with simulated electricity consumptions and the third group was assigned to buildings with no data so further ass...
View Source

Related to Load Profiles

  • Loss Leader; Recycled Products Contractor shall not sell or use any article or product as a “loss leader” as defined in Section 17030 of the Business and Professions Code. If Contractor will sell to the Judicial Council, or use in the performance of this Agreement, goods specified in PCC 12207 (for example, certain paper products, office supplies, mulch, glass products, lubricating oils, plastic products, paint, antifreeze, tires and tire-derived products, and metal products), then with respect to those goods: (i) Contractor shall use recycled products in the performance of this Agreement to the maximum extent doing so is economically feasible, and (ii) upon request, Contractor shall certify in writing under penalty of perjury, the minimum, if not exact, percentage of post consumer material as defined in the PCC 12200, in such goods regardless of whether the goods meet the requirements of PCC 12209.

  • Contract Database Metadata Elements Title: Sayville Union Free School District and Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU), Local 424 (2011) Employer Name: Sayville Union Free School District Union: Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU) Local: 424 Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 6131 Unit Size: 55 Number of Pages: 24 For additional research information and assistance, please visit the Research page of the Catherwood website - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/library/research/ For additional information on the ILR School - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/ 55 People TABLE OF CONTENTS ARTICLE Page XXII ANNUAL LEAVE DAYS 14 XXV BREAKS 18 XXVI CIVIL SERVICE LAW ARTICLE SECTION 75 18 XXVIII DURATION 19 XIV EMERGENCY WORK 11 XXI FOUL WEATHER CLOTHING 14 XI GRIEVANCE PROCEDURE 9 XVI HIGHER JOB CLASSIFICATION 12 XVIII HOLIDAYS 13 XV HOLIDAY AND WEEKEND BUILDING CHECKS 12 V INSURANCE 4 X LAYOFF, DISPLACEMENT AND RECALL ORDER 8 VII MANAGEMENT RIGHTS 7 XXVII MISCELLANEOUS 19 XVII NOTICES OF PROMOTIONS 13 XIII OVERTIME 10 II PAYROLL DEDUCTIONS 1 III PERSONNEL FILES 2 XXIV PHYSICAL EXAMINATIONS 18 XXIII RETIREMENT 16 IX STRIKES AND LOCKOUTS 7 XIX VACATIONS 13 XX VISITATION 14 IV WAGES 3 VI WORKERS' COMPENSATION 6 XII WORKWEEK 10 VIII WRITTEN BOARD POLICY 8 APPENDIX A 20 4/20/2016 AGREEMENT made and entered into this day of November 2013 between the SAYVILLE UNION FREE SCHOOL DISTRICT (hereinafter referred to as the “District”) and United Public Service Employees Union, ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇, N.Y. 11779 (hereinafter referred to as the “Union”).

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐▇▇▇▇▇▇-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Product Data Illustrations, standard schedules, performance charts, instructions, brochures, diagrams, and other information furnished by Developer to illustrate a material, product, or system for some portion of the Work.

  • SAMPLE (If applicable and the project has specifications, insert the specifications into this section.)