Ships and marine technology — Standard data for shipboard machinery and equipment

This document provides requirements and guidance on the capture and processing of data from sensors monitoring: ¾ the structure of the ship; ¾ shipboard machinery and equipment on board the ship; ¾ ship operational information. It is intended for implementers of software used to capture and process such data. This document describes how to name the sensor and required data item, as well as how to describe the data for shipboard machinery and equipment.

Navires et technologie maritime — Données normalisées pour les machines et équipements à bord des navires

General Information

Status
Published
Publication Date
08-Feb-2024
Current Stage
6060 - International Standard published
Start Date
09-Feb-2024
Due Date
01-Oct-2023
Completion Date
09-Feb-2024
Ref Project

Relations

Standard
ISO 19848:2024 - Ships and marine technology — Standard data for shipboard machinery and equipment Released:9. 02. 2024
English language
135 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


International
Standard
ISO 19848
Second edition
Ships and marine technology —
2024-02
Standard data for shipboard
machinery and equipment
Navires et technologie maritime — Données normalisées pour les
machines et équipements à bord des navires
Reference number
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 Data Channel . 4
5.1 Data Channel ID .4
5.1.1 General .4
5.1.2 Universal ID .4
5.1.3 Local ID .5
5.1.4 Short ID .6
5.1.5 Example of Data Channel ID .6
5.2 Data Channel Property .7
6 Time Series Data .12
6.1 General . 12
6.2 Type of Time Series Data . 12
6.2.1 General . 12
6.2.2 Tabular Data . 12
6.2.3 Event Data . 12
6.3 Time Series Data Composition . 13
7 Data structure .13
7.1 General . 13
7.2 Implementation language .14
7.3 Standard data types .14
7.4 Structure of Data Channel List .14
7.4.1 Data model .14
7.4.2 Logical structure . 15
7.5 Structure of Time Series Data . 20
7.5.1 Data model . 20
7.5.2 Logical structure .21
Annex A (normative) General requirement of data implementation .26
Annex B (informative) Examples of Local ID definitions — jsmea_codebook .51
Annex C (informative) The “dnv-v2” naming scheme — explanations and examples of LocalID
definitions .108
Bibliography .135

iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 8, Ships and marine technology, Subcommittee
SC 6, Navigation and ship operations.
This second edition cancels and replaces the first edition (ISO 19848:2018), which has been technically
revised.
The main changes are as follows:
— Annex A has been updated to define JSON as an equivalent implementation alternative to XML for
DataChannelLists and TimeSeriesData. JSON schemas have been introduced to ensure precise definition
and validation.
— The example of the codebook in B.2 has been extended to include navigational information, voyage
information, weather information around the ship, oil property information and ship motion information.
— In B.3, a full set of standard data names has been added as references, to improve usability.
— In Annex C, the naming scheme has been changed from from “dnvgl-vis” to “dnv-v2”, as well as various
updates to the rules for constructing the LocalID.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

iv
Introduction
On-board computer applications for safety and energy-efficient operations have become increasingly
popular. These applications require access to the data of shipboard machinery and equipment.
To access data of navigational equipment, the IEC 61162 series, which covers data exchange, can be used.
However, there are no existing standards covering the access of data from other on-board components and
systems (e.g. machinery, safety equipment, and hull).
Exchanging nonstandardized data between and/or among applications requires name-based aggregation
and format mapping. However, this involves a large amount of labour, which hinders the use of such data.
To improve such situations, this document defines unified requirements and guidelines for developing
machine and human-readable identifiers and data structures for shipboard machinery and equipment, with
the objective of facilitating the exchange and processing of sensor data from ships.
This document defines two concepts and their models for data exchange: one is Data Channel, and the
other is Time Series Data. This document thus defines two distinct data structures and file formats: A Data
Channel List, which contains the necessary meta-data, and a Time Series Data format for measurements.
The time-series format is designed to be lightweight and therefore contains minimal meta-data information,
only in the form of a reference to the channel list.
Data Channel is a concept that represents virtual data transmission channels, and defines time-invariant
properties. Data Channel can be viewed as a static description for the different sensor data streams. Data
Channel is composed of Data Channel ID and Data Channel Property. Data Channel ID uniquely identifies the
logical data channels. Data Channel Property defines attributes of Data Channel.
The purpose of this document is to provide guidance and requirements on exchanging data on board a ship.
However, in the future, it is possible that shipboard machinery and equipment will be connected directly to
the Internet.
Therefore, considering the compatibility between Data Channel ID and URLs, which are used to identify
data on the Internet, Data Channel ID has a hierarchical structure with slashes as delimiters. To represent a
hierarchy, Data Channel is categorized in accordance with the standardized naming scheme, called Naming
Rule, and named by concatenating these category names with slashes.
Annexes B and C provide two types of naming scheme, an example of a codebook and lists of standardized
category names given according to these schemes.
These naming schemes provided in Annexes B and C are not designed to unify Data Channel ID, but it is
assumed that some entities will develop, maintain and manage codebooks and that these codebooks will be
disclosed widely.
Data Channel Property is assumed to be used
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.