Available online at www.sciencedirect.

com

Available ScienceDirect
online atonline
Available www.sciencedirect.com
at www.sciencedirect.com

ScienceDirect
Procedia CIRP 00 (2018) 000–000
ScienceDirect www.elsevier.com/locate/procedia

Procedia CIRP 00 (2017)

Procedia 000–000
CIRP 72 (2018) 880–885
www.elsevier.com/locate/procedia

51st CIRP Conference on Manufacturing Systems

Architecture28th
andCIRP
development of an
Design Conference, Industrial
May 2018, Nantes,Internet
France of Things
framework for realizing services in Industrial Product Service Systems
A new methodology to analyze the functional and physical architecture of
existingKosmas
products for ana,assembly
Alexopoulos oriented
Spyros Koukas a
product
, Nikoletta familyMourtzis
Bolia, Dimitris identification
a*

a
Laboratory for Manufacturing Systems and Automation, Department of Mechanical Engineering and Aeronautics, University of Patras, 26500, Rio Patras,
Paul Stief *, Jean-Yves Dantan, Alain Etienne, Ali Siadat
Greece
* Corresponding author. Tel.: +30-261-0 99-7262; fax: +30-261-0 99-7744. E-mail address: mourtzis@lms.mech.upatras.gr
École Nationale Supérieure d’Arts et Métiers, Arts et Métiers ParisTech, LCFC EA 4495, 4 Rue Augustin Fresnel, Metz 57078, France

* Corresponding author. Tel.: +33 3 87 37 54 30; E-mail address: paul.stief@ensam.eu

Abstract

