iShare@Sea standard Share and Exchange Maritime Information“ · PDF file„Share and...
-
Upload
truongquynh -
Category
Documents
-
view
221 -
download
1
Transcript of iShare@Sea standard Share and Exchange Maritime Information“ · PDF file„Share and...
iShare@Sea standard
„Share and Exchange Maritime Information“
Part 1: Functional Documentation
Date February 10, 2014
Version 1.0 FINAL
Number of
pages
19 (incl. appendices)
Authors Michiel Stornebrink ([email protected])
Silja Eckartz ([email protected])
Elena Lazovik ([email protected])
License This work is licensed under a Creative Commons Attribution-
NoDerivs 3.0 Unported License.
Visit http://creativecommons.org/licenses/by-nd/3.0/deed.en for
more information.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 2 / 19
Contents
1 Introduction .............................................................................................................................. 3 1.1 Background................................................................................................................................ 3 1.2 Reading guide ........................................................................................................................... 3 1.3 Acknowledgements ................................................................................................................... 4 1.4 Version history ........................................................................................................................... 4
2 Business overview .................................................................................................................. 5 2.1 Purpose of iShare@Sea standard ............................................................................................. 5 2.2 Sensors, equipment and IT systems ......................................................................................... 6
3 Domain model .......................................................................................................................... 8 3.1 Energy generation cluster .......................................................................................................... 8 3.2 Propulsion cluster .................................................................................................................... 10 3.3 Supporting systems ................................................................................................................. 11 3.4 Explanation of equipment types .............................................................................................. 12
4 Condition monitoring information ....................................................................................... 14 4.1 Measurements ......................................................................................................................... 14 4.2 Events and states .................................................................................................................... 16 4.3 Counters and timers ................................................................................................................ 18 4.4 Context information ................................................................................................................. 19
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 3 / 19
1 Introduction
1.1 Background
Europe relies heavily on maritime transport. Up to 90% of all trade in Europe is transported by
ships, and the Netherlands is home to the largest port in Europe. The maritime sector,
however, is under pressure, mainly due to competition from Asian countries. This is equally
valid for the offshore industry. The generally shared opinion that constant innovation in
shipbuilding and offshore construction is essential for survival, because competition on cost-
price is not sustainable. For the sector this requires the acceptance and use of new innovative
concepts, which further decrease the operating costs. One of the possibilities is clever
techniques that support ships and offshore units from the shore as much as possible. You can
think of applications as: Condition Based Maintenance (where maintenance is not planned
based on elapsed time but on the technical condition); Crew Support (support crew in its
tasks); Logistics Support; Payload monitoring; Electronic document flows, etc.
Various maritime system suppliers, including suppliers of hydraulic systems, diesel engines,
office networks, HVAC systems, etc., want to support their customers better by providing
maintenance support for the systems after installation on board. This includes diagnosing and
optimizing the systems, preventing problems and reducing the probability of a failure to
increase availability. This enables them to compete because the life-cycle costs of their
system are lower.
The maritime suppliers who wish to develop such services are dependent on data from
different systems on board. There is a need to collect data from the own system
supplemented with data from other systems, securely store it, make it easily available to
stakeholders on the ship / offshore unit and ashore. These stakeholders can analyse the data
and draw conclusions on their own system or start actions that need to be taken crew or by
other stakeholders. However, if each party implements information exchange protocols based
on their own network philosophy or "proprietary" architecture and information models,
complexity and cost increases on board and blocks the optimal data fusion for (advice)
information.
This standard provides a shared information model and information exchange protocol for
exchanging maritime information to monitor condition of equipment, ships, offshore units,
payload and other valuable assets.
1.2 Reading guide
The iShare@Sea standard consists of two parts:
Part 1: Functional documentation. This part includes an introduction, domain model and
description of the maintenance information that is currently in scope.
Part 2: Technical interface specification. This part specifies how iShare information can be
exchanged between IT systems.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 4 / 19
1.3 Acknowledgements
This first version of the iShare@Sea standard is the results of a Joint Innovation Project by
industry partners, knowledge partners and the Dutch Top sector Water for Knowledge &
Innovation (TKI). The partners wish to jointly undertake research and development activities
in the field of information exchange in the field of the maritime industry.
We would like to thank all partners that participated in this JIP. These are:
Bachmann Electronic Benelux
Damen Shipyards Group
Dutch Institute World Class Maintenance
Dutch Ministry of Defense
Imtech Marine B.V.
Oliveira International B.V.
SBM Schiedam B.V.
SPM Instrument B.V.
Stichting Centrum Maritieme Technologie & Innovatie
TNO
1.4 Version history
Version Date Release notes
v1.0 DRAFT 2013-12-13 Draft version for partners
v1.0 FINAL 2014-02-10 Release of first version of the iShare@Sea standard
- Review comments of partners processed
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 5 / 19
2 Business overview
2.1 Purpose of iShare@Sea standard
The iShare standard aims at value creation by standardizing and enabling a broad range of
maritime information exchange, including monitoring of entire ships and payload. The
standard is an open information standard. This first version will be limited to the exchange of
condition based maintenance information of a set of equipment related to propulsion and
energy generation on board of ships and offshore units. The intention is clearly to broaden the
scope as soon as a first version of the standard is successfully implemented.
2.1.1 Open information standard
The scope is to enable data exchange between any system with any other necessary system
(on the ship or on land) in a uniform and secure way. When developing a standard to improve
interoperability between systems a distinction can be made between different levels of
interoperability. This standard focuses on the semantic and syntactic levels of interoperability.
Technical interoperability (e.g. connectivity) is out of scope.
Figure 1: Levels of Conceptual Interoperability1
The iShare@Sea standard is an open standard, which means that its use will be free of
charge and stakeholders are able to contribute to further development of the standard.
2.1.2 Condition based maintenance
The focus of the current version of the information standard is on condition based
maintenance (CBM) information. CBM is maintenance that is performed based on analysis of
the condition of the equipment instead of preventive, time based or corrective maintenance.
To be able to analyse the condition of the equipment, sensor and performance data need to
be exchanged between the equipment and other systems on board or between the equipment
1 http://en.wikipedia.org/wiki/Conceptual_interoperability
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 6 / 19
and onshore facilities. Chapter 4 provides the details about which kind of maintenance
information can be exchanged using the iShare standard.
Control information such as switching equipment on/off, increasing speed or opening/closing
valves are explicitly out of scope.
2.1.3 Equipment that is covered
Maritime equipment that is covered by this version of the standard includes equipment related
to power generation and propulsion systems. The information model is built of reusable
equipment components (pumps, valves, etc) and measurement elements (temperatures,
pressures, etc) that can be exchanged. This allows to quickly extend the scope of the
information model.
2.2 Sensors, equipment and IT systems
Several actors (both systems as human actors) play a role in the exchange of information.
While the equipment and payload that needs to be monitored is situated on board of a ship or
an offshore unit, the systems that receive and process this information can be found both on
board as well as ashore. The end-users of the information are also both on board (e.g. crew)
as well as ashore (e.g. suppliers, service providers, owners).
Sensors provide data about the condition of certain equipment, payload or any other valuable
asset. This measurement information is provided via many different (proprietary) protocols,
depending on the type of sensor, type of measurement, etc. At some point this data needs to
be translated to the iShare information model in order to further exchange this information
with other systems based on the iShare standard. This functionality of translation, but also
other functionalities like storing, enriching, securing and distributing the information, are
considered iShareBox functionalities. The iShareBox functionality can be integrated in the
equipment itself (e.g. an engine) or externalized by means of integrating IT systems on board.
This standard does not prescribe how to implement the iShare functionality. Finally the
information can be requested and used by other systems on board (e.g. platform
management system) for crew support and ashore (e.g. third party service applications) for
remote assistance.
Stakeholders that are involved in one way or the other with the iShare standard can be
clustered in the following three groups:
Primary stakeholders that make use of the iShare information, like owners, crew and
service providers.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 7 / 19
Secondary stakeholders that need to implement the iShare functionality, like system
integrators, equipment vendors, ship builders, service providers, etc..
Other stakeholders that are not primarily using the information but have certain interest
regarding the information or specification of the systems, like regulatory bodies, (local)
authorities, clients (e.g. oil companies), etc.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 8 / 19
3 Domain model
This chapter will specify the equipment types that are defined in this standard. We will provide
a breakdown structure and explanation of the covered equipment types.
Note that the described equipment types do not cover all equipment on board of ships or
offshore units. The list is expected to grow and externalized as a codelist. Prerequisite for this
is a standardization body that adopts and maintains this documentation.
3.1 Energy generation cluster
This cluster contains the equipment that is needed for generation of electric energy. This
includes drivers that provide mechanical power, equipment to transmit this power and a
generator to transform this into electric energy.
3.1.1 Drivers
Gas Turbine
Turbine Shaft Bearing
Seal Filter
Combustion Chamber Nozzle
Supporting Systems
Reciprocating engine
Turbo Charger
Cooler
Shaft Seal
Bearing Filter
Valve Auxiliary Gear
Shaft Seal
Bearing Filter
Pump Driver
Bearing Cylinder
Valve
Crankcase
Supporting Systems
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 9 / 19
3.1.2 Transmission
3.1.3 Electric energy generation
Electric Motor
Stator Windings
Rotor Windings
Shaft Seal
Bearing Cooler
Gearbox
Gear
Shaft Seal
Bearing Filter
Pump Driver
Bearing Valve
Crankcase
Supporting Systems
Rotating Generator
Stator Winding
Rotor Winding
Shaft Seal
Bearing Cooler
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 10 / 19
3.2 Propulsion cluster
This cluster contains the equipment that is involved in propulsion of a ship. This includes
drivers that provide mechanical power, equipment to transmit this power and a propeller to
transfer rotational power into thrust.
3.2.1 Drivers
The drivers as provided in section 3.2.1 are also applicable for the propulsion cluster. These
are: a gas turbine, a reciprocating engine and an electric motor.
3.2.2 Transmission
3.2.3 Propulsion.
Gearbox
Gear
Shaft Seal
Bearing Filter
Pump Driver
Bearing Valve
Crankcase
Supporting Systems
Brake
Clutch
Shaft Seal
Bearing
Propellor
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 11 / 19
3.3 Supporting systems
Supporting systems can be part of the specification of many other equipment elements. The
supporting systems cluster is mentioned for example as part of the gas turbine, the
reciprocating engine, and the gearbox. In this version of the standard support systems for
cooling, exhaust, hydraulics and lubrication are specified.
3.3.1 Cooling support system
3.3.2 Exhaust support system
3.3.3 Hydraulic support system
3.3.4 Lubrication support system
Cooling support system
Pump Driver
Bearing Valve
Filter
Cooler
Fan Driver
Exhaust support system Fan Driver
Hydraulic support system
Pump Driver
Bearing Valve
Filter
Cooler
Accumulator
Lubrication support system
Pump Driver
Bearing Valve
Filter
Cooler
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 12 / 19
3.4 Explanation of equipment types
Equipment type Explanation
Ship A vessel that floats on water.
Offshore unit
A structure floating on water that is not able to manoeuvre by
itself.
Drivers
Combustion chamber
A combustion chamber is the part of an engine in which fuel is
burned.
Crankcase
The housing for the crankshaft of an engine, where oil from hot
engine parts is collected and cooled before returning to the
engine by a pump.
Cylinder
The chamber in a reciprocating internal-combustion engine,
pump, or compressor within which the piston moves.
Electric motor
“Electric motor” as a general element not a specific
electromotor of a specific engine.
Gas turbine
A heat engine that converts the energy of fuel into work by
using compressed, hot gas as the working medium and that
usually delivers its mechanical output power either as torque
through a rotating shaft. Also known as combustion turbine.
Hydraulic motor
A motor activated by water or other liquid under pressure. A
hydraulic motor is a mechanical actuator that converts hydraulic
pressure and flow into torque and angular displacement
(rotation).
Nozzle
Projecting tube which discharges forcibly in a jet. Nozzle is a
device designed to control the direction or characteristics of a
fluid flow (especially to increase velocity) as it exits (or enters)
an enclosed chamber or pipe.
Reciprocating engine
A reciprocating engine, also often known as a piston engine, is
a heat engine that uses one or more reciprocating pistons to
convert pressure into a rotating motion (e.g. diesel engine).
Turbine or compressor
Any of various machines in which the kinetic energy of a
moving fluid, such as water, steam, or gas, is converted to
rotary motion. Any reciprocating or rotating device that
compresses a gas.
Turbo charger
A centrifugal compressor which boosts the intake pressure of
an internal-combustion engine, driven by an exhaust-gas
turbine fitted to the engine's exhaust manifold.
Transmission
Auxiliary gear A transmission of speed or force in service of a main function.
Brake
A device for on demand slowing or stopping motion by
absorbing kinetic energy mostly by creating friction.
Clutch
A device for on demand engage/disengagement of a motor and
a gearbox.
Gear
A toothed machine part, such as a wheel or cylinder, that
meshes with another toothed part to transmit motion or to
change speed or direction.
Gearbox A protective casing for a system of gears.
Shaft
A long, generally cylindrical bar that rotates and transmits
power, as the drive shaft of an engine.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 13 / 19
Equipment type Explanation
Energy generation
Electric generator A device that converts mechanical energy to electrical energy.
Rotor
The rotating part of a motor, dynamo, turbine, or other working
machine.
Stator
The stationary part of a motor, dynamo, turbine, or other
working machine.
Winding
One or more turns of wire forming a continuous coil through
which an electric current can pass, as used in transformers and
generators.
Propulsion
Propeller Revolving end of shaft with blades to push ship forward.
Auxiliaries
Accumulator
An apparatus for storing energy, power or media i.e. gas,
liquids etc.
Bearing
A device that supports, guides, and reduces friction of motion
between fixed and moving parts of a machine.
Cooler A container or apparatus for cooling, such as a heat exchanger.
Fan
A device, usually consisting of a rotating paddle wheel or an
airscrew, with or without a casing, for producing currents in
order to circulate, exhaust, or deliver large volumes of air or
gas.
Filter
A porous article or material for separating suspended
particulate matter from liquids by passing the liquid through the
pores in the filter and sieving out the solids.
Pump
A machine that draws a fluid into itself through an entrance port
and forces the fluid out through an exhaust port.
Seal
A device that joins two systems or elements in such a way as to
prevent leakage.
Valve
Any device that shuts off, starts, regulates, or controls the flow
of a fluid.
Supporting systems
Main elements of support systems are located outside the supported equipment. Support
systems can support multiple pieces of equipment at the same time. Measurements
regarding the medium (e.g. gas or fluid) can be measured at the support system or at the
supported equipment itself.
Cooling support system
A system to remove waste heat through the intake of cool air
or liquid.
Exhaust support system
A system for the disposal of exhaust. This can be exhaust
gasses, waste water or other fluids.
Hydraulic support system A system that delivers pressurized hydraulic fluid.
Lubrication support system A system for lubrication purposes.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 14 / 19
4 Condition monitoring information
This chapter provides the functional description of the condition monitoring information that
can be exchanged using the iShare standard. We distinguish between three types of data
information: measurements (sensor data), events and counters/ timers. Part 2 of the standard
provides all details regarding the data requests.
4.1 Measurements
A measurement describes the condition of a piece of equipment by a sensor value at a
certain point in time. The measurement can describe a variety of conditions measured by
specific types of sensors, e.g.: speed, temperature, pressure, vibration, etc. When
measurements are requested, also metadata about these measurements need to be provided
in order to interpreted the values. Metadata include the type of measurement, the identifier of
the sensor and the unit of measure.
Example of the result of a request for temperature measurements regarding a specific engine:
Sensor identifier : [ID of sensor]
Resource identifier : [ID of engine]
Measurement type : Temperature
Unit of measure : Degree Celsius
Measurements :
2013-12-01T16:33:01.000 60.5
2013-12-01T16:33:02.000 60.4
etc.
4.1.1 Measurement types and units of measure
This standard prescribes a set of units of measure (UOM) that must be used for the types of
measurement (e.g. meters per second to specify speed). This simplifies the implementation of
the standard, because not all different units of measure that are possible need to be
implemented (like km/s, miles per hour, etc). The standard only prescribes the UOMs that
need to be used when exchanging information, this does not restrict the way in which these
measurements are represented within systems internally or are presented to a human actor.
For example, an application receives information about the speed of a vessel, according to
the iShare standard in meters per second, but represents this data in knots to a user.
Measurement type Type code Units of measure UOM Code2
01. Space and Time
Acceleration A001 Metere per second squared MSK
Angle (plane) A002 Radian C81
Angular velocity A003 Radian per second 2A
Area A004 Square metre MTK
Length A005 Metre MTR
Time A006 Second SEC
Velocity A007 Metre per second MTS
Volume A008 Cubic metre MTQ
Periodic and related phenomena
2 Source: UNECE Recommendation no. 20 rev 8 (2012) – Codes for Units of Measure Used in International
Trade
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 15 / 19
Measurement type Type code Units of measure UOM Code2
Frequency B001 Hertz HTZ
Mechanics
Compressibility C001 Reciprocal pascal (1/Pa) C96
Density C002 Kilogram per cubic metre KMQ
Force C003 Newton NEW
Mass C004 Kilogram KGM
Mass flow rate C005 Kilogram per second KGS
Power C006 Watt WTT
Pressure C007 Pascal PAL
Torque C008 Newton metre NU
Viscosity C009 Pascal second C65
Volume flow rate C010 Cubic metre per second MQS
Work C011 Joule JOU
Heat
Temperature D001 Kelvin
Degree Celsius
KEL
CEL
Electricity
Current E001 Ampere AMP
Charge E002 Coulomb COU
Power E003 Watt WTT
Apparent power E004 Volt – ampere D46
Voltage E005 Volt VLT
Physical chemistry and molecular physics
Amount of substance F001 Mole C34
Mass concentration F002 Kilogram per cubic metre KMQ
Mass concentration F003 Mole per cubic metre C36
Molar mass F004 Kilogram per mole D74
Molar volume F005 Cubic metre per mole A40
Mole fraction F006 One (mol/mol) C62
Molecular concentration F007 Reciprocal cubic metre (1/m3) C86
Maritime specific
Pitch G001 Radian C81
P/D ratio G002 One (Pitch in meters/Propeller
diameter in meters)
C62
Valve position G003 Percentage
100 = open, 0 = closed
%
Liquid level G004 Percentage Metre
%
MTR
Vibration specific
Zero to peak (0-p) H001 Metre
Metre per second
Metre per second squared
MTR
MTS
MSK
Peak to peak H002 Metre
Metre per second
Metre per second squared
MTR
MTS
MSK
Root Mean Square
(RMS)
H003 Metre
Metre per second
Metre per second squared
MTR
MTS
MSK
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 16 / 19
4.2 Events and states
Simple event
Events keep track of things that happened to the sensor of an equipment or the equipment
itself. They can be of many different types, e.g.: installation, maintenance, starts, stops,
failures, alarm generated, changes in configurations (e.g. alarm setpoints), overrides, etc.
Each event contains information about the type, a time stamp, a short description (if needed)
and a value (if needed). Example:
Example of the result of a request for an event regarding a specific engine:
Event identifier : [ID of event]
Resource identifier : [ID of engine]
Event type : Alarm generated
Description :
Timestamp : 2013-12-01T16:33:01.000
Value :
Complex state referencing to events
State commonly refers to the present condition of a system or entity. The state of the
equipment provides the present condition of all system components. If there is a change in
the state of the system, this can be caused by and/or cause many events. Therefore, state
can be represented by the set of events relevant to the change to that system state.
Example of the result of a request for the (current) state regarding a specific engine:
Resource identifier : [ID of engine]
State type : Stopped
Timestamp : 2013-12-01T16:33:01.000
Value : (
Event identifier : 350,
Event identifier : 351,
Event identifier : 345)
This example represents the situation where the state of the engine changed to ‘Stopped’ and
provides a list of all relevant events identifiers. Every event type, description, timestamp and
value can be requested by its identifier, using the scheme presented before.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 17 / 19
Complex event referencing to states
Sometimes an event is not a simple event (e.g. sensor breaking), but a complex event
relevant to different components of the equipment. In that case, an event can consist of the
current states of all relevant equipment components.
Example of the result of a request for an event and states regarding a specific engine:
Event identifier : [ID of event]
Resource identifier : [ID of engine]
Event type : Alarm generated
Description : Engine is broken
Timestamp : 2013-12-01T16:33:01.000
Value : (
Resource identifier : [ID of component1], State : Failed,
Resource identifier : [ID of component2], State : Stopped,
Resource identifier : [ID of component3], State : Running)
This example demonstrates the situation where the event “Alarm generated” with the
description “Engine is broken” refers to the list of the states (i.e., current conditions) of all
relevant engine components.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 18 / 19
4.3 Counters and timers
Counters and timers can be used to keep track of how often (counter) or how long (timer)
certain conditions are reached by equipment. Examples of timer types are: operating hours,
non-operating hours, overload hours, etc. Examples of counter types are: starts/stops,
opened/closed, failed to start/stop, failed to open/close, emergency shut downs, etc. Both
counters and timers include a value and a reset timestamp.
Example of the result of a request for a counter value regarding a specific engine:
Counter type : Starts
Resource identifier : [ID of engine]
Value : 13
Reset timestamp : 2013-12-01T00:00:00.000
The example above provides the information that this engine is started 13 times since the first
of December 2013.
This standard does not provide a fixed list of counter types, because these strongly depend
on the properties of the equipment, the implementation that is used, etc. The counter types
can therefore be self-defined. In part 2 of this standard is explained how to request all defined
counter types for a specific piece of equipment.
iShare@Sea standard | Part 1: Functional Documentation | v1.0 FINAL 19 / 19
4.4 Context information
In addition to condition based maintenance information about the equipment on board of a
ship, context information about the ship and its surroundings might be needed to be able to
interpret and analyse the condition information correctly.
Currently only the location information, geo-coordinates and local time zone, are specified in
part 2, the technical interface specification.
The following table provides an overview of other context information identified during the
development of this standard that needs to be further specified and included in the technical
interface specification.
Elements Definition
Ship ID IMO or other ship number
Velocity over water m/s
Velocity over ground m/s
Rotational motions Pitch Trim
Roll List
Yaw
Sea state UOM WMO Sea State Code
Value Time Stamp Sensor ID
Sea swell Character of the sea swell
Location Latitude
Longitude
Time
Loading conditions Freeboard
Temperature Type Seawater, air
Value
Operational modus Type e.g. sailing, in mission, docked