You are on page 1of 24

System Architecture / Infrastructure Design

Moritz von Stietencron - BIBA D2.3 2 04.10.2013 286885 PU - Public To D2.3 System Architecture Infrastructure Design V0.4.Docx 24

Person responsible / Author: Deliverable No.: Work Package No.: Date: Project No.: Classification: Distribution: File name: Number of pages:

286885 BOMA

Status of Deliverable Action Submitted (author(s)) VU (WP Leader) Approved (QIM)


Revision History

By
Moritz von Stietencron Karl Hribernik

Date (dd.mm.yyyy)
04.10.2013

Date (dd.mm.yyyy) Version (version revision)


21.02.2013 26.02.2013 10.04.2013 23.04.2013 15.05.2013 20.05.2013 28.05.2013 12.07.2013 05.08.2013 26.08.2013 24.09.2013 27.09.2013 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.10 0.11 1.0

Author
Moritz von Stietencron Karl Hribernik Moritz von Stietencron Karl Hribernik Moritz von Stietencron Moritz von Stietencron Karl Hribernik Moritz von Stietencron Moritz von Stietencron Moritz von Stietencron Karl Hribernik Moritz von Stietencron Karl Hribernik Moritz von Stietencron Karl Hribernik Moritz von Stietencron Moritz von Stietencron Moritz von Stietencron

Comments
Draft TOC TOC revised; Draft Contents Contents updated TOC revised; Contents updated Contents updated Contents updated Contents updated Contents updated Contents updated Contents updated Contents updated Final Changes

Author(s) contact information

Name
Karl Hribernik Moritz von Stietencron

Organisation
BIBA BIBA

E-mail
hri@biba.uni-bremen.de sti@biba.uni-bremen.de

Tel
+49 421 218 50108 +49 421 218 50117

286885 BOMA

Table of Contents
1. 2. INTRODUCTION.......................................................................................................................................... 5 BOMA SYSTEM ARCHITECTURE .................................................................................................................. 5 2.1. 2.2. 3. INTERACTION CHANNELS AND LCM APPLICATION FRAMEWORK ............................................................................. 5 SEMANTIC MIDDLEWARE AND DATA SOURCES .................................................................................................... 8

BOMA INFRASTRUCTURE DESIGN .............................................................................................................11 3.1. 3.2. ELEMENTS OF THE BOMA INFRASTRUCTURE .................................................................................................... 11 REQUIREMENTS FULFILLED BY BOMA INFRASTRUCTURE ..................................................................................... 14

Figures
Figure 1: BOMA System Architecture Overview ......................................................................................... 5 Figure 2: BOMA System Architecture Interaction Channels & LCM Application Framework.................. 6 Figure 3: BOMA Mock Up Overview ........................................................................................................... 7 Figure 4: BOMA Mock Up Production Sheet List ........................................................................................ 8 Figure 5: BOMA Mock Up Activity Detail .................................................................................................... 8 Figure 6: BOMA Semantic Middleware and Data Sources .......................................................................... 9 Figure 7: Semantic Mediator....................................................................................................................... 9 Figure 8: BOMA UMG Structure................................................................................................................ 10 Figure 9: Exemplary UMG PC - "BeagleBone" ........................................................................................... 10 Figure 10: Exemplary BOMA Infrastructure .............................................................................................. 11

Tables
Table 1: List of BOMA Infrastructure Components ................................................................................... 11 Table 2: List of BOMA Technical Requirements ........................................................................................ 14

286885 BOMA

Abbreviations and Acronyms:


DSS LMS BOW LCM QLM NMEA Decision Support System Lifecycle Management Server BOat Web application Life Cycle Management Quantum Lifecycle Management National Marine Electronics Association

286885 BOMA 1. Introduction


The BOMA WP2 Boat Lifecycle Management Infrastructure design analyses the requirements put forward in the previous WPs and from these requirements designs the infrastructure and the services that will be proposed by the SMEs to their customers. Building on the structured analysis and merging of the different requirements from the SMEs and the definition of the pilot cases which both has been documented in deliverable "D2.1 Requirements catalogue and pilot definition", this deliverable documents the developed system architecture and the infrastructure design developed in BOMA. The deliverable is structured in two parts. The first will show the general system architecture, required for the BOMA solution, while the second will show the infrastructure utilised for this architecture in more detail.

2. BOMA System Architecture


Based on the requirements which were identified in task 2.1 and the pilot cases built upon these requirements in task 2.2 this deliverable documents the development and specification of the BOMA System Architecture as conducted in task 2.5. The BOMA system architecture consists of the following four layers: the Interaction Channels, the LCM Application Framework, the Semantic Middleware and the Data Sources.
Interaction Channels

