Smart Controller Sample Clauses

Smart Controller. MUSE GRIDS project will develop a new multi-objective smart controller which will be tested in the Osimo and Oud- Heverlee demo sites. The multi-objective smart controller will be in charge of the energy dispatch in order to balance demand and generation and accomplish with the grid connection codes increasing the self-consumption within power-quality and comfort boundary conditions. Moreover, it will also use weather forecasts to implement an optimal control in a prefixed horizon taking into account demand and generation predictions. The architecture and complete description of this Smart Controller will be presented in D1.3 of the project. In this section a brief description and considerations will be included in order to clarify the role of this controller in the DSM strategies. As D1.3 is still in progress some changes can be included in D1.3 with respect to the description included in this deliverable. Apart of the common structure some specific deployment issues related to both demo sites will be also detailed in this section and section 4.2.1. The main objectives of the Multi-Objective Smart Controller are:  Maximize primary energy saving and reduce LCOH/LCOE as optimization targets.  Increase the self-consumption of the local energy community  Increase energy efficiency and performance of each grid.  Increase local energy district reliability: guarantee of supply reducing external contribution, increasing lifetime and reducing maintenance. The Multi-Objective Smart Controller concept is shown in Figure 13. The multiobjective smart controller will be key in the DSM strategy as it will manage storage capabilities and controllable loads in the grid. A predictive control strategy will be applied along a prediction horizon which makes it possible to plan the demand profile (e.g. shifting loads or charging/discharging batteries) according to expected users’ needs, generated power and services/constraints required by the grid. As this DSM will be based on prediction models, it will be necessary to take into account the prediction errors and include in the smart controller an optimal control running at the lowest acquisition period of the grid that will adapt the planned DSM strategy to the real situation at any moment. As shown in the figure, actual set-points will take into account the baseline constraints that include long-term requirements and decisions. The architecture of the smart controller is shown in Figure 14. Not every of the showed modules...
View Source
Smart Controller. The smart controller in the Oud-Heverlee demo-site will be based in the common architecture defined in section 3.2.1. In this case the optimal control will have a special focus on power-quality and comfort boundary conditions due to the typical characteristics of Oud-Heverlee local energy community. Most of the controlled devices on the demo are home appliances or systems related to domestic user. So, it will be very important for the smart controller the users comfort as a “direct” objective of the optimization function, not only as an aggregated demand. In this sense demand side management can take into account single users flexibility or needs and take advantage of the controllable devices installed in the houses. On the other hand, Oud-Heverlee demo has a strong focus on grid stability due to the grid configuration and the weak connection to the main grid. Smart controller will also balance the demand to guarantee that grid stability through load shifting (specially for EVs) and thanks to the neighbourhood battery. As previous acquisition and measurement systems have been deployed in this demo under a backend system used by Laborelec, it will be also used for the smart controller deployment. This backend system is known as OLAF (OnLine Application Foundation) (Figure 34) and it contains many basic applications which are commonly used for different projects. An example of this is the historian application which stores data in a pre-defined manner. Another commonly used block in OLAF is the API-management application which is used to communicate specific data in a specific format with external partners in an agreed on manner and that can be used to integrate modules owned by different providers. A final example of a commonly used block is the solar forecasting block that uses data from the Belgian TSO (▇▇▇▇) to deliver a solar generation forecast. Besides the commonly used blocks, there are also specialized blocks which are likely only to be used in one project or for a specific client. The optimization block, containing the custom objective function of the Oud-Heverlee Energy Community will be one of these specific blocks developed for MUSEGRIDS project. A block which makes an assessment of the grid health, the grid diagnostic module, will also be a new specific block. Due to the ongoing EU project STORY, there are several existing constraints which must be taken into account. There will be four main elements to take into account: the STORY-ABB battery ...
View Source
Smart Controller deployment
View Source

Related to Smart Controller

  • Data Controller The Sponsor shall be the data controller for such personal data except that, if Quintiles deals with any personal data under this Agreement in the manner of a data controller, Quintiles shall be the data controller of such personal data to the extent of such dealings. Quintiles may process "personal data", as defined in the applicable data protection legislation enacted under the same or equivalent/similar national legislation (collectively "Data Protection Legislation"), of the Investigator and Study Staff for study-related purposes and all such processing will be carried out in accordance with the Data Protection Legislation.

  • Controller The Controller shall be the chief accounting officer of the Company. He shall keep full and accurate accounts of the assets, liabilities, commitments, receipts, disbursements and other financial transactions of the Company; shall cause regular audits of the books and records of account of the Company and supervise the preparation of the Company’s financial statements; and, in general, he shall perform the duties incident to the office of controller of a company (as if the Company were a Delaware corporation) and such other duties as may be assigned to him by the Member or the President or as may be provided by law. If no Controller is elected by the Member, the Treasurer shall perform the duties of the office of controller.

  • Chief Operating Officer The Chief Operating Officer shall be responsible for managing the day to day operations of the Company and shall see to it that all orders of the Chief Executive Officer are carried into effect.

  • Other Controller Audit Any other Controller may audit SAP’s control environment and security practices relevant to Personal Data processed by SAP in line with Section 5.1 only if any of the cases set out in Section 5.1 applies to such other Controller. Such audit must be undertaken through and by Customer as set out in Section 5.1 unless the audit must be undertaken by the other Controller itself under Data Protection Law. If several Controllers whose Personal Data is processed by SAP on the basis of the Agreement require an audit, Customer shall use all reasonable means to combine the audits and to avoid multiple audits.

  • Treasurer The Treasurer shall be the chief financial and accounting officer of the Trust, and, subject to the provisions of the Declaration of Trust and to any arrangement made by the Trustees with a custodian, investment adviser or manager, or transfer, shareholder servicing or similar agent, shall be in charge of the valuable papers, books of account and accounting records of the Trust, and shall have such other duties and powers as may be designated from time to time by the Trustees or by the President.