This paper presents the architecture and the development details of an Industrial Internet of Things (IIoT) solution that supports the lifecycle of
IPSSs (Industrial Product-Service Systems). The proposed framework supports the definition, commissioning and operation phases of services
Abstract
in IPSS. The framework utilizes an IIoT system architecture that enables services’ deployment both at the edge tier and in the platform tier and
Inuses the enterprise
today’s business tier for implementing
environment, the trendspecific
towardsapplications thatvariety
more product provideand
interfaces to end-users.
customization A service
is unbroken. fortolaser
Due this machine data analysis
development, the needand
of
aggregation
agile is designed and
and reconfigurable implemented
production systemson emerged
top of thetoproposed framework
cope with in order to
various products demonstrate
and the capabilities
product families. To design of it.
and optimize production
systems as well as to choose the optimal product matches, product analysis methods are needed. Indeed, most of the known methods aim to
© 2018aThe
analyze Authors.
product or onePublished by Elsevier
product family on theB.V.
physical level. Different product families, however, may differ largely in terms of the number and
Peer-review under responsibility of the scientific
nature of components. This fact impedes an efficient committee of the 51st
comparison and CIRP
choiceConference on Manufacturing
of appropriate product familySystems.
combinations for the production
system. A new methodology is proposed to analyze existing products in view of their functional and physical architecture. The aim is to cluster
Keywords: Industrial Internet of Things (IIoT); Industrial Product-Service Systems (IPSS); Data Analytics
these products in new assembly oriented product families for the optimization of existing assembly lines and the creation of future reconfigurable
assembly systems. Based on Datum Flow Chain, the physical structure of the products is analyzed. Functional subassemblies are identified, and
a functional analysis is performed. Moreover, a hybrid functional and physical architecture graph (HyFPAG) is the output which depicts the
1. Introduction The purpose of this paper is to present the architecture and
similarity between product families by providing design support to both, production system planners and product designers. An illustrative
the development details of such an IIoT solution that supports
example of a nail-clipper is used to explain the proposed methodology. An industrial case study on two product families of steering columns of
The manufacturing
thyssenkrupp Presta France environment has
is then carried outradically
to give achanged over evaluation
first industrial the lifecycle of IPSSs.
of the proposed The proposed framework supports the
approach.
the last decades, following the technological
© 2017 The Authors. Published by Elsevier B.V. revolution in definition, commissioning and operation phases of services in
information and communication technology. Manufacturing IPSS. The
Peer-review under responsibility of the scientific committee of the 28th CIRP Design Conference 2018.framework utilizes a three-tier IIoT system
companies’ long-term goal is to remain competitive and ensure architecture that enables services’ deployment both at the edge
their sustainability
Keywords: [1].method;
Assembly; Design The Family
shift of profit margins
identification from tier as well as in the platform tier and uses the enterprise tier
products to services, has transformed traditional production for implementing specific applications that provide interfaces
equipment supplier industries to providers of Industrial to end-users. In order to demonstrate the capabilities of the
Product-Service Systems (IPSS). IPSS is a new business model proposed framework a pilot case from the machine building
1.forIntroduction
consistent delivery of industrial products and services. In of the product
industry range and
is presented. In characteristics manufactured
particular, an IPSS and/ora
that features
many cases, the value creation offered by a service of an IPSS, assembled in this system. In this context, the main
service for laser machine data analysis and aggregation, has challenge in
Due to
requires the fast
a software development
system that needs toinanalyzethe data
domaincoming of modelling and analysis is now not only
been designed and implemented on top of the proposed to cope with single
communication and an ongoing trend of digitization
from different data sources within the industrial product, such and products,
framework. a limited product range or existing product families,
digitalization,
as a numericalmanufacturing
controller of enterprises
a laser-cuttingare machine
facing important
or from but The
also remaining
to be able to of analyze
the paperand to follows:
is as comparethe products
secondtochapter
define
challenges in today’s market environments:
Internet of Things (IoT) devices embedded or attached a continuing
to the new product families. It can be observed that classical
comprises a state of the art on the main aspects of this work. existing
tendency
industrialtowards
product.reduction
In manyofcases,
product development
a diverse number times and
of such product families are
The architecture andregrouped in function
the prototype of the of clients
IIoT or features.
framework are
shortened product lifecycles. In addition, there
industrial products are deployed in a wide range of customeris an increasing However, assembly oriented product families are hardly
presented in section three. Section four presents the application to find.
demand of customization,
environments. The deployment,beingmanagement,
at the same time in a global
and maintenance of On
the the product
proposed family
IIoT level, products
framework differ
for realizing mainlyininIPSS
services two
competition with competitors all over the world. This
of such services create the need for Industrial Internet of Things trend, main characteristics: (i) the number of components
using pilot examples. Finally, this paper concludes with the and (ii) the
which is inducing the development from macro
(IIoT) solutions that take into account the technical details, as to micro type of components (e.g. mechanical, electrical, electronical).
results of this work and also the intentions of the authors for
markets,
well as, results in diminished
the different lot sizes
stakes holders that due to augmenting
are involved in the Classical
future work.methodologies considering mainly single products
product varieties
IPSS business model. (high-volume to low-volume production) [1]. or solitary, already existing product families analyze the
To cope with this augmenting variety as well as to be able to product structure on a physical level (components level) which
identify possible optimization potentials in the existing causes difficulties regarding an efficient definition and
2212-8271 ©system,
production 2018 The it
Authors. Publishedtobyhave
is important Elsevier B.V. knowledge
a precise comparison of different product families. Addressing this
Peer-review under responsibility of the scientific committee of the 51st CIRP Conference on Manufacturing Systems.

2212-8271©©2017
2212-8271 2018The
The Authors.
Authors. Published
Published by Elsevier
by Elsevier B.V. B.V.
Peer-review
Peer-review under
under responsibility
responsibility of scientific
of the the scientific committee
committee of the of theCIRP
28th 51stDesign
CIRP Conference
Conference2018.
on Manufacturing Systems.
10.1016/j.procir.2018.03.152
 Kosmas Alexopoulos et al. / Procedia CIRP 72 (2018) 880–885