LCM Application Framework

LCM Modules

Production Modules

Service Modules

CRM Modules

...

Boat Management Application Framework Semantic Middleware

Query Services

Configuration Services
Boat/data source database

Semantic Mediator
Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper

Back-end data sources

On-board data sources

3d party Internet data sources

Data Sources
Stakeholder Data Source 1 Stakeholder Stakeholder Data Data Source 2 Source n
Universal Marine Gateway 1 Universal Marine Gateway 2 Universal Marine Gateway n

Web Services

Cloud Services

Social Network Services

Telediagnostic Bus

On-board Sensor 1

On-board Sensor 2

On-board Sensor n

Figure 1: BOMA System Architecture Overview

Figure 1 gives an overview of the arrangement of the different layers within the BOMA system architecture while the following sections describe the layers in more detail.

2.1.

Interaction Channels and LCM Application Framework

The interaction channels are the means of access for all the different types of users to the Life Cycle Management (LCM) application framework.

286885 BOMA
Possible interaction channels are: On-board (Touch-)Screens of existing Systems Owners Smartphone or Tablet or Laptop-computer PDAs or Tablets used in the production and maintenance processes Computers used for production and maintenance planning and control Computers used in pre- and after-sales service Any web-enabled device
Interaction Channels

LCM Application Framework

LCM Modules

Production Modules

Service Modules

CRM Modules

...

Boat Management Application Framework

Figure 2: BOMA System Architecture Interaction Channels & LCM Application Framework Semantic Middleware
Query Services

Configuration Services

In BOMA the HOLONIX i-LiKe platform provides the application framework of the BOMA system Semantic Mediator architecture. It offers various modules for different business departments (e.g. Design, Production, Warehousing and Maintenance). These modules support the management of many data and information Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper throughout the item lifecycle, from the bill of material (as-designed, as-customized and as-produced), design documents and customer complaints to usage data, and maintenance history Back-end data sources 3d party Internet data sources On-board data sources In WP2 the i-LiKe platform was adopted towards the requirements of the leisure boating industry. To Data Sources improve the understanding within the project team and the usability of the solution first a software mockup has been built for studying, testing and display. The mock up also helped to verify the fulfilment ofCloud the Web Social Services Services Network requirements imposed by the SMEs involved in the project. Services Within i-LiKe a BOMA product item mock-up was created. Figure 3 shows an example of the overview page while Figure 4 and Figure 5 display exemplary detail pages.
Stakeholder Data Source 1 Stakeholder Stakeholder Data Data Source 2 Source n
Universal Marine Gateway 1 Universal Marine Gateway 2 Universal Marine Gateway n Telediagnostic Bus

Boat/da data

On-board Sensor 1

On-board Sensor 2

On-board Sensor n

286885 BOMA

Figure 3: BOMA Mock Up Overview

The product item in BOMA platform identifies a single physical product already manufactured and delivered to the market. It is the virtual representation of a real boat, its avatar. The BOMA solution is also susceptible for retrofitting into the existing boat population, having a faster impact and providing business benefits to all parties involved in the value chain. The product item comes from the product type already defined into the system. A product type identifies a particular model of the range. Before the product type is being sent into production it can be customised according to the users requirements, creating a customised bill of material. As soon, as the customised product type is completely defined it can be sent into production, turning into a new product item. The details of a selected item are shown in a pop-up page where are recorded all the data gathered within the whole lifecycle. All the information need by the shipyard or desired by boat-owner are accessible through this page. In particular: Production Sheet related to the Product Item A complete and updated list of all activities done on that item through the entire lifecycle (e.g. service and maintenance activities etc.) List of the sensors installed on board. Selecting one or more, users can visualize or download recorded data, stored in suitable formats List of manuals of equipment and components assembled on the boat. They support boat owner in self-maintenance and other simple activities Picture of the Product item for a faster identification All the changes occurred during production and parts and components replaced during the usage. The system, if required, can also keep the log of the boat owners, tracing also these additional details.

286885 BOMA

Figure 4: BOMA Mock Up Production Sheet List

Figure 5: BOMA Mock Up Activity Detail

2.2.

Semantic Middleware and Data Sources

The semantic middleware utilised in BOMA builds the infrastructure layer for integrating the various data sources. It integrates the various data sources and presents the data requested to the boat management application framework (i.e. the HOLONIX i-LiKe Platform).

LCM Application Framework

LCM Modules

Production Modules

Service Modules

CRM Modules

...

286885 BOMA
Boat Management Application Framework Semantic Middleware Query Services Configuration Services
Boat/data source database

Semantic Mediator
Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper Wrapper

Back-end data sources

On-board data sources

3d party Internet data sources

