Professional Documents
Culture Documents
1JFHCL11omra.....,_
•
• YOUR FIRST MILESTONE IN A
SUCCESSFUL IoT JOURNEY
IoT Reference Architecture Guide
-
.... ~ .....
Authors
MIKE SUYAMBUNATHAN
BEVIL GOPAL
Director, IT Innovation, Solution Director, IoT,
Merck & Co., Inc. HCL Technologies
NITIN
KAUL
Associate Director,
IT Architecture,
Merck & Co., Inc.
loTWoRKS~
byHCL~
Introduction
''
forces that drive business. As organizations across industry
sectors examine and evaluate how the utilization of IoT In order to realize the true
capabilities can improve the way they manufacture products, benefit of IoT, enterprises
provide services, and manage their supply chains, the should consider adoption of
pharmaceutical industry has a compelling opportunity to
a platform-based approach
adopt and profit from these game-changing technologies.
Some early adopters have already started exploring IoT to
enable end-to-end digital integration across the value chain.
•
ability of IoT to collect huge amount of data and provide
relevant insights.
laTWoRKS~
O,HCLa..taa rur
Need for Reference Architecture
''
reference models, and best practices improve the success
rate of investments on new solutions, ensure lower cost in Improvement in the success
both short and long terms (Total Cost of Ownership), provide rate of investments on new
a frame for policy implementation and improve service solutions, lower cost (Total
delivery to end users. Here are some key reasons for building
Cost of Ownership),
a reference architecture in an enterprise context:
a frame for policy
implementation and
To converge silo IoT initiatives/solutions with
corporate IT solutions
improved service delivery
to end users
Most of the business units within large enterprises are
building their own IoT solutions as point solutions, without
adhering to the standards. This hinders the possibility of
cross-leveraging the solutions across other business units. As
a long-term and strategic solution, we often recommend our
customers to take a ‘Federated’ approach (as depicted in the
below diagram) to build IoT solutions. According to this
approach, the Corporate IT team should take the
responsibility of building the best practices, architecture
guidelines, multi-modal data structures, security and
governance practices, etc., which would be common across
business units. In a nutshell, the Corporate IT team should
incorporate all these common guidelines and best practices
in the form a Reference Architecture and ensure its adoption
across business units. This will take away a lot of burden
from the individual business units and they can focus on
building their specific use cases leveraging the platform
reference architecture. This also helps in providing a
level-playing ground for all the business units, irrespective of
their maturity levels, to pursue their IoT initiatives.
❖ ME~~T~ FOR L FE
which will be relevant to the business. For instance,
Corporate IT / Central IT
creating a device category list based on the
connectivity supported by the device (as shown below):
Reference Architecture
Standardized Information Model (Patient & Asset)
Standard Platform Services (Hot Path, Cold Path) DEVICE FEATURE EXAMPLE
TYPE
Standard Gateway
Type 1 Non IP Capable - Analog Sensors
Security and Governance
& Digital Output Sensors
Best Practices and Architecture Guidelines and Attached Devices
1. Connectivity Management – To connect various devices, systems, and networks in an IoT ecosystem
2. Data Aggregation and Storage – To collect data from devices & systems, and store them for further processing
3. Application Enablement – To build custom IoT solutions for the chosen business use case
The below mentioned diagram provides more details on each of these capabilities:
These capabilities can be delivered through a 3-tier IoT logical reference architecture as depicted below:
SECURITY
.--------------------~.
o Device I
Control Flow
API
Control Flow
Custom Apps
'I Management Application
'
UI UI
API Gateway
Rules & Control
: I
'····················~ '··-···-··--··-··--··-···-·· ··--------------------------
Edge Tier Platform Tier Enterprise Tier
0 MERCK
INVENTING ron L rE
Tier 1: Edge
Tier 2: Platform
The Platform Tier consolidates, processes, and analyses data
flows from the Edge Tier and provides management
functions for devices and field gateways. This tier receives,
processes, and forwards control commands from the
Enterprise Tier to the Edge Tier. It also offers
non-domain-specific services, such as data operations and
analytics.
Tier 3: Enterprise
Receives data flows from Edge & Platform tiers and issues
control commands to these tiers. The Enterprise Tier
implements enterprise domain-specific applications and
decision support systems and provides interfaces to end
users, including operations.
laTWoRKS~
O,HCl..1'ufl.a r ur
Key design considerations
The IoT reference architecture provides guidance for Agility: With IoT becoming mainstream with new
building secure and scalable, device-centric solutions for requirements and opportunities arising over time,
connecting devices, conducting analysis, and integrating the architecture must aid in the quick launch of new
with backend systems. Here are the key considerations in data services and applications.
building a reference architecture that can be used to build
scalable IoT Solutions. Modular and loosely coupled: Each of the layers in
the IoT reference architecture must be designed in a
Security: IoT solutions often integrate with existing modular way and should be independent of each
technologies and processes that are vital to the core other. This will help to leverage best of the breed
operation of the business. As a result, the resilience of supplier technologies for each layer and also for
these systems is important and security is deeply linked each of the features supported by a layer.
with resilience. As mentioned in the previous diagram, the
reference architecture should take into account security Based on open standards: Communication between
and privacy measures across all areas, including device the layers of the reference architecture must be
and user identity, authentication and authorization, data based on open standards to ensure interoperability.
laTWoRKS~
O,HCl..1'ufl.a r ur
Technology choices for implementing
IoT Reference Architecture
The choice of right technology and platform for the
development of IoT solutions is vital for any organization to
succeed in its IoT journey.
Connectivity
To begin with, our recommendation is to select a platform
management, data
which offers all three IoT capabilities outlined previously -
connectivity management, data aggregation and storage,
aggregation and storage,
and application enablement. Having these elements in place and application
and fully integrated is important for building end-to-end IoT enablement are
solutions. important for building
end-to-end IoT solutions
The other important criterion is to consider openness and
ease of integration. We recommend selecting an IoT
platform that meets the business needs and permits
deployment with minimal disruption to existing systems. An
open framework will be modular, with easy-to-use APIs, and
an easy-to-integrate framework will fit smoothly with
existing IT architecture.
laTWoRKS~
o,HCL
1'ufl.a r ur
Pharma Transformation led by IoT
•
of preserving and improving human life ethically and with
integrity, Merck’s mission is to provide society with superior
products and services by developing innovations and
solutions that improve the quality of life and satisfy
customer needs, and to provide employees with meaningful
work and advancement opportunities, and investors with a
superior rate of return.
About
IoT WoRKSTM, a dedicated IoT business unit of HCL
Technologies, enables organizations to create best-in-class
business solutions by maximizing effectiveness and returns
on their asset investments. Rated as a global leader in IoT
consulting & services by top analysts, our solutions enable
IoT-led business transformation through creation of more
efficient business processes, new revenue streams and
business models that deliver measurable business outcomes.
The transformative impact of IoT is realized by IoT-izing the
‘things’, connect the assets to a data platform and then use
the data to derive business insights and take business
decisions which ultimately lead to change in enterprise
processes and people practices.
laTWoRKS~
o,HCL
1'ufl.a r ur
loTWaRKS"
,,,HCI. acta:«::uv»s
To know more about IoT WoRKSTM and its capabilities visit hcltech.com/IoT
or write to us at iotworks@hcl.com
Hello there! I am an Ideapreneur. I believe that sustainable business outcomes are driven by relationships nurtured through
values like trust, transparency and flexibility. I respect the contract, but believe in going beyond through collaboration, applied
innovation and new generation partnership models that put your interest above everything else. Right now 115,000 Ideapreneurs
are in a Relationship Beyond the Contract™ with 500 customers in 32 countries. How can I help you?
TM
WX-TC2480