The document discusses using an IoT analytics platform for measurement and knowledge extraction from big data in IoT. It covers:
1. The business opportunity of IoT with over 10 billion connected devices generating data that can improve understanding and decision making.
2. An IoT analytics platform that ingests, processes, stores, analyzes and publishes/visualizes data from diverse sources. It discusses modules for integration, processing, machine learning, APIs, dashboards and more.
3. Two use cases - energy segmentation using clustering algorithms on consumption data, and traceability in distribution using real-time monitoring of deliveries.
From measurement to knowledge with sofia2 Platform
1. From measurement to knowledge
Big data and real time analytics in the IoT
http://twitter.com/SOFIA2_Platform
http://about.sofia2.com
plataformasofia2@indra.es
http://sofia2.com
5. 5
IoT as a Business Opportunity
More than
10 billion of
connected
devices
Plus 10-20
billions to add in
the next 10 years
Only 1% o fthe
data is actually
used (as
alerts, event
triggering….)
Devices generate a continuous flow of data whose acquisition
and analysis will allow us a better understanding of reality and
an improvement and faster decision making.
We will have a volume of data without coming, which will allow us
to extract an extensive knowledge of the client and with this to
offer the customer custom solutions to measure and participate
in their day to day
Internet Of Things
terminology was used
for the first time on 1999
referring to identifiable
objects (things) and its
vistual representation in
an infrastructure.
Business Processes Transformation
New Business Models
6. 6
Why using IoT?
The Goal
Making better and faster business decisions by the combination of real-time process and
analysis of the information.
7. 7
IoT Mainstays
Integration & Connectivity Process and Analytics
IoT Flow Social flow General
SystemsDevices
…
RRSSAPIs G.Analytics PIWIK
Y.Finance …
“Interoperability between IoT systems is critical. Of the total
potential economic value the IoT enables, interoperability is
required for 40 percent on average and for nearly 60
percent in some settings.” McKinsey
“Currently, most IoT data are not used. For example, on an
oil rig that has 30,000 sensors, only 1 percent of the data
are examined. That’s because this information is used
mostly to detect and control anomalies—not for optimization
and prediction, which provide the greatest value.” McKinsey
8. 8
Types of IoT Analytics
Descriptive
Predictive
Prescriptive
Pushes and Alerts
Embedded Models
Streaming
Realtime Analysis
What question to answer? What method to apply?
Combining both perspectives we can get many applicable use-cases
13. 13
Administration, Security, Monitoring, Control
Business apps
Custom apps
Sensors and devices
Storage Publish
People
Third Party
Systems
INGEST
Bulk, Event Ingestion
PROCESS
Preparation, Anaytics
VISUALIZE
IoT Platform Information Flow
14. 14
IoT Broker
Light communication
Protocols: REST,
MQTT, WS, etc…
Development APIs &
SDKs
Real time processing.
Rules and flows
Semantic model
Real Time
Repository
Big Data Repository
Staging Area
Notebooks:
• Algorithm
Execution
• Schedulling
• Data Scientist
collaborative
environment
• Exports and
Visualization.
Machine Learning:
• Algorithm
Execution
• Parametrization
• Publication
• Machine Learning
inference
API Manager:
Service Publication
and lifecycle
management
Dashboards &
synoptics
Diifferent options to
configure
dashboards for
realtime & analytics
visualization of the
data
Open Data
Portal:
Opendata
publication in
different standard
formats.
Data Links:
ODBC & JDBC
Access to data
Data Flow
Visual ETL style
model.
Bacth ingestión.
Monitorization
Stadistics & graphics
Heterogeneous
sources of information
IoT Platform Functional Capabilities
15. 15
Platform Modules
Discovery
Apps & VerticalIoT Flow
Social flow
General
SOURCES INGEST & PROCESS STORE ANALYZE PUBLISH & VIEW
SystemsSDKs
Java Javascript
Python Android iOS
.Net R C(C++ …
Devices
…
RRSSAPIs
G.Analytics PIWIK
Y.Finance …
IoT
Gateway
IoT
Broker
Ontology
Stream
Process
Sofia2 Storage
Real Time Database
Notebooks API
Manager
DataLink
HTML5 & API
MANAGEMENT
CONFIG
DB
Sofia2
Control Panel
Security
Historical Database
Staging Area ODBC
JDBC
Dashboards
Ontology
APIs
VerticalSystemsAppsExplotationVisual
Plugins
REST
Ext APIs
Open Data
Portal
Synoptics
CEP
Ontology
Flows
MQTT
… APIs
Rules
Bots
ML Engine
SPACES
DEVICES
Devices
SEMANTIC
Custom
Integration
DataFlow
BigData Ingestion
17. 17
Energy Segmentation
Context / complexity
• Electricity consumption information retrieval
• Segments for the organization of consumption patterns / Period of the
customer set.
• Consumer recovery and trend analysis.
Technological solution
• Collection and storage of sources: Ingestion in HDFS.
• Data exploration: Understanding its distribution, quality, volumetry.
They are data of hourly curves of 6 months.
• Cleaning of data and selection of relevant information.
• Indicators generation by CUP and Period.
• Inference of new data to complete dataset.
• Application of K-means algorithm and elbow technique for selection
of K.
• Analysis of results
18. 18
Energy Segmentation
Apps & VerticalIoT Flow
Social flow
General
SOURCES INGEST & PROCESS STORE ANALYZE PUBLISH & VIEW
SystemsSDKs
Java Javascript
Python Android iOS
.Net R C(C++ …
Devices
…
RRSSAPIs
G.Analytics PIWIK
Y.Finance …
Stream
Process
Sofia2 Storage
Real Time Database
Notebooks API
Manager
HTML5 & API
MANAGEMENT
CONFIG
DB
Sofia2
Control Panel
Historical Database
Staging Area
JDBC
Dashboards
Ontology
APIs
VerticalSystemsApps
Ext APIs
CEP
Ontology
Flows
APIs
Rules
ML Engine
SPACES
DEVICES
SEMANTIC
DataFlow
1
2
3 4
5
19. 19
INGEST / STORE ANALYZE PUBLISH & VIEW
Capabilities
Visual ETL modelling. Java extensible. Integrated in Sofia2
Control Panel
(HTML5)
Debug and Preview. Sources & destinations:
Kafka, Hadoop, JMS,
JDBC, AmazonS3…
Alerts and
Notifications
Deployment integrated
on Control Panel.
18 available processors
for ETL modelling: Split,
hasher, remover, merger…
Charts and execution
statistics visualization
Energy Segmentation
20. 20
Energy Segmentation
INGEST / STORE ANALYZE PUBLISH & VIEW
Optimized for and agile and real time access to the
information.
Real Time Data Base
Optimized not the storage and management of big
Data, not so often accessed.
Historical Data Base
Capabilities
One repository per each
moment on the lifecycle
of the information.
Support to different
technologies depending
on the information access
pattern.
Standard support and SQL
& NO-SQL databases
Access to the information
with optimized
response times.
Horizontal Scalable. Different repositories
are integrated between
them and with other
modules of the platform
Each entity of the data model have a
configured time-window, in order to
identify the data stored as historic or real-
time information
Information will be persisted in the real-
time database until it would be
automatically moved to the historical
database.
Any information (real-time or historical)
will be accessible from any of the other
modules of the platform: Integration,
Machine Learning, APIManager
Differential
Staging Repository
For structured, semi-structured and unstructured
data, as a temporary holder in case of transform
processess requiring persistence.
21. 21
Energy Segmentation
INGEST / STORE ANALYZE PUBLISH & VIEW
Capabilities
Interpreter Management
(sh, jdbc, md, angular…)
Shared and
multiuser environment
Data Scientist IDE.
Multilenguaje execution
on the same notebook
(SparkSQL, R, Hive, Scala,
Python)
Instant visualization of
results with
incorporated charts
Invocable from
other platform
moduels such as
Realtime
Processing Module.
Schedulled execution of Web environment
integrated in the
Control Panel of the
platform
Export and
visualization
22. 22
Energy Segmentation
INGEST / STORE ANALYZE PUBLISH & VIEW
Capabilities
Configurable Gadgets
with integration and
querying capabilities to
the Repositories
Configurable
Dashboards reusing
gadgets, with drilldown
and cascade
dependencies, URL
exposition and CSS
customization
.
Dashboards
23. 23
Energy Segmentation
YouTube
Sofia2 IoT Platform
• Demos and viewers
• Sofia2 presentations
• Workshops and
tutorials
• Dashboards
• Technical support
• Solutions built on
Sofia2
24. 24
Traceability in distribution: Executive Dashboards
Context / complexity
• Solution for automatic verification of delivery punctuality, next point arrival
forecast update and temperature ranges verification during stores supply.
• Monitoring and registration of Arrival time to store
• Early warning + Expected arrival time notification to the next store
• Traceability of goods delivered and collected at each store
• Online monitoring of delivery operations
Technological solution
• Real Time Management & Reporting system.
• Black-box (GPS & Mobile Comms.) + Beacons integrated with The Route
Planning system.
• Sofia2 as core for device integration, data analytics, calculations, events
detection and notifications.
Results
• Greater efficiency in distribution, store unloading and platform
loading
• Avoid management conflicts with transportation providers and
internal customers or franchisees
• Compliance with temperature transport regulations
• Reduction in the loss of means and its control, as well as of the
goods in transit
• Improvements in route planning and contracting suppliers
• Improve efficiency in all internal processes of the value chain:
• Verification of load units sent in the correct vehicle
• Control of in route stops + openings control
• Verification of load units left and loaded at each stop
• Selective inventories of accumulated media in stores and
warehouses
• Truthful and timely information for the management of
incidences of distribution or lack of means
a
a
ab b
b
c c
c
(tª) (tª)
25. 25
Traceability in distribution: Executive Dashboards
Apps & VerticalIoT Flow
Social flow
General
SOURCES INGEST & PROCESS STORE ANALYZE PUBLISH & VIEW
SystemsSDKs
Java Javascript
Python Android iOS
.Net R C(C++ …
Devices
…
RRSSAPIs
G.Analytics PIWIK
Y.Finance …
IoT
Gateway
IoT
Broker
Ontology
Stream
Process
Sofia2 Storage
Real Time Database
Notebooks API
Manager
HTML5 & API
MANAGEMENT
CONFIG
DB
Sofia2
Control Panel
Security
Historical Database
Dashboards
Ontology
APIs
VerticalSystemsApps
Plugins
REST
Ext APIs
CEP
Ontology
Flows
MQTT
… APIs
Rules
SPACES
DEVICES
Devices
SEMANTIC
1 2
3
4
26. 26
Traceability in distribution: Executive Dashboards
INGEST / PROCESS & STORE ANALYZE PUBLISH & VIEW
Capabilities
Communication
connectors for different
client’s programming
language.
Development APIs for
the client side.
Security capable in
terms of communication,
authentication and
authorization.
Light communication
protocols (REST, OPC,
MODBUS, WebSockets,
MQTT, WS, JMS, AMQP…)
Real-time processing and
validation of the
interchanged information.
Homogenization of the
information received,
according to the data model
defined (protocol
independent)
Java Extensible (APIs,
Protocols, Plugins)
Auditing of integration
activity
Integrated in Sofia2
Control Panel (HTML5)
27. 27
Traceability in distribution: Executive Dashboards
Capabilities
Real time processing of
the information received
Different coding
languages supported
(Groovy, R, Python).
Integrated with other
modules of the platform
such as repositories or
notebooks.
Capabilities for simple
IFTTT, CEP or visual
definition of flows
Alerts, notifications,
enrichment of
information…
Managed and monitoried
from Sofia2 Control
Panel (HTML5)
INGEST / PROCESS & STORE ANALYZE PUBLISH & VIEW
28. 28
Traceability in distribution: Executive Dashboards
INGEST / STORE ANALYZE PUBLISH & VIEW
Capabilities
Integrated Security
(authenticación,
autorization,
encription…)
Data can be published
independently of the
repository storing the
information (real time
or historical)
Custom Query
commands, APIs clone,
HTML5 CRUDs
generated automatically
Integration with third
Party APIs including
Open Data or
WebServices to be
Apified
.
APIs Lifecycle
managemen (Created,,
in Process of
development, published,
dDeprecated, Removed)
Throtling control and
auditing of the activity
29. 29
Traceability in distribution: Executive Dashboards
YouTube
Sofia2 IoT Platform
• Demos and viewers
• Sofia2 presentations
• Workshops and
tutorials
• Dashboards
• Technical support
• Solutions built on
Sofia2
At its core, digital transformation with the IoT involves making better, faster business decisions. Traditionally businesses would use end-of-the-day reports and relied heavily on Excel spreadsheets to optimize operations. Organizations started moving to data warehouse models in the 1990s, but data analysis often took hours or days.
Today it is possible to connect business processes and systems to the internet, such as for enterprise resource planning and customer relationship management. And through the explosion of machine sensors and networks, it is now possible to connect point-of-sale systems, manufacturing equipment, or devices used in smart buildings.
Gartner, in fact, predicts that more than half of major new business processes and systems will incorporate some element of the IoT by 2020. Use cases enabled by the IoT are extensive:
When point-of-sale data is combined with manufacturing and warehouse data, a retailer can optimize their supply chain to increase sales and ensure a smooth customer experience.
A manufacturer could predict when a piece of equipment might fail, or spot defects on a production line, saving millions of dollars.
A smart building might continually adjust the temperature in certain rooms, solar output, or lighting, leading to substantial energy savings.
A transportation or shipping system could reroute during times of congestion, thus improving customer experience and gaining insights on future planning.
But integration has been cited as one of the top and most costly barriers to adopting IoT analytics. Gartner has estimated that through 2018, half the cost of implementing IoT solutions will be spent on integration. The average cost per project of integrating device, data and systems is about $8 million per project. McKinsey & Company, meanwhile, pegs 40 percent of the value of the IoT on interoperability.
https://www.rtinsights.com/iot-analytics-use-cases-tdwi/
Pushes and alerts: A popular example includes beacon technology, which is used by brick-and-mortar stores such as Macy’s, Target, and Lord & Taylor to offer personalized, hyper-local, and in-store retail promotions through a smartphone app.
Streaming: Often analysis has to be done in-memory and immediately, such as that with complex event processing. Some examples of CEP include scoring financial transactions as they occur to prevent fraud; processing video events; and detecting collision.
Embedded Models: With real-time data, rules can be generated to trigger actions if certain patterns in the data stream are detected.
Predictive maintenance; cancer detection/treatment support
[llamada a la acción] A principios de 2017 entra en vigor la Nueva Directiva de Pagos, de ámbito europeo (PSD2), que supondrá una revolución aún mayor en el mundo fintech, al permitir que cualquiera pueda convertirse de facto en un banco. ¿Estarán todas las empresas en disposición de garantizar la seguridad de la operativa económico financiera al igual que lo han venido haciendo los bancos hasta ahora? Parece natural descansar en un aliado de confianza como [Newbrand].
Cómo es el mercado??
Driver de crecimiento: transacciones online
Tipología (gama de productos/servicios disponibles online)
Número de clientes digitales (incidencia sociodemográfica)
Clientes digitales activos: volumen de transacciones por cliente (número e importe)
Catalizador Normativo:
GDPR
PSD2: apertura del mercado de pagos; proveedores de servicios de acceso a cuentas corrientes… securizando los actuales mecanismos de pago, y protegiendo al consumidor y su gobierno de credenciales
Segmentación por naturaleza:
Geográfico: de ámbito nacional o comunitario – por regulación y por utilidad del perfilado y base de clientes
Sectorial:
Tamaño:
Global: estimado en un orden de magnitud superior al mercado de pagos
Cómo se llega a él?
Entidades financieras:, Operadoras de Telecomunicaciones, Organismos de monitorización y consulta de fraude