Data Sources
Stakeholder Data Source 1 Stakeholder Stakeholder Data Source n Data Source 2
Universal Marine Gateway 1 Universal Marine Gateway 2 Universal Marine Gateway n

Web Services

Cloud Services

Social Network Services

Figure 6: BOMA Semantic Middleware and Data Sources

At the heart of the semantic middleware stands the semantic mediator. The semantic mediator intelligently integrates heterogeneous systems, standards, schemata and data exchange formats (see Figure 7). It is capable of extracting knowledge regarding the data structures of the underlying data sources and subsequently transforming, decomposing and recomposing data requests according to that knowledge. The mediator relies on semantic descriptions of the data sources The application framework can access the semantic mediator through a query service, which the semantic middleware includes. Via a configuration service the semantic mediator can be initialised to read and interpret the varying data sources. Because of this dynamic configuration service the semantic mediator also provides a suitable integration mechanism for dynamic data sources like RFID and sensors.
Telediagnostic Bus On-board Sensor 1 On-board Sensor 2 On-board Sensor n

Semantic Mediator

Figure 7: Semantic Mediator

As the semantic mediator builds on a distributed system the processed data remains where it is generate. It integrates the data sources at a semantic, not only syntactic level. The automation of the integration is possible via (semi-) automatic ontology mapping. It allows semantic integration of sensor data with enterprise systems and thus the reasoning upon the automatically integrated data. The concept of the semantic mediator makes it necessary to use a semantic data model for product lifecycle management (i.e. the PROMISE Object Model) and a simple management of stakeholder data sources per boat. The preparation of QLM wrappers/query interface for UMG/iLike integration is also a prerequisite for the utilisation of the semantic mediator. The data sources within the BOMA scope that feed the semantic mediator through their respective wrappers are grouped into three sections: Back-end Data Sources, On-board Data Sources &

286885 BOMA
Service CRM 3rd Party Internet Data Sources. ... Modules Modules The Back-end data sources are the already existing systems of the different stakeholders (e.g. production planning systems, customer relationship management systems and warehousing systems). The on-board data sources represent the data coming from different systems on the boats. They are Boat Management Application Framework sourced and aggregated by the Universal Marine Gateway (UMG) which is also developed within BOMA and described in the following section. The 3rd party internet data sources are online servicesConfiguration which can provide for example weather forecasts Query Services Services and other 3rd party data which is of interest to the stakeholders.
Boat/data source database

Production Modules

Wrapper

The Universal Marine Gateway (UMG, see Figure 8) provides data collection, storage, and filtering and Semantic Mediator serves as a gateway to on-board sensors as well as to 3rd party, on-board data sources (e.g. the NMEA standard). It also is the communication gateway between the boat and the boat management application Wrapper Wrapper Wrapper i-LiKe Wrapper Wrapper Wrapper Wrapper framework (i.e. the HOLONIX Platform).
On-board data sources 3d party Internet data sources

nd data sources

takeholder Stakeholder Data ta Source 2 Source n

Universal Marine Gateway 1

Universal Marine Gateway 2

Universal Marine Gateway n

Web Services

Cloud Services

Social Network Services

Telediagnostic Bus

On-board Sensor 1

On-board Sensor 2

On-board Sensor n

Figure 8: BOMA UMG Structure

Figure 9: Exemplary UMG PC - "BeagleBone"

The key component of the UMG is a single-board computer. It is a full linux PC and offers wired as well as wireless connectivity. In addition to easy sensor integration it has a low cost factor and is easily extendable. The BeagleBone computer shown in Figure 9 is an excellent example of such an computer. The on-board sensors are required to measure the usage data (e.g. running conditions, component stress and integrity). Like the UMG PC they should preferably be low cost.

10

286885 BOMA 3. BOMA Infrastructure Design


The BOMA infrastructure comprises a number of elements, which enable it to host the architecture described earlier in this deliverable. These elements are described in the following subsection and are mapped to the technical requirements, they support.

Figure 10: Exemplary BOMA Infrastructure

Figure 10 gives an overview of a wide range of exemplary elements of the BOMA infrastructure and their connection with each other. As stated before the central connection point of the boat and the onshore parts of the BOMA architecture is the UMG. It connects the different pre-existing (e.g. NMEA 2000 hardware) and additional sensors and systems with the respective instances of the i-Like system.

3.1.

Elements of the BOMA Infrastructure

The BOMA infrastructure includes the following elements, in order to fulfil the technical requirements, which were identified in D2.1. This list describes the setup of the BOMA infrastructure including all components envisioned during the requirements analysis. Not all are necessarily needed to conduct the BOMA pilot cases and for other application scenarios further components might be necessary.
Table 1: List of BOMA Infrastructure Components

