S.2.i Suggestion Service

WP8 – Project coordination
D8.1 Project Handbook
CIP-ICT-PSP-2012-6 – 325161
"This project is partially funded under the ICT Policy Support Programme (ICT PSP) as part of the
Competitiveness and Innovation Framework Programme by the European Community"
(http://ec.europa.eu/ict_psp).
Suggestion Service
Technical documentation part of
WP4 Integration of SUNSHINE pilot smart urban services
Revision: 1.0
Authors:
Luca Giovannini, Oscar Benedetti (SGIS)
Umberto Di Staso, Gabrio Girardi (GRAPHITECH)

CIP-ICT-PSP-2012-6 – 325161
Dissemination level PU (public)
Contributor(s)
Reviewer(s)
Editor(s)
Partner in charge(s)
Due date
Submission Date
REVISION HISTORY AND STATEMENT OF ORIGINALITY
Revision Date Author Organisation Description
V0.1 06/11/2015 Luca Giovannini SGIS
Document
created
V1.0 21/12/2015 Luca Giovannini SGIS Final release
Statement of originality:
This deliverable contains original unpublished work except where clearly indicated otherwise.
Acknowledgement of previously published material and of the work of others has been made
through appropriate citation, quotation or both.
Moreover, this deliverable reflects only the author’s views. The European Community is not
liable for any use that might be made of the information contained herein.

CIP-ICT-PSP-2012-6 – 325161
Table of Contents
1 Use Cases - Buildings.......................................................................................................... 4
1.1 Access to daily suggestion on heating system use ........................................................ 4
1.1.1 user interface mockups .......................................................................................... 5
1.2 View/edit of building comfort profiles .......................................................................... 7
2 Use Cases - Shelters ........................................................................................................... 9
2.1 Access to daily prediction on h/c system activity.......................................................... 9
2.2 View/edit of h/c system thresholds............................................................................. 10
2.2.1 user interface mockups ........................................................................................ 11
3 Server-side Service Specifications.................................................................................... 13
3.1 Servizi RESTful (profili comfort e threshold buildings) ................................................ 13
3.1.1 Esempi................................................................................................................... 14
3.2 Servizi SOS (suggestion output)................................................................................... 16
3.2.1 Building ................................................................................................................. 16
3.2.2 Shelter................................................................................................................... 17

CIP-ICT-PSP-2012-6 – 325161
1 Use Cases - Buildings
The suggestion service for buildings has two use cases:
1. Access to daily suggestion on heating system use
Regular supervision activity of system suggestions, based on standard comfort profiles
ingested at the beginning of the heating season and on daily weather forecasts. Suh a
form of fruition implies the ability to access (without editing) daily profiles for:
o Requested comfort
o Estimated internal temperature profile
o Estimated system on/off profile
This use case includes also an email notification of the daily suggestion to the user in
the case of “out-of-the-average days”.
2. View/edit of building comfort profiles
Spot activity to verify/adjust/plan inputted comfort profiles. This use case has to allow
a global view of all the requested comfort profiles throughout the thermal season and
allow its adjustment.
1.1 Access to daily suggestion on heating system use
Suggestions are computed daily for each pilot building covered by the service.
 The suggestion is estimated for the day following the current and is scheduled to be
computed at 11:00 CET daily, right after the new weather prediction for the current
day are loaded from Meteogrid’s weather service.
 If the system was not able to retrieve the new 3-day weather forecasts for the day,
the forecast of the previous day are used.
 If no consumption profile has been provided for the day following the current, the
suggestion routine is not executed and no suggestion is computed.
The suggestion routine has two outputs:
 The estimated internal temperature profile for the day following the current
 The suggested on/off profile for the heating system of the building for the same day
The outputs of the suggestion profile can be accessed by the user in three ways:
 the web client
 the energy app
 email notification to building manager

CIP-ICT-PSP-2012-6 – 325161
1.1.1 user interface mockups
1.1.1.1 web client
The client shows:
 The requested comfort profile [1] for the selected day
 The estimated internal temperature profile [2] for the selected day
 The suggested on/off profile [3] for the heating system of the building for the day
By selecting a different day in the past from the calendar [4], the dashboard updates the
contents of panel [1], [2] and [3] accordingly.
With respect to panel [2] and [3], no suggestion is computed when either:
 No comfort profile is provided for the day (the building is not in use)
 No forecast data is available
2
4
3
1

CIP-ICT-PSP-2012-6 – 325161
1.1.1.2 energy app
The client shows:
 The requested comfort profile [1] for the day following the current
 The estimated internal temperature profile [2] for the day following the current
 The suggested on/off profile [3] for the heating system of the building for the same
day
contents of panel [1], [2] and [3] accordingly.
With respect to panel [2] and [3], no suggestion is computed when either:
 No comfort profile is provided for the day (the building is not in use)
 No forecast data is available
1.1.1.3 email notification to building manager
Daily heating schedule suggestion for:
Elementare Poledrelli - Via Poledrelli 1 - CT03-77
Heating suggestion for day:
2015-11-03
Requested comfort temperature:
20 °C
Requested comfort periods:
32
1
4

CIP-ICT-PSP-2012-6 – 325161
from 7:30 to 18:00
Temperature difference with respect to previous days:
DeltaT_min = 3.0 °C (normal)
Suggested turn on/off times:
Turn on 4:32
Turn off 18:00
1.2 View/edit of building comfort profiles
1.2.1.1 web client
The client shows:
 The requested comfort profiles [5] for all the days of the year. Comfort profiles are
shown in blocks of 7 consecutive days and changing the day in the calendar on top
allows to scroll the blocks backwards and forwards. Days with no comfort profiles are
shown with blank lines.
 The form to modify/delete [6] the comfort profiles for all the days of the year. The
fields from/to allow to edit more than one day at the same time (all with the same
comfort values). In order to edit just a single day it is sufficient to fill the field “from”
with the corresponding date.
6
5

CIP-ICT-PSP-2012-6 – 325161
1.2.1.2 energy app
The client shows:
 The requested comfort profiles for all the days of the year. Comfort profiles are shown
in a calendar panel [5] with buttons allowing to scroll between the months.
 The form to modify/delete [6] the comfort profiles for all the days of the year.
6
5

CIP-ICT-PSP-2012-6 – 325161
2 Use Cases - Shelters
The suggestion service for shelter has two use cases:
 Access to daily prediction on h/c system activity (shelters)
 View/edit of h/c system thresholds (shelters)
2.1 Access to daily prediction on h/c system activity
2.1.1.1 web client
The client shows:
 The requested system use thresholds [1] for the selected month
 The suggested heating/cooling system use [3] for the same day
contents of panel [2] and [3] accordingly.
With respect to panel [2] and [3], no suggestion is computed when no forecast data is
available.
2
1
3
4

CIP-ICT-PSP-2012-6 – 325161
2.1.1.2 energy app
The client shows:
 The requested system use thresholds [1] for the selected month
 The suggested heating/cooling system use [3] for the same day
contents of panel [2] and [3] accordingly.
With respect to panel [2] and [3], no suggestion is computed when no forecast data is
available.
2.2 View/edit of h/c system thresholds
There are two types of thresholds:
 The number of times the heating system of the shelter is turned on during the day
 The number of times the cooling system of the shelter is turned on during the day
These two types of threshold can be specified independently
 For each shelter
 For each month of the year
When editing threshold values, the clients only allow the user to specify the year and month
of the corresponding timestamp. Then the client will send a PUT command to the server (see
4
1
2 3

CIP-ICT-PSP-2012-6 – 325161
section 3.1.1.2) by adding a fictitious day to the specified date (ie. 2015-12-01). New PUT
values referring to the same year/month will overwrite the previous values.
Since threshold values are inserted with a bulk ingestion procedure, no INSERT command is
available for the client, but just a MODIFY one.
2.2.1.1 web client
The client shows:
 The requested system use thresholds [5] for all the months of the year. Changing the
day in the calendar on top allows to scroll the thresholds of the different months.
 The form to modify/delete [6] the thresholds for all the months of the year.
5 6

CIP-ICT-PSP-2012-6 – 325161
2.2.1.2 energy app
The client shows:
 The requested system use thresholds [5] for all the months of the year.
 The form to modify/delete [6] the thresholds for all the months of the year.
5
6

CIP-ICT-PSP-2012-6 – 325161
3 Server-side Service Specifications
3.1 Servizi RESTful (profili comfort e threshold buildings)
 Le risorse gestibili con i servizi REST sono profiles (profili comfort di temperatura attesa).
 Nella sintassi dei servizi REST il nome della risorsa è sempre al plurale.
 La chiamata a un servizio REST è costituita da una richiesta HTTP che utilizza un cosiddetto
verbo (GET, POST, PUT, DELETE …), a un URI di una risorsa a cui si riferisce l’azione del
servizio, corredata da eventuali parametri in stile “query string” (?par1=val1&par2=val2) e
con un eventuale “body” codificato in JSON o XML. Anche gli header vengono utilizzati per
qualificare meglio richiesta: Content-Type specifica ad esempio il formato richiesto. I
parametri della query string possono influenzare il comportamento del servizio (parametri
per effettuare ricerche, per paginare il risultato …). Nella risposta è essenziale il codice di
stato HTTP. Ad es.: 200  ok, 404  not found, 401  not authorized
 chiamata tipo:
HTTP VERB https://<baseURL>/<resourceURI>?<query_string> BODY
 I profiles stabiliscono la temperatura che si vuole avere in un determinato edificio in
determinati periodi della giornata. Per ogni edificio, sarà possibile stabilire un profilo di
comfort per ogni giorno dell’anno. Ogni profilo di comfort è quindi caratterizzato da:
edificio, giornata di attuazione. Ogni edificio è identificato dal suo id (buildingid) e dal
pilot (pilot) di appartenenza.
Ogni profiles si presenta in tal modo:
{"T":20,"INT":[{"from_hh":0, "from_mm":0, "to_hh":0, "to_mm": 0}]}
dove :
a. T : temperature attesa ( richiesta )
b. INT : array di 4 parametri che determinano il periodo di
interesse.
i. from_hh : identifica l’ora in cui il periodo inizia
ii. from_mm : identifica i minuti in cui il periodo inizia
iii. to_hh : identifica l’ora in cui il periodo ha termine
iv. to_mm : identifica i minuti in cui il periodo ha
termine
 Il modello dati di input/output è sempre in formato JSON
base URL: https://sunshine.sinergis.it/services/suggestion

CIP-ICT-PSP-2012-6 – 325161
RISORSA: profiles (dispositivi)
verb resource description
GET
<base_url>/css/<CODESPACE>/profiles?buildingid=
<BUILDINGID>&pilot=<PILOT>
Lista dei profili di comfort legati
all’edificio determinato dal
BUILDINGID di un determinate pilot
GET <base_url>/css/<CODESPACE>/profiles/<ID>
Dettaglio del profilo con id = <ID>
PUT <base_url>/css/<CODESPACE>/profiles/<ID>
Permette di modificare il profilo
indicato in uri. Ritorna il dettaglio del
profilo modificato. Il payload della
richiesta deve contenere il nuovo
profilo visto appena sopra
POST
<base_url>/css/<CODESPACE>/profiles?
buildingid=<BUILDINGID>&pilot=<PILOT>&daybelow=
<DAYBELOW>&dayupper=<DAYUPPER>
Permette di settare un periodo non
ancora presente in banca dati.
(I.E dayupper=2015-09-
05&daybelow=2015-09-03)
Gli estremi sono compresi nel periodo.
RISORSA: thresholds
verb resource description
GET
<base_url>/css/<CODESPACE>/thresholds?foiuri=<F
OIIDENTIFIER>
Dettaglio delle thresholds per lo shelter
con FOIIDENTIFIER specificata
GET <base_url>/css/<CODESPACE>/thresholds/<ID>
Dettaglio delle thresholds con id = <ID>
PUT
<base_url>/css/<CODESPACE>/thresholds?foiuri=<F
OIIDENTIFIER>&day=<yyyy-MM-
dd>&warmthreshold=<INT_VALUE>&coldthreshold=<IN
T_VALUE>
Permette di editare i valori delle
thresholds per uno specifico shelter e
una determinata data.
3.1.1 Esempi
3.1.1.1 Profili comfort per buildings
Dettaglio del profilo 461:

CIP-ICT-PSP-2012-6 – 325161
GET https://sunshine.sinergis.it/services/suggestion/css/FER/profiles/461
{
id: "461"
buildingid: "49146"
day: "2015-09-05"
comfortProfile: "{"T":20,"INT":[{"from_hh":0, "from_mm":0, "to_hh":0,
"to_mm": 0}]} "
pilot: "ferrara"
}
Modifica del profilo di comfort:
PUT https://sunshine.sinergis.it/services/suggestion/css/FER/profiles/461
Payload:
{"T":20,"INT":[{"from_hh":8, "from_mm":0, "to_hh":18, "to_mm": 0}]}
{
id: "461"
buildingid: "49146"
day: "2015-09-05"
comfortProfile: "{"T":20,"INT":[{"from_hh":8, "from_mm":0,
"to_hh":18, "to_mm": 0}]} "
pilot: "ferrara"
}
3.1.1.2 Thresholds sulle accensioni per shelters
GET
https://sunshine.sinergis.it/services/suggestion/css/TRN/thresholds?foiuri=http://www.sunsh
ineproject.eu/swe/featureOfInterest/TRN/shelter/SMI
{
thresholds:
{
id: "1"
day: "2015-12-26"
warmthreshold: "2"
coldthreshold: "5"
}
}

