09/11/2017 Reply Netcamp PoliTo - AWS IoT - Grohe and Caleffi Case Studies

1. IOT PLATFORM
Andrea Mercanti | Cloud Solution Architect | Storm Reply
Paul Kapteijn | Senior Manager | Concept Reply
Marco Garbarino | | Concept Reply

2. TODAY’S TOPICS
TWO ANSWER TO IOT
Two different solution to home automation
Implementation of IOT solution for different use cases in home automation

3. STORM REPLY
THE REPLY’S COMPANY FOCUSED ON AWS
70 Experts
CloudArchitects, DevOps, Microservices Architects
50 Top Brand Customers
Enel, Vodafone, Ferrero, Volkswagen, ePrimo, Grohe, etc
AWS Premier Consulting Partner
The only Italian company to have the highest level of
certification

4. CONCEPT REPLY
THE OFFERING
Concept Reply is a specialized consulting partner for IoT projects and part of the
Reply Network. We provide a multidisciplinary approach to cover all software
components of an IoT project. Technology independent. Agile.
Things
Firmware development
IT infrastructure
Backend implementation
App
IoT App development

5. IOT EXPONENTIAL GROWTH
IOT IN THE NEXT FUTURE

6. THE IOT PATH
OUR POINT OF VIEW
THINGS CONNECTED
THINGS
SYSTEM OF
THINGS
SYSTEM OF
SYSTEMS

7. The future is really simple with Amazon
AWS
SERVERLESS
PLATFORM

8. AWS GIVES YOU SUPERPOWERS

9. AWS SERVERLESS FRAMEWORK
API
GATEWAY
LAMBDA DYNAMODB
NO SERVER, NO PAIN
IOT
GATEWAY

10. DEVOPS METODOLOGIES
FAIL FAST, FAIL OFTEN

11.  No. 1 global brand in 150
countries
 6% global market share
 Strong positions in all key
markets; clear #1 position in
key European markets
Americas EMENA Asia
GROHE:THE WORLD’S LEADING
PROVIDER OF SANITARY FITTINGS

12. Freehander
Aquatower Europlus Costa
Grohtherm 3000RelexaEurosmart
Essence Eurodisc
10 YEARS AGO

13. F-Digital
Grohtherm Smartcontrol Sensia ArenaF-Digital Deluxe
GROHE Blue Home

14. BEFORE A DRIP
BECOMES A FLOOD
GROHE Sense & GROHE Sense Guard

16. WLAN
Router
Service
Provider
Mobile
Mobile
THE GROHE CLOUD
INDIVIDUALIZED
EXPERIENCE & SERVICES
FOR OUR CUSTOMERS
GROHE
GROHE
Sense
GROHE
Sense Guard

17. Enable remote monitoring of the home environment via
various Grohe Ondus devices on a mobile App
Enable device-to-device communication
Enable registering, configuring, controlling and
updating your Ondus devices from a mobile App
Enable device data analytics
THE USE CASES
OF THE GROHE ONDUS IOT CLOUD

18. GROHE IOT CLOUD
AWS ARCHITECTURE
Batch‘Speed’
Amazon
RedshiftAWS IoT
MQTT-WSS
AWS API
Gateway
Analytics Store
IdP:
G+, FB, IAM
Notif
handler
Data lake
Deviceconnectivitylayer
Datalayer
Servinglayer
Alarm
Notifcations
REST
API
S3
Analytics
dashboard
Amazon
SNS
Mobile App
Amazon RDSCognito
Thingshadow
Handler
DynamoDB
Alarm
handler
Quicksight
MeasCache
handler
User Profile
Passive
Alarms
AWS API
Gateway Device
Auth
Analytics
Load
Redshift
REST
Status data
BatchlogicSpeedlogic
APIlogic
Appliance
Push
Locations
Rooms
Profile
 Lambda architecture: speed, batch and serving layer
 Two main data flows: IoT and mobile app

19. 4 Months
from scratch
to first version
4 Environments
dev, stag, pre-prod,
prod
45 REST API
endpoints
50 LAMBDA
functions
9 NOSQL
DynamoDB
tables
8 SQL
RDS tables
7 REDSHIFT
datawarehouse
tables
26 IAM
security roles
6 IOT GW rules
for dispatching
15 AWS PaaS
services
Xxxx Devices
live in production
GROHE IOT CLOUD
SOME NUMBERS

20. GROHE IOT CLOUD
 Reduce the task of a single Lambda function
• More Lambda functions
• More Lambda running in parallel
 API Gateway, integration timeout is 30 seconds, make sure your
API logic doesn’t take longer
 Use the AWS services at their full capabilities
 Sending “commands” from both Mobile-App and IoT devices is not
obvious
LESSONS LEARNED

21. WHAT’S NEXT?
FURTHER DEVELOPMENT
SYSTEM-OF-SYSTEMS INTEGRATION
FIRMWARE UPDATE CAMPAIGNS
MORE DEVICES
ANALYTICS

22. CALEFFI: CONNECTED PRODUCTS
Caleffi develops and manufactures components
for heating, air conditioning and sanitary
systems, heat accounting systems and specific
components for renewable energy plants.
In 2016 it has more than 1,000 employees
distributed between the Italian
headquarters and the foreign branches, it
sells in more than 70 countries.

23. USE CASE
FULL CONTROL FROM EVERYWHERE

24. USE CASE
TAILORED WARNING NOTIFICATION

25. USE CASE
REMOTE DEVICE CONTROL

26. GOALS
Remotely control of Caleffi devices
Allow communication between Caleffi
devices of different kinds.
Caleffi objects able to talk also with other
systems.

27. Direct configuration
Local Data Access
Remote Data Access
Mobile App
Web App
Back-end server(s)
Front end web server
1
2
3
4
SOLUTION

28. Direct configuration
MOBILE APP

29. Local
DB
Remote
Content
Retriever
Local
Content
Retriever
Orchestrato
r
Configuration
engine
Messages
Notification
Engine (Local
& Remote)
Events
Viewer Web- View
Rule
Engine
Backend Server
Gateway
HTTPS
MOBILE APP ARCHITECTURE

30. AWS Backend Server
Mobile App
Smart
Gateway
Amazon Echo
Google API.AI Platform
Google Home
AWS IoT Platform
Smart Gateway
Device SDK
ENVIRONMENT

31. External
HARDWARE ARCHITECTURE
THERMOSTAT MODULE ARCHITECTURE
power supply
RF Module MPU WiFi module
LED(s) button
external
antenna
external
DC power
supply
external

32. RF Module Field Module
AWS IOT
GATEWAY: SOFTWARE
ARCHITECTURE
Device interface – Rx/Tx MQTT - HTTPS
AWS KINESIS
Communication &
Configuration Interface

33. CLOUD ARCHITECTURE
SNS
Push
notification
IOT
• Devices
enrollment
• Devices
management
• Real time
commands
RDS
• User
accounting
• Data
storage
EC2
• Services
• Gateway
and Mobile
Backend
• Dashboard/
Frontend

34. FINDING
WHAT WE LEARNED
Design and develop a full stack solution is NOT SIMPLE
Reply is able to support clients in this challenge
providing first class know-how for these use cases

35. Make the solution even more generic and flexible:
Current solution is tailored for Caleffi devices, the challenge is to evolve the system in
order to create software modules able to be as much hardware-indipendent as
possible
Develop software layers in order to not depend on specific third
part IOT Services
Very often clients have specific requests on framework and technologies to use in
their solution, next step is to make the system as much IOT framework-indipendent as
possible
New devices
Open/Closed window sensor
NEXT STEPS

36. THANK YOU!