Universal Marine Gateway (UMG) fulfils req. #12,13,15,16,18-20,23,26,28-30,33,35,42-44,46,49,51,53,54,58,65,69,126,127, 135,138,139,143-146,148,149,152-154,166,170,177,178,183,185,186,208, 210,212,218 The UMG is one of the two centrepieces of the BOMA infrastructure. It combines all the data which is provided by the different sensors and interfaces (i.e. NMEA) on-board and aggregates it for further use in the i-LiKe system. It therefore is necessary for fulfilling a large number of technical requirements. Also it is used to process the sensor data generated in the production process.

C1

11

286885 BOMA
RFID PDA fulfils req. #2,13,21,22,28,31,32,34,49,51,60,63,147,148,150-153,181,185,194,196, 208,215,217 The RFID PDA is used for part identification in the context of production as well as in maintenance, storage and repair. The RFID PDA is the key interaction channel of the personnel to the BOMA LCM Management Application. RFID Tags fulfils req. #2,28,32,49,60,63,147,148,152,153,196,208,217 The RFID Tags identify the boat components they are attached to. Thus they can also identify the whole boat. NMEA Gateway (UMG compliant) fulfils req. #12,13,15,16,18-20,23,26,30,33,49,135,139,144,152,166,183,208,218 The NMEA Gateway connects the UMG to the NMEA bus on board of the boat. This is necessary in order to acquire and integrate the data, which is already pre-existing in the on-board systems, like engine management or gearbox control. Water Temperature Sensor fulfils req. #89,89.3,144,154,178 The water temperature sensor measures the surrounding waters temperature and delivers this data to the UMG, which can process and include it in the BOMA data set. Air Temperature Sensor fulfils req. #28,89,89.2,144,146,148,149,154,178 In the case of on-board deployment, the air temperature sensor measures the temperature of the surrounding air and delivers this data to the UMG, which can process and include it in the BOMA data set. The air temperature is also important for the production environment and therefore this sensor will also be applied to the production UMGs. Humidity Sensor fulfils req. #28,89,89.1,144,145,148,149,154,178 In the case of on-board deployment, the humidity temperature sensor measures the humidity of the surrounding air and delivers this data to the UMG, which can process and include it in the BOMA data set. The air humidity is also important for the production environment and therefore this sensor will also be applied to the production UMGs. Barometric Pressure Sensor fulfils req. #89,144 The barometric pressure sensor measures the barometric air pressure and delivers this data to the UMG, which can process and include it in the BOMA data set. Ambient Light Sensor fulfils req. #89,144 The ambient light sensor measures the ambient light and delivers this data to the UMG, which can process and include it in the BOMA data set. Accelerometer fulfils req. #6,12,43,44,154,178,186 The accelerometer measures the proper acceleration of the boat, which can for example be expressed in g-force units. It delivers this data to the UMG which processes it and C2

C3

C4

C5

C6

C7

C8

C9

C10

12

286885 BOMA
includes it in the BOMA data set. This data can be used to assess the performance and condition of the boat. Gyroscope fulfils req. #6,12,154,178 While the accelerometer measures the acceleration, the gyroscope determines and maintains the orientation of the boat. It also delivers this data to the UMG which processes it and includes it in the BOMA data set. This data can be used to assess the performance and condition of the boat. Strain Gauge fulfils req. #6,42-44,127,143,186 A strain gauge measures the strain in a material. It uses the physical property of electrical conductance and its dependence on the conductor's geometry and delivers information about changes in geometry of the considered area. This data is processed in the UMG and included in the BOMA data set, so it can be used for assessing the boat hulls condition and enable the assessing of its integrity. WiFi Module fulfils req. #28,46,53,54,58,69,212,221 The WiFi module will be attached to the UMG and enable wireless communication. This can be utilised in the case of on-board usage to establish connectivity with the boat owners smart phone, the maintenance crews systems or when the boat is in a marina with the local WiFi network in order to communicate with the backend system. In the production environment it serves to integrate the UMG into pre-existing or dedicated WiFi networks and the attached IT systems. WWAN Module fulfils req. #46,53,54,58,69,224 The WWAN module enables wireless communication based on standards like GSM, UMTS or LTE without a separate device as an access point to the internet. This is especially important for automated transmission of live performance data. Satellite Communication Module fulfils req. #46,53,54,58,69,202 The satellite communication module enables over-the-air communication from locations where no WiFi or cellular network is available. This secures the possibility to access live data from any operating location and gives the possibility of emergency message dispatch. XBee UMG Shield fulfils req. #89 The XBee shield will be attached to the UMG and empowers it to communicate over a stable, medium range, wireless connection with sensors which can be distributed across the boat without the need for wired connection. XBee Sensor-Nodes fulfils req. #89 The XBee sensor nodes, are the counterpart to the XBee UMG shield and allow the sensors attached to them to communicate with the UMG. GPS Receiver fulfils req. #32,135,138,166 C11