2 Author name / Procedia CIRP 00 (2018) 000–000
2. State of The Art
IIoT is defined as a network of entities that are connected.
In this network, devices are located, identified and operated
upon. IIoT describes the IoT technology as it is used in several
industries such as manufacturing. The role of IoT in factories
is relying on connecting smart machines, devices, and people
through a network, analyze data extracted from machines
through sensors, and finally make decisions based on data and
store data for later use [2].
IIoT appears back in the 00s with the RFID tags for
facilitating routing, inventorying and loss prevention [3]. The
higher estimated value of IIoT applications concerns factories
IIoT, incorporates Physical resources and Cyberworld, leading
to the creation of Cyber-Physical Systems (CPS), which enable
among others, Real-Time production control, operation
optimization and predictive maintenance [4]. Enablers of IIoT
are the Affordable Hardware, Affordable computing power,
Standardization, architectures, and the Tactile internet (5G).
On the other hand, IIoT barriers are security issues,
technological competence, nonscalable systems, mixed
criticality in industrial systems and latency [4, 5].
Challenges for the realization of IIoT are the Interoperability
due to Heterogeneous data and Variation in data interpretation,
the Scalability (Sustainable existing networks and integrate
new networks) and Security issues (Data protection and
Confidentiality) [6]. In order to address challenges related to
the implementation of IIoT, IIoT reference architectures have
been created.
There are several reference architectures, among others are
the Reference Architecture Model Industrie 4.0 (RAMI 4.0),
the Industrial Internet Reference Architecture (IIRA) and the
Internet of Things Architecture (IoT-A). RAMI 4.0 has 6 layers
entitled Business, Functional, Information, Communication,
Integration and Asset [7]. IIRA has 4 layers entitled Business,
Usage, Functional and Implementation [8]. An IoT system that
utilizes data collected from sensors, located at a shop-floor in
order to increase the visibility of shop floor processes by
providing the right information to the right people, at the right
time has been implemented based on a layered architecture,
consisting of the Shop-Floor Sensor, Metrology, Proxy, Data
Aggregation, Context Aware Services and Application layer
[9].
IoT Adoption in Manufacturing leads to the production of
big volumes of data with veracity, commonly referred as Big
Data. The adoption of IoT in manufacturing, enables the
transition from traditional manufacturing systems into modern
digitalized ones, utilizing data analytics in order to produce
more value leading to the generation of new economic
opportunities through industries re-shaping [10]. Decision
making is ubiquitous in the contemporary organizational
processes. Big Data analytics are used in order to improve
decision making in different manufacturing stages. The data
fusion and the interpretation of the data lead both to the
improvement of the product design, as well as to the product
use, since value feedback is collected through sensor-based
services, supported by IoT following collaboration schemes
[11].
881
Following the aforementioned, as a result of their constant
urge to retain sustainability, more and more companies have
shifted to the IPSS business model, in an effort to gain
competitive advantages. IPSS business models introduce a
paradigm shift towards selling functionality, instead of selling
products. Simultaneously, such models include the dynamic
adoption of changing customer demand and provider’s abilities
[12]. In the proposed framework, sensor-based IPSS are
examined.
The scalability and high availability without compromising
performance requirements of the IoT solutions, lead to the need
of databases which could support the management of massive
amounts of data. NoSQL databases are increasingly used in big
data and real-time web applications [13]. Following a Column
data model, the proposed framework utilizes Cassandra
NoSQL database, a leading distributed database [14].
As the importance of IoT increases a few approaches have
emerged that offer IoT related functionalities. Google provides
the Google IoT framework [15] which is a set of fully managed
and integrated services that allow developers to easily and
securely connect, manage, and ingest IoT data from globally
dispersed devices at a large scale, process and analyze/visualize
that data in real time, and implement operational changes and
take actions as needed. In addition, General Electric provides a
framework named PREDIX [16], which aims in the
development, deployment, and operation of industrial apps at
the edge and in the cloud.
The proposed IIoT framework shares common traits with
some IoT related solutions in terms of the architectural layout,
however the current state of the art frameworks are mostly
generic solutions, that can be used as elements to develop IIoT
applications in general and are not specialized or oriented to the
concept of Product Services. On the contrary the proposed
approach focuses on the needs of IPSS and incorporates a
strong semantic connection between the participating entities,
specifically targeted to the development of IPSS systems.
3. Architecture and Prototype of IIoT framework
The proposed services framework utilizes the three-tier
industrial IoT system architecture that enables services’
operation both at the edge and in the platform tier and uses the
enterprise tier for implementing specific applications that
provide interfaces to end-users. This is a well-established
system architecture pattern for implementing coherent
industrial applications. The proposed IIoT framework is
comprised of edge sensors with which data are aggregated.
Accordingly, through IoT gateways, those data are shared,
filtered and transmitted from the edge to the cloud. Part of the
proposed framework is to manage, analyze and turn valuable
data into analytics and finally, data processing will lead to
useful insights, shared information through the intent and also
the provision of services.
882 Author
Kosmasname / Procedia
Alexopoulos et CIRP
al. / Procedia
Fig. 1. Services Framework reference Architecture
In Fig. 1 the architecture of the proposed IIoT framework is
presented. This framework allows on one hand the definition
and management of Service Types and Instances. In addition,
it is focalized to provide stream and batch analytics support, in
big data enabled technologies, and also to be able to support
Edge and Cloud Computing. Software components enable the
cost-effective and efficient service provision. In this sense, the
architecture shown in Fig. 1 is the reference that shows how
different implementations can be developed.
A fully functional prototype of the IIoT framework together
with an IPSS system solution has been developed. The
developed IIoT framework is comprised of four different
applications that implement the complete prototype solution.
1. The core IIoT cloud framework application
2. The Edge Software Application
3. The PSS cloud application of the IPSS
4. The IPSS web-based application
Each one of the four different applications is described in
detail accordingly.
3.1. Core IIoT Cloud Framework
The Core IIoT is a scalable, big data-oriented application
that offers a set of core functionalities for storing and retrieving
timeseries, accessing the ontology models, as well as,
performing analytic and timeseries processing operations.
Moreover, the core IIoT framework provides some reusable
building blocks for UI development such as timeseries chart
visualization, map visualization, and graph visualizations. As
shown in Fig. 2 the Core IIoT framework provides
functionalities that are used by all components of an IPSS
System.
The Core IoT framework uses a detailed ontology that
models a PSS System. The ontology, models in detail the
building blocks of a Product Service System, which in the
context of this prototype are the Products, the Services and the
Sensors. The modelling and implementation follow an open
00 (2018)
000–000
CIRP 72 (2018) 880–885 3
world modelling perspective, allowing the definition of new
properties and structure of every item. The modeling also takes
into account the lifecycle of these items, by differentiating
between types and instances. This approach is similar to the one
proposed by RAMI 4.0. [7].
The Sensor model of the framework can be used to model
arbitrary sensor systems but also in a more abstract way to
model input coming from products or found in other systems.
This approach is based on the concept that “anything that can
be read—from files to product-specific data—can and should
be considered sensor input” [17] The IIoT framework includes
a Knowledge Repository that is used to store the models of all
the IPSS System, as well as workflow related information that
covers different aspects of the IPSS such as its design,
customization, orders, offers, as well as, information about
suppliers and service providers.
While sensors are essential sources of information, the
services modeling can be used to model IIoT enabled
functionalities offered by an IPSS. The framework allows the
services to receive the data coming from the sensors modelled
as timeseries and transported in timeseries packages.
Each sensor and service instance is connected to a different
set of timeseries through a set of ontology properties, that
define information about the usage of each timeseries, such as
if it is an input or an output. The modeling allows the definition
of different type of timeseries that are connected with
taxonomies of sensor, services, sensor stimuli and other
information. This modeling approach enables the selection of
analytic queries, such as identifying all the timeseries that
capture vibration information that is used in a PSS together
with a specific type of products.
The developed IIoT framework uses different technologies
to persist the model of the IPSS systems, and the timeseries
information as each covers a different need.
 4 Author
