Optimised charging of EV Sample Clauses

Optimised charging of EV the customer has an electric vehicle and connects it to a charging station at a) home or b) public charge spot. To prevent a peak loads due to EV charging, the DSO is able to influence charging of EVs.
AutoNDA by SimpleDocs
Optimised charging of EV the customer has an electric vehicle and connects it to a charging station at home. To prevent a peak loads due to EV charging when people come home from work, the DSO is able to schedule and start the charging of EVs and possibly configure the charging program. The customer has to inform the DSO of how much the EV must be charged and when the vehicle must have been loaded to the required capacity level. The DSO can then execute EV charging to optimally balance energy production and consumption. In the table below the main stakeholders and their high level interests are listed for use case 3 (UC3). In Table 3-6 the information assets use in this use case have been listed. Table 3-5 List of main stakeholders and their interests in SEGRID use case 3. Stakeholders Interests Customer (Small Office, Household, EV owner) Correct invoice for energy consumption Loads and appliances operate correctly EV charged upon demand DSO Energy distribution Energy balancing Power quality management Energy supplier Purchase energy Energy sales & billing (invoicing) Table 3-6 List of information assets for SEGRID use case 3.2 Information Assets Description Measurement Data Measurement Data are smart meter measurements about the energy consumption or energy production at a connection on the LV-level. Sensor Data Sensor Data are (smart) grid measurements about the binary states of breaker and isolator. Switch Data Switch Data are the commands from the control systems in order to switch on-off a device. In case of the smart meter it is to switch on or off the customer’s connection to the grid. Change consumption /generation command Change consumption/generation command is a special type of command to give instructions to Smart Meters and household appliances to start, reduce consumption or to increase/decrease generation. In use case 3 this is used to control customer devices and smart household appliances. Consumption Priorities Consumption Priorities are in use case 3 used to communicate to the DSO that a particular smart household appliance is ready to be started by the DSO within certain time frame. Current Status Data Current status data is a special case of Binary measurements to indicate the state of a Smart Household Appliance. Set points Set points are used to control process devices with continuous regulation like generation units. In use case 3 set points are used to control the EV charging point. Monitoring Data Measurement data are smart household meter measurements g...

Related to Optimised charging of EV

  • Purpose of Educator Evaluation A) This contract language is locally negotiated and based on M.G.L., c.71, § 38; M.G.L. c.150E; the Educator Evaluation regulations, 603 CMR 35.00 et seq.; and the Model System for Educator Evaluation developed and which may be updated from time to time by the Department of Elementary and Secondary Education. See 603 CMR 35.02 (definition of model system). In the event of a conflict between this collective bargaining agreement and the governing laws and regulations, the laws and regulations will prevail.

  • Purpose of Evaluation 10.1.1 It is recognized that a system of evaluation is essential to assist Unit Members in developing competency and realizing their potential. It is further recognized that information gathered through such a system will enable decisions that measure a Unit Member’s performance in a just and equitable manner.

  • Purpose Statement Abuse of drugs and alcohol is a nationwide problem. It affects persons of every age, race, sex and ethnic group. It poses risks to the health and safety of employees of the City of Minneapolis and to the public. To reduce those risks, the City has adopted this LOA concerning drugs and alcohol in the workplace. This LOA establishes standards concerning drugs and alcohol which all employees must meet and it establishes a testing procedure to ensure that those standards are met. This drug and alcohol testing LOA is intended to conform to the provisions of the Minnesota Drug and Alcohol Testing in the Workplace Act (Minnesota Statutes §181.950 through 181.957), as well as the requirements of the federal Drug-Free Workplace Act of 1988 (Public Law 100-690, Title V, Subtitle D) and related federal regulations. Nothing in this LOA shall be construed as a limitation upon the Employer's obligation to comply with federal law and regulations regarding drug and alcohol testing. The Human Resources Director is directed to develop and maintain procedures for the implementation and ongoing maintenance of this LOA and to establish training on this LOA and applicable law.

  • 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-­‐xxxxxx-­‐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).

  • Scope of Project i. The work to be performed under this Agreement for the Rapid City Metropolitan Transportation Planning Process will be conducted in accordance with the CY 2018 Unified Planning Work Program incorporated in this agreement by reference as Attachment D, and the 2018 Unified Planning Work Program Amendment 2018-01, incorporated in and attached to this agreement as Attachment F.

  • Archival Back-Up and Disaster Recovery Licensee may use and copy the Product and related Documentation in connection with: i) reproducing a reasonable number of copies of the Product for archival backup and disaster recovery procedures in the event of destruction or corruption of the Product or disasters or emergencies which require Licensee to restore backup(s) or to initiate disaster recovery procedures for its platform or operating systems; ii) reproducing a reasonable number of copies of the Product and related Documentation for cold site storage. “Cold Site” storage shall be defined as a restorable back-up copy of the Product not to be installed until and after the declaration by the Licensee of a disaster; iii) reproducing a back-up copy of the Product to run for a reasonable period of time in conjunction with a documented consolidation or transfer otherwise allowed herein. “Disaster Recovery” shall be defined as the installation and storage of Product in ready-to-execute, back-up computer systems prior to disaster or breakdown which is not used for active production or development.

  • Using Student feedback in Educator Evaluation ESE will provide model contract language, direction and guidance on using student feedback in Educator Evaluation by June 30, 2013. Upon receiving this model contract language, direction and guidance, the parties agree to bargain with respect to this matter.

  • Registry-­‐Level Fees (a) Registry Operator shall pay ICANN a registry-­‐level fee equal to (i) the registry fixed fee of US$6,250 per calendar quarter and (ii) the registry-­‐level transaction fee (collectively, the “Registry-­‐Level Fees”). The registry-­‐level transaction fee will be equal to the number of annual increments of an initial or renewal domain name registration (at one or more levels, and including renewals associated with transfers from one ICANN-­‐accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25; provided, however that the registry-­‐level transaction fee shall not apply until and unless more than 50,000 Transactions have occurred in the TLD during any calendar quarter or any consecutive four calendar quarter period in the aggregate (the “Transaction Threshold”) and shall apply to each Transaction that occurred during each quarter in which the Transaction Threshold has been met, but shall not apply to each quarter in which the Transaction Threshold has not been met. Registry Operator’s obligation to pay the quarterly registry-­‐level fixed fee will begin on the date on which the TLD is delegated in the DNS to Registry Operator. The first quarterly payment of the registry-­‐level fixed fee will be prorated based on the number of calendar days between the delegation date and the end of the calendar quarter in which the delegation date falls.

  • Paragraph specific notes Notes following the numbered paragraphs

  • CONTRACTOR RESPONSIBILITY FOR SYSTEM AGENCY’S TERMINATION COSTS If the System Agency terminates the Contract for cause, the Contractor shall be responsible to the System Agency for all costs incurred by the System Agency and the State of Texas to replace the Contractor. These costs include, but are not limited to, the costs of procuring a substitute vendor and the cost of any claim or litigation attributable to Contractor’s failure to perform any Work in accordance with the terms of the Contract.

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