C12

C13

C14

C15

C16

C17

C18

13

286885 BOMA
The GPS receiver enables the UMG to determine the position of the boat via the global positioning system. In the future, this receiver may also use the data from the Galileo positioning system. i-LiKe Instance fulfils req. #16-23,26,28-34,42,49,51,53,54,58,128,132,147,148,150,154,166,169,170, 181,184,185,192-194,196,208 The i-LiKe installation is the second centrepiece of the BOMA solution. It constitutes the BOMA Life Cycle Management Application Framework described in Section 2.1. WiFi @ Marina & Workshop fulfils req. #28,46,53,54,58,69,212,216,221 The WiFi network to be established at the marina and at the workshops will be utilised to enable online connectivity of the UMG for data transfer and remote monitoring. Semantic Mediator fulfils req. #82,128,132,143,192,216 The semantic mediator is the third key part of the BOMA solution. It semantically integrates all data sources considered meaningful to the BOMA solution. It thus enables, that all the different data sources (analog and digital sensors, NMEA data etc.) can be combined and compared. Owners Smartphone fulfils req. #46,53,54,58,69,135,138,194,212,215,216,224 The Owners smart phone can be used as a gateway to connect the UMG to the internet when the boat is out of range of WiFi networks. It may also serve as a separate interaction channel for the boat owner. C19

C20

C21

C22

3.2.

Requirements fulfilled by BOMA Infrastructure

This section lists the requirements which are fulfilled by the utilisation of the BOMA infrastructure components described in section 3.1 and shows exactly which components are important for the respective requirement.
Table 2: List of BOMA Technical Requirements

Allocation of UID to Part Technical Requirement - Stakeholders: Fiart Mare, Marex Fulfilled by infrastructure components C2,3 The allocation of the unique identifier (UID) to the boats part is achieved via RFID tags and the RFID enabled PDAs. Assess Hull Integrity Technical Requirement - Stakeholders: Hydrolift, Karnic Fulfilled by infrastructure components C10,11,12 The integrity of the boats hull is assessed via the measurements of the accelerometer, gyroscope and the strain gauges. Collect Boat Performance Data Technical Requirement - Stakeholders: Marex Fulfilled by infrastructure components C1,4,10,11 Data about the performance of the boat is gathered via the NMEA gateway, the

#2

#6

#12

14

286885 BOMA
accelerometer and the gyroscope and is processed in the UMG. Collect Component Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,2,4 The collection of the component data is achieved by the NMEA gateway, the UMG and the PDAs. Collect Data on Boat when in Use Technical Requirement - Stakeholders: Fiart Mare, Hydrolift, Karnic, Marex, Marine Center Fulfilled by infrastructure components C1,4 For collecting data on the boat, while it is in use, the UMG and the NMEA gateway are used. Collect Drive Train Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4,19 The drive train data is collected by the UMG from the NMEA gateway and passed on to the i-Like instance. Collect EOL Data Technical Requirement - Stakeholders: Hydrolift Fulfilled by infrastructure components C19 The EOL data is collected by the i-Like instance. Collect Engine Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4,19 The engine data is collected from the NMEA gateway by the UMG and passed on to the iLike instance. Collect Fuel Filter Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4,19 The fuel filter data is collected from the NMEA gateway by the UMG and passed on to the iLike instance. Collect Gearbox Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4,19 The gearbox data is collected from the NMEA gateway by the UMG and passed on to the iLike instance. Collect Genset Data Technical Requirement - Stakeholders: marine Center Fulfilled by infrastructure components C1,19 Information about the genset is entered via the PDAs and processed in the i-Like instance. Collect Heads Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C2,19 #13

#15

#16

#17

#18

#19

#20

#21

#22

15

286885 BOMA
Information about the heads is entered via the PDAs and processed in the i-Like instance. Collect House Battery Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4,19 The house battery data is collected from the NMEA gateway by the UMG and passed on to the i-Like instance. Collect Outboard Engine Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4,19 The outboard engine data is collected from the NMEA gateway by the UMG and passed on to the i-Like instance. Collect Production Data Technical Requirement - Stakeholders: Karnic, Marex Fulfilled by infrastructure components C1,2,3,19 The data from the production processes is collected by the UMG from the temperature and humidity sensors as well as from the RFID PDAs and the RFID tags. The data is transferred via the WiFi shield on the UMG and the WiFi network at the production site to the i-Like instance. Collect Propeller Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,19 The propeller data is collected by the UMG and passed on to the i-Like instance. Collect Pump Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4,19 The pump data is collected from the NMEA gateway by the UMG and passed on to the i-Like instance. Collect Safety Gear Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C2,19 Information about the safety gear is entered via the PDAs and processed in the i-Like instance. Collect Shipment Information Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C2,3,18,19 Data about the shipment status is collected by the RFID PDAs, the tags and the GPS sensor. It is processed in the i-Like instance. Collect Starter Battery Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4,19 The starter battery data is collected from the NMEA gateway by the UMG and passed on to the i-Like instance. #23

