IoT Technical Roadmap

1. I O T T E C H N I C A L
R O A D M A P
D E S I G N E D F O R I O T S T A R T U P B Y R E I D L A I

2. R E Q U I R E M E N T
O V E R V I E W
P A R T 1

3. B U S I N E S S R E Q U I R E M E N T
S U M M A R Y

4. C O R E M O D U L E S
I o T
P l a t f o r m
C a s e / P a l l
e t
R e a l t i me
M o n i t o r i n g
M e m b e r s h
i p a n d
U s a g e
B a s e d
B i l l i n g
P r e d i c t i o n
S e r vi c e
I o T
A s s e t s
e C o m m e r c
e S t o r e
I o T
A s s e t s
L i f e c yc l e
M a n a g e me
n t
I o T
A s s e t s
O r d e r
F u l f i l me n t

5. M e m b e r s h
i p a n d
U s a g e
B a s e d
B i l l i n g
I o T
A s s e t s
O r d e r
F u l f i l me n t
C O R E M O D U L E S
I o T
P l a t f o r m
C a s e / P a l l
e t
R e a l t i me
M o n i t o r i n g
P r e d i c t i o n
S e r vi c e
I o T
A s s e t s
e C o m m e r c
e S t o r e
I o T
A s s e t s
L i f e c yc l e
M a n a g e me
n t

6. P R O D U C T R O A D M A P
P A R T 2

7. T E C H N I C A L P R O D U C T R O A D M A P

8. P R O O F O F C O N C E P T
P A R T 3

9. C O N S T R A I N T S
• No information about sensor public access
communication - MQTT/AMQP/HTTP
• No information if sensor can be deployed with X.509
certificate
• Limited timeframe to deliver Proof of Concept
• No hardware on hand
• Learning curve about EPC tag format

10. D E C I S I O N P O I N T S / F A C T O R S
• Choosing between MQTT and AMQP protocol
• Sensor capability to support X.509 certificate deployment
• Comparing between Amazon AWS IoT and Microsoft IoT
Hub (Google IoT does not support MQTT)
• Choosing base board compatible with both AWS and
Azure
• Fast monitoring and dashboard implementation

11. P O C B U I L D ( 1 7 F E B 2 0 1 7 )
• Use MQTT v3.1.1 (bi-directional) with TLS v1.2 (X.509
certificate)
• Use Grove starter kit plus (optional) - because PST use ECP
Class 1 Gen 2 as communication standard between tag and
reader (All-in-one package for Intel Galileo Gen 2 and Edison)
• Use Azure IoT SDK - supports ANSI C, .NET, Java, NodeJS
and Python (AWS SDK only support C and NodeJS)
• Use FluentD to collect MQTT log message and forward to
InfluxDB stack running on Azure Container Service for fast alert
and bashboard prototype development

12. P O C D E L I V E R A B L E S
• EPC RF sensor simulator
• IoT message will be forward to Azure IoT Hub through MQTT v3.1.1 protocol with TLS 1.2 support
• Messages will be delivered to time series database (InfluxDB) for real-time Dashboard (Grafana)
• Draft RF sensor requirement
• Draft requirement of
• Tag EPC URI
• Reader URI
• numerical representation of the temperature
• location
• time stamp

13. P O C O V E R V I E W