Architectural Design Principles For Industrial Internet of Things

302 Pages·2017·9.99 MB·English

DOCTORA L T H E S IS
Department of Computer Science, Electrical and Space Engineering H Architectural Design Principles
EISLAB as
a
n
D For Industrial Internet of Things
e
r
ISSN 1402-1544 h
a
ISBN 978-91-7790-128-0 (print) m
y
ISBN 978-91-7790-129-7 (pdf)

A
r
Luleå University of Technology 2018 c
h
i
t
e
c
t
u
r
a
l
D
e
s
i
g
n

P
r
i
n
c
i
p
le
s

F
o
r

I
n
d
u
s
t
r
i
a
l
I
n
t Hasan Derhamy
e
r
n
e
t

o
f
T
h
i
n
g
s

Industrial Electronics
Image on the cover:
Silver Fern (Cyathea dealbata, or from Māori kaponga or ponga ), Auckland,
New Zealand, 2009.
The Fern is an example of a naturally occuring fractal. Nature is an inspiring
model for architecting complex technological solutions. Through fractals
nature efficiently architects infinitely complex systems.
Architectural Design Principles
For Industrial Internet of Things
Hasan Derhamy
Department of Computer Science, Electrical and Space Engineering
Lule˚a University of Technology
Lule˚a, Sweden
Supervisors:
Jens Eliasson and Jerker Delsing
Printed by Luleå University of Technology, Graphic Production 2018
ISSN 1402-1544
ISBN 978-91-7790-128-0 (print)
ISBN 978-91-7790-129-7 (pdf)
Luleå 2018
www.ltu.se
To Nana and Grandad and my family
iii
iv
Abstract
Associetyhasprogressedthroughperiodsofevolutionandrevolution,technologyhas
played a key role as an enabler. In the same manner that mechanical machines of the
1800’sdrovetheindustrialrevolution,nowdigitalizedmachinesaredrivinganotherone.
With this recognition of a fourth industrial revolution, the Industry 4.0 initiative was
founded. One of the drivers of Industry 4.0 is the Industrial Internet of Things (IIoT).
TheIIoTisaconsequenceofwidelypresentcomputingubiquityandinterconnected-
ness. Software has become a crucial tool of almost all industries from bakeries and arts
to manufacturing facilities and banking. Programming is now a required competence
and used by a variety of professions. It is not only about algorithm development, it has
becomemoreaboutengineeringandintegratingexistingdesignsandtools. Thisimpacts
the way software is architected and drives a large body of research in the area.
Software solutions are becoming more distributed, not only over multiple processes,
but over heterogeneous hardware and business domains. Computing platforms could be
mobileorgeographicallyseparatedoverlargedistances,exposingthesolutionstonetwork
disturbances, performance degradation and security vulnerabilities.
Hence, IIoT introduces complexity on a scale previously unseen in the software in-
dustry. Softwarearchitecturemustaccommodatetheseheterogeneousdomainsandcom-
petencies and handle the increasing levels of complexity.
This thesis proposes an architectural style for designing IIoT software architectures.
The popular Service Oriented Architecture (SOA) style is not sufficient to define a com-
pletearchitectureforIIoTapplications. SOAfundamentalprinciplesaredefinedasloose
coupling, lookup and late binding. The proposed architecture style extends these SOA
principles with autonomy, specialization, data at its source and first person perspective.
It preserves the benefits of SOA that models functionalities as reusable services with
standardized interfaces. Thus, the proposed style helps to capture the heterogeneity of
IIoT (e.g. systems, capabilities, domains, competencies etc.), while handling challenges
imposed by it. The style also captures resource constraints of IIoT platforms; distri-
bution of application logic across IIoT; dependence between services within IIoT; and
presentation of the solution in various stakeholder perspectives.
The IIoT generates large amounts of data that is subsequently stored, analysed,
archived and eventually fed back into the product life cycle. Centralization of data has
well known challenges. This thesis proposes a method of information extraction based
on the principle of data at its source. Such data preserves implicit context, reducing the
burden of semantic data within the system. Desired information is expressed through
dynamic(runtime)queries. Usingthequeries,apathiscreatedtoretrievetherequested
v
data. It alleviates the need for data to be stored in intermediary nodes; data remains at
thesource. Thus,IIoTapplicationsextractinformationandpresentittorequestingsys-
temswithoutredundantsourcerelatedcontext. Thishelpswithissuesofdataownership,
access control and stale data.
Another IIoT challenge tackled in this work is decentralization of Manufacturing
ExecutionSystem(MES).Itismotivatedbyaneedtomitigatetheimpactofvulnerable
sharednetworksonthefactoryfloor;andbybusinessrequirementstoreducedependence
on local factory infrastructure. This thesis explores a solution where functions of MES
are distributed to the workstations that enables them to operate autonomously. Such
autonomous workstations utilize the proposed Intelligent Product, Workflow Manager
and Workflow Executor systems. Thus, MES can be decentralized to edge nodes as
envisioned by Industry 4.0.
vi
Contents
Part I 1
Chapter 1 – Introduction 3
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Problem formulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Research Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Thesis scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5 Thesis structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2 – Software, Systems and the IIoT 13
2.1 Internet of Things. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Industry 4.0 and RAMI 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Software Architecture Practice . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4 Fundamental Architectural Styles . . . . . . . . . . . . . . . . . . . . . . 19
2.5 Advanced Architectural Styles . . . . . . . . . . . . . . . . . . . . . . . . 21
2.6 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.7 Systems of Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.8 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 3 – Architecting IIoT Software 29
3.1 Protocol Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2 Information Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3 Towards Decentralized MES . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.4 Challenges of Software Engineering in IIoT . . . . . . . . . . . . . . . . . 35
3.5 Principles for Software Architecture design in IIoT . . . . . . . . . . . . 37
3.6 The Principled Decomposition . . . . . . . . . . . . . . . . . . . . . . . . 39
3.7 The Architectural Style. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 4 – Contribution 53
4.1 Summary of Appended Publications. . . . . . . . . . . . . . . . . . . . . 53
Chapter 5 – Conclusion and Outlook 57
5.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.2 Future work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
References 63
vii
Part II 71
PaperA–A Survey of Commercial Frameworks for the Internet of
Things 73
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2 What is an Internet of Things Framework . . . . . . . . . . . . . . . . . 76
3 Frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4 Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
5 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Paper B – Translation Error Handling for Multi-Protocol SOA
Systems 95
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
2 Background and Related Work. . . . . . . . . . . . . . . . . . . . . . . . 99
3 Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4 Proposed Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5 Implementation and Results . . . . . . . . . . . . . . . . . . . . . . . . . 107
6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
7 Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8 Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
PaperC–IoT Interoperability - On-demand and low latency Trans-
parent Multi-protocol Translator 115
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
2 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
3 Arrowhead Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
4 Proposed SOA-based translator . . . . . . . . . . . . . . . . . . . . . . . 123
5 Translator Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6 Transparency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
8 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
9 Future work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Paper D – Orchestration of Arrowhead services using IEC 61499:
Distributed Automation Case Study 141
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
2 IEC 61499 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
3 Arrowhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4 Case study: Conveyor Loop with Distributed Control . . . . . . . . . . . 147
5 Application of Arrowhead architecture . . . . . . . . . . . . . . . . . . . 147
6 Application integration in IEC 61499 . . . . . . . . . . . . . . . . . . . . 150
7 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
viii