#26

#28

#29

#30

#31

#32

#33

16

286885 BOMA
Collect Thru-Hull Fittings Data Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C2,19 Information about the thru-hull fittings is entered via the PDAs and processed in the i-Like instance. Continue Data Collection when not in Use Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1 For continuing the data collection while the boat is in use, the UMG is implemented. Define Stress Hotspots Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1,12,19 The stress hotspots are defined from the data read by the strain gauges and processed by UMG and i-Like instance. Determine Energy Effect Technical Requirement - Stakeholders: Hydrolift Fulfilled by infrastructure components C1,10,12 The energy effect is determined from the readings of the strain gauges and the accelerometer and processed by the UMG. Determine Force Effect Technical Requirement - Stakeholders: Hydrolift Fulfilled by infrastructure components C1,10,12 The force effect is determined from the readings of the strain gauges and the accelerometer and processed by the UMG. Enable Automated Transmission Technical Requirement - Stakeholders: Hydrolift, Fiart Mare, Karnic, Marex Fulfilled by infrastructure components C1,13,14,15,20,22 To enable automated transmission, the UMG and WiFi, WWAN and Satellite Communication Modules can be used. Also the data can be transferred via the WiFi network or the owners smart phone. Enable Boat Components Traceability Technical Requirement - Stakeholders: Fiart Mare, Marex Fulfilled by infrastructure components C1,2,3,4,19 The traceability of the boat components is enabled by the UMG, the RFID PDAs, the RFID tags, the NMEA gateway and the i-Like instance. Enable Data Logging & Saving Technical Requirement - Stakeholders: Hydrolift, Fiart Mare, Karnic, Marex, Marine Center Fulfilled by infrastructure components C1,2,19 Data logging and saving will be accomplished by the UMG, the RFID PDAs and the i-Like instance. Enable Event Data Transmission Technical Requirement - Stakeholders: Hydrolift, Marex #34

#35

#42

#43

#44

#46

#49

#51

#53

17

286885 BOMA
Fulfilled by infrastructure components C1,13,14,15,19,20,22 Event data transmission is enabled by the UMG, the WiFi, WWAN and Satellite communication modules, WiFi networks and the owners smart phone, as well as the i-Like instance. Enable Manual Transmission Technical Requirement - Stakeholders: Fiart Mare, Karnic, Marex Fulfilled by infrastructure components C1,13,14,15,19,20,22 Manual data transmission is enabled by the UMG, the WiFi, WWAN and Satellite communication modules, WiFi networks and the owners smart phone, as well as the i-Like instance. Enable Operating Data Transmission Technical Requirement - Stakeholders: Hydrolift, Fiart Mare, Karnic, Marex Fulfilled by infrastructure components C1,13,14,15,19,20,22 Operating data transmission is enabled by the UMG, the WiFi, WWAN and Satellite communication modules, WiFi networks and the owners smart phone, as well as the i-Like instance. Enable Part Identification Technical Requirement - Stakeholders: Fiart Mare, Karnic, Marex, Marine Canter Fulfilled by infrastructure components C2,3 Part identification is enabled by the RFID PDAs and the RFID tags. Enable UID Readability Technical Requirement - Stakeholders: Fiart Mare, Marex Fulfilled by infrastructure components C2,3 UID readability is enabled by the RFID PDAs and the RFID tags. Enable Wired Transmission Technical Requirement - Stakeholders: Fiart Mare, Karnic, Marex Fulfilled by infrastructure components C1 For wired data transmission the UMG is necessary. Enable Wireless Transmission Technical Requirement - Stakeholders: Fiart Mare, Karnic, Marex Fulfilled by infrastructure components C1,13,14,15,20,22 Wireless data transmission is enabled by the UMG, the WiFi, WWAN and Satellite communication modules, WiFi networks and the owners smart phone. Establish Data Interface Syntax Technical Requirement - Stakeholders: Marex Fulfilled by infrastructure components C21 The semantic mediator establishes the data interface syntax. Implement Environmental Sensors Technical Requirement - Stakeholders: Hydrolift, Karnic, Marex Fulfilled by infrastructure components C5-9,16,17 As environmental sensors the following are implemented: Water temperature, air temperature and humidity. For wireless integration the XBee sensor-nodes and the XBee UMG shield are required. #54

