===== Meeting in Bilbao CNRS / TECNALIA : Use Cases for Actuation Conflict Management in KUBIK ===== Invitation Letter and Agenda : Discussed Use Cases : * Use Case with a SCADA System for the Climate Control *Application Outputs setpoint (commands) for each fane coil, curtain , blinder, lights *Application Inputs temperature sensors (inside / outside), humidity (inside / outside), COV, CO2, light sensors (inside / outside), switches, solar radiation *Application 1 : Management of the luminosity in a room : Open the curtain if light outside is high enough or switch on the light inside, switch off the light and close de curtain when we want to decresase luminosoty in a room. based on a real switch. *Application 2 : If the solar radiation is high enough to increase temperature in a room we open the curtain to solar radiation (fan coil consume less energy) *Application 3 : If the solar radiation is high, to decrease temperature in a room we close the curtain/Blinder to solar radiation (fan coil consume less energy) *Application 4 : switches in a room allow to switch on/off the lights *Application 5 : termostats in room allow to drive fan coils . *Conflict App1 / App3 *conflict : luminosity in room (App1) versus cool the room (App3) * Strategy 1 : *knowing the application he give a priority *If people are in a building, priority to luminosity in the other case priority to curtain / blinder are at the middle stage * Conflict App4 / App4 * Strategy : *automaton on/off is on *adding some time delay consideration **COMMENTS :** *Sometimes we need to have informations on the semantic off the App (energy consumption is a priority over luminosity) *Sometimes we need more inputs than those we want to manage for actuation conflict (when Paul is in the room then ...) * Same applications based on multiple devices and Man machine interfaces ** Some References : ** {{:recherche:enact:specificmeeting:taking_advantage_of_an_existing_indoor_climate_monitorization_for.pdf|}}