CIP-ICT-PSP-2012-6 – 325161
PUT
https://sunshine.sinergis.it/services/suggestion/css/TRN/threshold?foiuri=http://www.sunshi
neproject.eu/swe/featureOfInterest/TRN/shelter/SMI&day=2015-12-
26&warmthreshold=2&coldthreshold=3
{
thresholds:
{
id: "1"
day: "2015-12-01"
warmthreshold: "2"
coldthreshold: "3"
}
}
3.2 Servizi SOS (suggestion output)
Ad ora è stato attivato il suggestion per un edificio e per uno shelter. Sono state aggiunte due
tipologie di offering per permettere la catalogazione dell’output del suggestion :
CWRM_NUL_1d, CCLD_NUL_1d.
Rispettivamente, la prima rappresenta un contatore giornaliero adimensionale dei picchi di
riscaldamento e il secondo un contatore giornaliero adimensionale dei picchi di
rinfrescamento.
3.2.1 Building
Procedure : http://www.sunshineproject.eu/swe/procedure/FER-S12
Featureofinterest :
http://www.sunshineproject.eu/swe/featureOfInterest/FER/building/ScuolaElemPoledrelli
Offering :
 http://www.sunshineproject.eu/swe/offering/FER-S12_TEMP_CEL_1h
 http://www.sunshineproject.eu/swe/offering/FER-S12_ONOF_BOO_1h

CIP-ICT-PSP-2012-6 – 325161
3.2.2 Shelter
Procedure : http://www.sunshineproject.eu/swe/procedure/TRN-S47
Featureofinterest : http://www.sunshineproject.eu/swe/featureOfInterest/TRN/shelter/SMI
Offering :
 http://www.sunshineproject.eu/swe/offering/TRN-S47_TEMP_CEL_15
 http://www.sunshineproject.eu/swe/offering/TRN-S47_CWRM_NUL_1d
 http://www.sunshineproject.eu/swe/offering/TRN-S47_CCLD_NUL_1d

S.2.i Suggestion Service

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (7)

Ähnlich wie S.2.i Suggestion Service

Ähnlich wie S.2.i Suggestion Service (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

S.2.i Suggestion Service