#58

#60

#63

#65

#69

#82

#89

18

286885 BOMA

Monitor Air Humidity Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1,7 To monitor the air humidity the UMG and the humidity sensor are required. Monitor Air Temperature Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1,6 To monitor the air temperature the UMG and the air temperature sensor are required. Monitor Water Temperature Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1,5 To monitor the water temperature the UMG and the water temperature sensor are required. Install On-Board Computer Technical Requirement - Stakeholders: Fiart Mare, Hydrolift, Karnic, Marex, Marine Canter Fulfilled by infrastructure components C1 The UMG is the on-board computer. Install Stress Sensors Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1,12 To install stress sensors, the UMG and the strain gauges are required. Integrate with Existing Enterprise Systems Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C19,21 To interoperate with existing enterprise systems, the i-Like instance and the semantic mediator are required. Interoperate with SAP Technical Requirement - Stakeholders: Fiart Mare Fulfilled by infrastructure components C19,21 To interoperate with SAP, the i-Like instance and the semantic mediator are required. Log GPS Position Technical Requirement - Stakeholders: Hydrolift Fulfilled by infrastructure components C1,4,18,22 To log the GPS position the UMG, the NMEA gateway, a GPS receiver and the owners smart phone can be used. Measure "Down-Time" Technical Requirement - Stakeholders: Hydrolift Fulfilled by infrastructure components C1,18,22 To measure the down-time, the UMG, a GPS receiver and the owners smart phone can be used.

#89.1

#89.2

#89.3

#126

#127

#128

#132

#135

#138

19

286885 BOMA
Measure Engine Wear Technical Requirement - Stakeholders: Marine Center Fulfilled by infrastructure components C1,4 To measure the engine wear the UMG and the NMEA gateway can be utilised. Measure Waves Technical Requirement - Stakeholders: Hydrolift Fulfilled by infrastructure components C1,12,21 To measure the wave intensity the data from strain gauges and accelerometer are gathered via the UMG and combined with online marine weather data and wave information provided by the semantic mediator. Measure Weather Technical Requirement - Stakeholders: Hydrolift Fulfilled by infrastructure components C1,4-9 To measure the parameters of the current weather the UMG gathers data from sensors measuring water temperature, air temperature, barometric pressure, humidity and ambient light. Some data might be gathered via the on-board NMEA bus. Monitor Air Humidity Technical Requirement - Stakeholders: Karnic, Marex Fulfilled by infrastructure components C1,7 The air humidity is measured via a humidity sensor and processed by the UMG. Monitor Air Temperature Technical Requirement - Stakeholders: Karnic, Marex Fulfilled by infrastructure components C1,6 The air temperature is measured via a humidity sensor and processed by the UMG. Monitor Components Technical Requirement - Stakeholders: Karnic, Marex, Marine Canter Fulfilled by infrastructure components C2,3,19 The components are monitored throughout the production using RFID tags and the RFID PDA. The data is processed in the i-Like instance. Monitor Composite Parts Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1-3,6,7,19 The composite parts are tracked thro throughout the production using RFID tags and the RFID PDA, while the environmental conditions of the composite part production is monitored via air temperature and humidity sensors, which are managed by a UMG. The data is processed in the i-Like instance. Display Hull Mixing Ratio Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1,6,7 The mixing ratio of resin and catalyst for the composite parts is calculated by the UMG and based on the data from the humidity and temperature sensors. Monitor Man Hours per Stage Technical Requirement - Stakeholders: Karnic #139

#143

#144

#145

#146

#147

#148

#149

#150

20

286885 BOMA
Fulfilled by infrastructure components C2,19 The man hours used per stage are monitored by the PDAs and the data is processed in the iLike instance. Monitor Material Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C2 The material used can be monitored using the PDAs. Monitor Optional Equipment Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1-4 Optionally installed equipment can be monitored either via RFID tags and the PDA or via the UMG and the NMEA gateway if the parts are connected to it. Monitor Parts & Accessories Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1-4 The parts and accessories can be monitored either via RFID tags and the PDA or via the UMG and the NMEA gateway if the items are connected to it. Monitor Working Conditions Technical Requirement - Stakeholders: Karnic, Marex Fulfilled by infrastructure components C1,5-11,19 The working conditions of the boat are monitored by i-Like based on the data gathered by the UMG and provided by the different sensors. Provide Availability Information Technical Requirement - Stakeholders: Fiart Mare Fulfilled by infrastructure components C1,4,18,19 The UMG can process the data from the GPS receiver (in some cases via the NMEA gateway) and forward it to the i-Like instance where the availability information can be provided. Provide Boat Service Schedule Technical Requirement - Stakeholders: Marex Fulfilled by infrastructure components C19 The boats service schedule can be computed by the i-Like instance. Provide Dynamic Database Technical Requirement - Stakeholders: Fiart Mare Fulfilled by infrastructure components C1,19 The main dynamic database is provided by the i-Like instance. Also the UMG has a limited size database to buffer and store some more recent data. Provide On-Board Data Processing Technical Requirement - Stakeholders: Fiart Mare, Hydrolift, Karnic, Marex, Marine Canter Fulfilled by infrastructure components C1 The on board data processing power is provided by the UMG. #151