Kosmasname / Procedia
Alexopoulos CIRP
et al.
/ Procedia
Fig. 2. IoT Implementation
The persistence of the Knowledge model about the PSS
systems is implemented using the Apache Jena Framework
TDB that provides native high-performance triple store that
supports the full range of Jena APIs [18]. As the Jena API is an
adopted by different triple data storage systems it is possible to
use the IIoT framework with different implementations such as
Oracle Spatial and Graph [19] or Open Link Virtuoso [20]. This
implementation is ACID compliant and is well suited for the
CRUD operations as well as detailed SPARQL 1.1 queries.
However, in a big data environment with many different IPSS,
a BASE compliant, big-data enabled has been used. In
particular, the Apache Cassandra database has been used. The
modeling of the timeseries storage in Cassandra utilizes some
redundancy in order to achieve better performance in
frequently used queries. However, one of the main principles
that Cassandra was built on is that disk space is a very cheap
resource so minimizing disk seeks at the cost of higher space
consumption is a good tradeoff [21].
The access to the Graph DB and Timeseries database is only
granted to the Core IIoT Framework, which is a scalable Java
JEE 7.0 application that provides REST interfaces which
support the lifecycle of PSS systems. Other applications can
only access information indirectly, by using a wide range of
micro-services offered by the Core IIoT Cloud framework.
3.2. The Edge Software Application
The Edge Software Application is responsible to capture
information from the sensors, process them in the edge layer,
as suggested by the ubiquitous computing approach and also
utilize the services offered by both the Core IIoT framework
and the PSS Cloud Application. This software application is
developed in Java and is comprised of two submodules. An
IPSS specific part that has been developed for the prototype
IPSS, and a reusable prototype module that offers useful
functionality suitable for the development of an IPSS.
The IPSS specific module is responsible to capture the
information coming from the sensors by using the related
sensors SDK and also capture the information from the Laser
Machine by accessing the machine’s Mongo DB, that stores
machine related data such status events, parts processed and
more. The sensors and the MongoDB are sources of
00 (2018)
000–000
CIRP 72 (2018) 880–885 883
information that have been modeled as Sensor entities, and the
stream of data that is produced by them as timeseries. This layer
on top of getting the readings of the 3D vibration sensors is
responsible to make the appropriate calls to the framework
edge module.
The framework edge module is a reusable component that
offers some edge analytics services such as the calculation of
the FFT of the vibration sensors and comparisons of the
observed values with the given thresholds. The edge module
also offers other functionalities that are performed by
communicating with the cloud IoT framework application,
such as the packaging and transmitting of timeseries, the
sending of notifications and alarms, the retrieval of historical
data, the batch processing and the filtering of historical data.
3.3. The IPSS Cloud Application
The online IPSS application is implemented as a Java EE
application that utilizes the IoT Core Application framework in
order to perform batch analytics on the information that is
available in the timeseries, and ontology databases that are
controlled by the IoT Framework. The analysis implemented
includes functions such as clustering of different alarms per
product, per customer type, as well as, analysis of the lifecycle
of a PSS from a sales perspective, identifying the number of
online Views, Offers, Requests, Orders and Completed orders.
3.4. The PSS Web UI Application
The web-based application offers a user interface that an
IPSS user may access from his browser and has access to the
historical information saved in the ontology and timeseries
databases of the IoT Cloud Framework application. The web
based UI, adapts the content exposed to different users
depending on their role. Users that own a specific IPSS, can
view information about their IPSS and the historical data that
has been pushed in the IIoT core application by IPSS software
running on machines they own. On the other hand,
manufacturers of machines may view aggregated information
and analysis over the whole spectrum of their machines models
coming from different customers. The web based UI is also
able to configure the different analyses that take place in the
884 Kosmas Alexopoulos et al. / Procedia CIRP 72 (2018) 880–885
Author name / Procedia CIRP 00 (2018) 000–000
IPSS Cloud Application, as well as, control the different
thresholds for warning and alarms that are applicable to the
Edge PSS Application.
The modelling follows an open world approach, allowing
these applications to run in two distinct environments. In
particular, a division concerning the environment of these
applications can be made in terms of the applications running
on the cloud servers and the applications running on the IPSS
hardware, or edge environment.
The proposed framework has an ontology based knowledge
model specifically developed to model product services. Each
Product Service is uniquely identified and its services and
sensors are semantically linked with the streams of data coming
from the IoT devices. The values from the IoT devices are
converted to a single format that is understood internally by the
proposed IIoT framework and can be converted back to its
original form if needed.
4. Pilot Case
Many of the currently used manufacturing equipment and
tools, especially the ones that do not incorporate the use of
digital technology, do not have the capability to observe, record
or store information about how the equipment has been used or
any potential faults that may have occurred. However, some
modern high-tech manufacturing equipment, are capable of
capturing information regarding the usage of the machine. The
information captured by the machines, includes aims to identify
the functionalities of the machine that is in use, potential alarm
events, internal failures or even abnormal external operations
that could potentially cause an error. Although modern
production equipment is capable of capturing this information
and can save them to some internal data storage, one has to
scrutinize over the actual information captured manually, in
order to analyze them and most of the time only the most recent
events are available as the embedded software needs to delete
older records as the available memory space is limited. This
leads to the loss of older, history records that may contain
information that is essential to correctly diagnose a problem.
This information is isolated, and not readily available when
needed. In a typical scenario, an Engineer will access this
information and check for particular events when trying to
address an issue in the machine. The Engineer will try to
analyze the logs manually, in an error-prone, time-consuming
process. Following that, a Machine data analysis service will
provide the final level of analytics and reporting for several
roles (Engineer, Sales, and Customer) on top of the IIoT
framework. This service gathers information from Machine and
Sensors, analyzes data, identifies trends in one and multiple
machines and provides reports, and warnings comparing
information to thresholds.
The IPSS under investigation is a laser cutting machine with
vibration sensors installed. Involved actors are IPSS Provider
and IPSS Customer. The following figure presents the Machine
Data Analysis and Report Service Concept showing also the
different functionalities offered in different users. The Machine
Data Analysis and Report Service offer functionalities that
benefit both Customers and the manufacturer in different ways.
5
Considering that most of the customers are SMEs which lack of
experts and accesses to advance analytics tools, through the
proposed framework they can be connected in such a way with
their IPSS Providers and receive detailed reports about the
usage of their machines.
Fig. 3. Machine Data Analysis and Report Service Concept
The service can capture machine and sensor data, analyze
them and create reports for the customer. The reported analytics
are relevant only to the machines that the customer owns. These
machines are connected to the Company’s Machine Data
Analysis and Report Service. The customer may also choose to
allow the manufacturer to use and analyze the data captured by
the service, in order to receive notifications, recommendations,
and suggestions from the manufacturer regarding his machine.
Furthermore, the customer can set specific alarm and warn
thresholds over which the service will notify the customer. The
Manufacturer sees detailed info for every connected machine
that the customer has provided the required permission.
Analytics provide distilled info on various categories such as
machine Type, processes, setup, parameters, and working
hours. This information can be used by the laser machines
manufacturing company to recommend solutions to the
customer or plan the design of new machines and features that
best fit customers’ needs. The laser machines company
Customers’ Office and Engineers, have access to cumulative
views of machine information (e.g. how customers use
machines, faults encountered, parameters etc.) that provide
valuable knowledge such as how customers use machines, what
faults have been encountered and what are the machine
parameters used.
Summarizing, the situation before the use of the proposed
IIoT framework finds Laser Machines to produce logs, which
are isolated, not readily available, and thus company’s
Customers Office and Engineering need to analyze manually
different logs. Through the utilization of the proposed
framework, Machine logs information is gathered centrally,
analyzed and reported consistently. Also, the Laser provider
will offer customized applications to the already occupied or
new machines, passing in such a way to Digitization,
Customization and Servitization. Closing, Fig. 4 presents the
Customers and Manufacturer perspectives on this service and
also the results of the proposed framework can be summarized
on cost and time reduction and customization.
 6 Author
