This session provides a technical overview of a new-generation core IoT platform, designed and implemented by Enel in partnership with AWS IoT. The core IoT platform provides a single architecture and a common set of services that will be adopted by existing and future IoT applications across different business units at Enel. We analyze use cases with a live showcase of platform capabilities. We also demonstrate how the core platform enables Enel to build resilient and scalable business solutions by leveraging existing and leading-edge AWS services, such as the AWS IoT Device Gateway, AWS IoT Device Shadow, and AWS Greengrass.

1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
IoT @ Enel:
A New Generation IoT Core Platform
I g n a c i o B e r e n g u e r G a r c i a – P r o g r a m M a n a g e r - E n e l
F e d e r i c o S e n e s e – S e n i o r C o n s u l t a n t – A W S
N o v e m b e r 2 8 , 2 0 1 7

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Objectives & Agenda
Enel at a glance
Why is IoT interesting for Enel?
Why did we choose AWS IoT?
What did we do?
Take-away
Present how Enel will use AWS to build IoT solutions for our customers

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
World leading integrated
electricity and gas operator
https://www.enel.com/es/medios/Album.0.620.es-es.2.9.html

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
83 GW
capacity of electricity generation
https://www.enel.com/es/medios/Album.0.119.es-es.1.9.html

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
2.1 million km
electrical network
https://www.enel.com/es/medios/Album.0.123.es-es.3.9.html

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
65 million
customers
https://www.enel.com/es/medios/Album.0.123.es-es.4.9.html

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Why IoT is important
for Enel?
https://www.enel.com/es/medios/Album.0.120.es-es.1.9.html

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Open Power
https://www.enel.com/es/medios/news/d201709-enel-nica-empresa-de-servicios-en-el-top-50-change-the-world-list-de-fortune.html

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Open Power
We are opening energy access to
more people
We are opening the world of energy
to new technologies
We are opening new ways for people
to manage energy
We are opening new uses of energy

10. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
IoT @ Enel
Residential
Customers
Industrial
Customers
Industrial
Installations

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Why Enel uses AWS IoT?
Strategic choice
Time to Market
Future Proof
Scalability
Manageability

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Using AWS IoT @ Enel
Smart Home for Residential Customer
Motion
detected
Event
Switch on the
light
Action
IoT
Lambda
S3 DynamoDB
Example use case: home
automation for residential
customers
The scenario should work also
without cloud connectivity

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
IoT Architecture @ Enel
IoT
Device
Management
API
Storage
Gateway
Devices

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Storage
Gateway
Devices
AWS
Greengrass
IoT
AWS
IoT
Amazon
S3
Amazon
DynamoDB
API
Data
Aggregation
API
Command
API
Control
Mgmt. API Amazon
API Gateway
Rules API
Device Management
External
System
s
IoT Architecture @ Enel
Internal
Systems
AWS
Greengrass
Device
Registry
Device
Shadow
Amazon
ElasticsearchAWS
IoT
Lambda
functions
AWS
Lambda
AWS
Lambda

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
IoT Gateway Activation
Description
Architecture diagram
Technical challenges
U s e c a s e 1

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
IoT Gateway Activation - Description
Gateway is manufactured
and shipped to customer
Customer opens the box
and connects the Gateway
to Internet
Gateway is auto-
provisioned and connected
to IoT Platform in the Cloud

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
IoT Gateway Activation - Demo
 IoT Gateway is in factory status
 User connects the IoT Gateway to Internet, and switch power on
 IoT Gateway activation will run completely unattended
 We will open a console window to see IoT Gateway boot process
 After IoT Gateway is auto-provisioned we will check using AWS
console
o AWS IoT Device Registry
o AWS Greengrass
 Finally we will see how the IoT Gateway is sending information to
AWS IoT

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Architecture diagram
Gateway
AWS
IoT
1. Certificate activation
AWS Lambda
2. Gateway registration
AWS Lambda

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
1. Certificate activation
Gateway
Gateway
certificate
AWS
IoT
CA
certificate
IoT
rule
Lambda f Gateway
certificate
IoT
policies

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
2. Gateway registration
Amazon S3
Lambda f AWS IoT
Device Registry
AWS
Greengrass
Gateway
AWS
IoT
IoT
rule

21. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
2. Gateway registration — details
Register gateway
• Create thing
• Apply security policies
• Configure Amazon S3
resources
• Configure AWS
Greengrass group
Rollback
• Remove AWS
Greengrass group
• Remove Amazon S3
resources
• Remove security policies
• Delete thing

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Technical challenges
 A certification authority can be deployed only once per region
o Use multiple CAs across multiple business units and staging
environments
 Gateway registration involves multiple steps that may fail
o Incorporate retry logic, where possible
o Ensure consistency by including rollback option

23. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Rule execution @ Edge
Description
Architecture diagrams
Technical challenges
U s e c a s e 2

24. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Rule Execution - Description
A rule is configured by the customer:
“If motion is detected by the motion
sensor, the light must be switched on”
Rule is persisted in the IoT Gateway
When the event is triggered, the rule
should be executed, regardless
Internet connectivity

25. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Rule Execution - Demo
 In the demo we have an IoT Gateway connected to the IoT
Platform, and two sensors paired: motion sensor and Smartplug
 We are going to create a rule using an API. We will use Postman
for calling the API
 The rule is going to be inserted in the device shadow of the
triggering sensor
 Then we will see the rule execution in connected and
disconnected scenarios

26. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Architecture diagram
AWS
IoT
Amazon
API Gateway
Amazon
DynamoDB
1. Rule configuration
AWS Lambda
Gateway
AWS Greengrass
Device 1
Device 2
2. Rule execution

27. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
1. Rule configuration
Gateway
Amazon API
Gateway
Lambda f Amazon
DynamoDB
Lambda f IoT
shadow
AWS
Greengrass
IoT
shadow

28. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
{
“reported:”:
{
…
"RULES":
[{
"NAME": "RULE1",
"TRIGGERS": [
{"THING":”device1","SENSOR":”motion_detected",”OPERATOR”:”==“,"VALUE":”true"}
],
"ACTIONS":[
{"THING":”device2","SENSOR":”power","VALUE":"ON"}
]
}]
}
}
Rule definition — shadow document

29. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Greengrass Core
IoT shadow Lambda f
Amazon
DynamoDB
IoT rule
AWS IoT
Lambda fIoT rule
Device 1
Device 2
Trigger
2. Rule execution
Logging
Action in AWS cloud
Action

30. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Technical challenges
 Custom IFTTT (IF-This-Then-That) rule engine
o Designed for simple cases
o Complex cases – involving multiple triggers and actions – require ad-hoc
optimizations
 Local repository for rule configuration
 General purpose storage not provided by AWS Greengrass
 Leverage IoT shadow mechanism
 Rule size limits
o Device shadow size limit (8 KB)
o Upper-bound limit to the number of rules – average rule size

31. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Conclusions

32. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Take Away—Enel
Convergent IoT
Platform
Trained our
development
teams
Governance
model for IoT
Platform
evolution
We are ready to
use IoT to
transform the
use of energy

33. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Take Away—AWS
Serverless
architecture
Leverage AWS
IoT capabilities
Time to market Future proof

34. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
THANK YOU!
I o T @ E n e l