#152

#153

#154

#166

#169

#170

#177

21

286885 BOMA
Provide Operating Conditions & Performance Data Technical Requirement - Stakeholders: Fiart Mare, Hydrolift, Karnic, Marex, Marine Canter Fulfilled by infrastructure components C1,5-11 Data on the operating conditions and performance is gathered from the various sensors by the UMG and provided for further use. Provide Production GUI Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C2,19 The graphical user interface of the production system is provided by the i-Like instance and displayed on the PDA. Provide Sensor-Processor Interface Technical Requirement - Stakeholders: Fiart Mare, Hydrolift, Karnic, Marex, Marine Canter Fulfilled by infrastructure components C1,4 The sensor processor interface is provided by the UMG and the NMEA gateway. Provide Service Data Technical Requirement - Stakeholders: Marex Fulfilled by infrastructure components C19 The service data is provided by the i-Like instance. Provide Service personnel / Operator Interface Technical Requirement - Stakeholders: Fiart Mare, Karnic, Marex Fulfilled by infrastructure components C1,2,19 The interface for the operator and service personnel can be provided by the i-Like instance and displayed via the PDAs or via the UMG. Provide Stress and Impact Information Technical Requirement - Stakeholders: Hydrolift, Karnic, Marine Canter Fulfilled by infrastructure components C1,10,12 The information on stress and impacts can be measured by strain gauges and accelerometer and is processed and provided for further use by the UMG. Provide XML Input & Output Technical Requirement - Stakeholders: Fiart Mare Fulfilled by infrastructure components C19,21 XML input and output can be provided by the i-Like instance and the semantic mediator. Provide different Data Views Technical Requirement - Stakeholders: Karnic, Marex, Marine Canter Fulfilled by infrastructure components C19 Different data views will be provided by the i-Like instance. Provide different GUI Technical Requirement - Stakeholders: Karnic, Marex, Marine Canter Fulfilled by infrastructure components C2,19,22 Different GUI will be provided by the i-Like instance and can be displayed on the PDAs and the owners smartphone. #178

#181

#183

#184

#185

#186

#192

#193

#194

22

286885 BOMA

Recognise Change of Ownership Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C2,3,19 A change of ownership can be recognised using the RFID PDAs and RFID tags or the i-Like system. Satellite Communication Technical Requirement - Stakeholders: Fiart Mare, Marex Fulfilled by infrastructure components C15 Satellite communication is provided by the satellite communication module. Track Component Changes Technical Requirement - Stakeholders: Marex Fulfilled by infrastructure components C1-4,19 Component changes can be identified and tracked via the RFID PDAs and tags, the i-Like instance or the UMG and NMEA gateway. USB Interface Technical Requirement - Stakeholders: Marex Fulfilled by infrastructure components C1 The UMG can provide a USB interface. Use Customers Smartphone as Data Access Point Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1,13,22 To use the owners smartphone as a data access point, the smartphone it self, a local wifi connection and the UMG are necessary. Use Mobile Device Displays Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C2,22 As mobile device displays the PDAs and the owners smartphone can be used. Use Texts & EMail for Communication Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C20-22 To use texts and email for communication the owners smartphone, the semantic mediator and wifi connection at the marina can be used. Use existing Part Identification Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C2,3 For the use of existing part identification mechanisms the RFID PDAs and tags can be utilized. Use onboard Displays Technical Requirement - Stakeholders: Karnic Fulfilled by infrastructure components C1,4 To use existing onboard displays the NMEA gateway and the UMG can be used.

#196

#202

#208

#210

#212

#215

#216

#217

#218

23

286885 BOMA
Wireless LAN Technical Requirement - Stakeholders: Fiart Mare, Karnic, Marex Fulfilled by infrastructure components C13,20 The WiFi module and the WiFi network at marinas and the workshops will be used to establish WLAN connectivity. Wireless WAN Technical Requirement - Stakeholders: Fiart Mare, Karnic, Marex Fulfilled by infrastructure components C14,22 The WWAN module and owners smartphone can be used to establish WWAN connectivity. #221

#224

24