Kosmasname / Procedia
Alexopoulos CIRP
et al.
/ Procedia
Fig. 4. Machine Data Analysis and Reporting: Customers and Manufacturer perspectives and results
5. Conclusions and Future Work
The present work provides the architecture and development
of an Industrial Internet of Things framework for realizing
services in Industrial Product Service Systems. An integrated
prototype has been developed that successfully demonstrates
data collection, analysis and reporting. The integrated prototype
provides different functionality oriented towards different user
roles and their particular needs. From the end-user perspective,
the main benefits from the use of this framework are that the
information collected at the different machines is
systematically collected, aggregated and analyzed by a big-data
enabled, streamlined process that respects the privacy and
information of the users. The output of this analysis is reported
to the users in a graphical, user friendly way using a set of
different graphs and figures.
The next steps would be to deploy the framework in a set of
different environments and allow the end users to utilize and
test it for an adequate period of time. Afterwards, the
functionalities offered by the service will be refined and further
improved, based on the feedback received from the end users
through their use and testing of the providing services.
Consolidating the results with the feedback provided by end
users, the related software components and analytics algorithms
are going to be improved.
Acknowledgements
This work has been partially supported by the H2020 EC
funded project “An Integrated Collaborative Platform for
Managing the Product-Service Engineering Lifecycle –
ICP4Life” (GA No: 636862).
References
[1] Chryssolouris G (2006) Manufacturing Systems: Theory and Practice.
second ed.Springer-Verlag, New York.
00 (2018)
000–000
CIRP 72 (2018) 880–885 885
[2] Tedeschi S, Mehnen J, Tapoglou N, Roy R. Secure IoT Devices for the
Maintenance of Machine Tools. Procedia CIRP. 2017;59(TESConf
2016):150–5.
[3] Suresh P, Daniel JV, Parthasarathy V, Aswathy RH. A state of the art
review on the Internet of Things (IoT) history, technology and fields of
deployment. 2014 Int Conf Sci Eng Manag Res. 2014;1–8.
[4] Manyika J, Chui M, Bisson P, Woetzel J, Dobbs R, Bughin J, et al. The
Internet of Things: Mapping the value beyond the hype. McKinsey Glob
Inst. 2015;(June):144.
[5] Breivold HP, Sandstroem K. Internet of Things for Industrial Automation
-- Challenges and Technical Solutions. 2015 IEEE Int Conf Data Sci Data
Intensive Syst . 2015;532–9.
[6] Sadeghi A-R, Wachsmann C, Waidner M. Security and privacy challenges
in industrial internet of things. Proc 52nd Annu Des Autom Conf - DAC
’15 . 2015;1–6.
[7] Adolphs P. Rami 4.0. 2015
[8] Lin S-W, Miller B., Durand J., Bleakley G., Chigani A., Martin R., et al.
Reference Architecture. Ind Internet Consort . 2017;1.80:1–7.
[9] Alexopoulos K, Makris S, Xanthakis V, Sipsas K, Chryssolouris G. A
concept for context-aware computing in manufacturing: the white goods
case. Int J Comput Integr Manuf. 2016;29(8):839–49.
[10] Mourtzis D, Vlachou E, Milas N. Industrial Big Data as a Result of IoT
Adoption in Manufacturing. Procedia CIRP . 2016;55:290–5.
[11] Matsas M, Pintzos G, Kapnia A, Mourtzis D. An Integrated Collaborative
Platform for managing Product-service Across their Life Cycle. Procedia
CIRP . 2017;59(TESConf 2016):220–6.
[12] Meier H, Roy R, Seliger G. Industrial Product-Service systems-IPS2.
CIRP Ann - Manuf Technol. 2010;59(2):607–27.
[13] Samuel OW. Comparative Analysis of Relational ( Oracle ) and Non-
Relational ( Cassandra ) Databases for Business Intelligence. 2017
[14] Chebotko A, Kashlev A, Lu S. A Big Data Modeling Methodology for
Apache Cassandra. 2015 IEEE Int Congr Big Data . 2015;238–45.
[15] Google, Google Cloud Platform, https://cloud.google.com/solutions/iot/
[16] LG,PREDIX Site, https://www.predix.io/
[17] Biron J, Follett J. Foundational Elements of an IoT Solution . Vol. 64,
Physiological Research. 2016. 69 p.
[18] Apache Foundation, Apache Jenna Framework, https://jena.apache.org/
[19] Oracle Spatial And Graph, Oracle,
http://www.oracle.com/technetwork/database/options/spatialandgraph/do
wnloads/index-089452.html
[20] Open Link Virtuoso, Jenna providers,
http://vos.openlinksw.com/owiki/wiki/VOS/VirtJenaProvider
[21] Datastax, Advanced Time Series with Cassandra,
https://www.datastax.com/dev/blog/advanced-time-series-with-cassandra