ISO 19848:2018

INTERNATIONAL ISO
STANDARD 19848
First edition
2018-10
Ships and marine technology —
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 2018
© ISO 2018
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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2018 – All rights reserved

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 General . 4
5.2 Data Channel ID . 4
5.2.1 Universal ID . 4
5.2.2 Local ID . 5
5.2.3 Short ID . 6
5.2.4 Example of Data Channel ID . 7
5.3 Data Channel Property . 7
6 Time Series Data .11
6.1 General .11
6.2 Type of Time Series Data .12
6.2.1 Tabular Data . .12
6.2.2 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 .19
7.5.1 Data model .19
7.5.2 Logical structure .20
Annex A (Normative) Implementation .24
Annex B (informative) Examples of Local ID definitions — jsmea_mac .41
Annex C (informative) Examples of LocalID definitions — DNVGL-VIS.44
Bibliography .57
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 documents 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).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/patents).
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.
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 © ISO 2018 – All rights reserved

Introduction
On-board computer applications for safety and energy-efficient operations have become popular. These
applications require access to data of shipboard machinery and equipment.
To access data of navigational equipment, a data exchange standard, the IEC 61162 series can be
used. However, access of data from other on-board components and systems (e.g. machinery, safety
equipment and hull) have not yet been standardised.
Exchanging non-standardised data between and/or among applications requires name-based
aggregation and format mapping. However, this requires a large amount of labour, which hinders the
use of such data.
To improve these situations, this document defines unified rules for developing machine and human-
readable identifiers and data structures for shipboard machinery and equipment, with the objective to
facilitate 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 it 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.
There are three types of Data Channel ID. One is Local ID, which is a unique identifier used on-board a
ship, and another is Universal ID, which is a universal identifier, composed of Name Entity, Ship ID (e.g.,
IMO numbers) and Local ID. The other ID is Short ID, a short alternative ID of Local ID.
The purpose of this document is for exchanging data on-board a ship; however, in the future, shipboard
machinery and equipment may 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 categorised in accordance with the standardised categorising
rule and named by concatenating these category names with slashes.
In Annexes B and C, two types of categorising rules and example of codebook, lists of standardised
category names given in accordance with the rules, are defined for reference.
They are not designed to unify Data Channel ID, but it is assumed that some entities will develop,
maintain and manage codebook and that they will be disclosed widely.
Data Channel Property is assumed to be used to automate data processing and help understanding of
data. Data Channel Property shall be used because it is considered to be essential to both computer
applications and humans for the reasons mentioned above.
Time Series Data is a concept that represents collection of time-stamped data. Time Series Data is
assumed to be used for sharing latest data and for analysing trends made over time-stamped data.
For reliable data exchange, this document mandates the use of XML (Extensible Markup Language)
and XML Schema for data encoding and data structure definition. Using XML and XML schemas makes
it possible to define data structures precisely and validate data in accordance with such definitions.
As a result, it is believed that data can be exchanged more reliably between and/or among computer
applications.
Further, for convenience and efficiency, this document also defines data-structures in JSON and
CSV format.
It is assumed that data from shipboard machinery and equipment will be collected by shipboard data
servers, which are defined in ISO 19847. Then, the data encoded in accordance with this document, in
some cases, could be encrypted for security reasons, will be shared between and/or among computer
applications in a wide variety of means, such as in Hyper Text Transfer Protocol (HTTP), in Message
Queue Telemetry Transport (MQTT) or by e-mail through the servers. As described above, external
computer applications can retrieve on-board data uniformly by accessing the servers.
vi © ISO 2018 – All rights reserved

INTERNATIONAL STANDARD ISO 19848:2018(E)
Ships and marine technology — Standard data for
shipboard machinery and equipment
1 Scope
This document applies to the structure of the ship and to shipboard machinery and equipment, and
is intended for implementers of software used for the capture and processing of sensor data from the
objects mentioned above.
For those purposes, this document describes the way to name the sensor, required data item, and the
way to describe the data above.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 8601, Data elements and interchange formats — Information interchange — Representation of dates
and times
ISO/IEC 80000 series, Quantities and units
W3C XML: Extensible Markup Language (XML) 1.0, W3C Recommendation
W3C XML Schema Part 1: XML Schema Part 1: Structures, W3C Recommendation
W3C XML Schema Part 2: XML Schema Part 2: Datatypes, W3C Recommendation
RFC 3339, Date and Time on the Internet: Timestamps
RFC 4180, Common Format and MIME Type for Comma-Separated Values (CSV) Files
RFC 5234, Augmented BNF for Syntax Specifications: ABNF
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http: //www .electropedia .org/
— ISO Online browsing platform: available at https: //www .iso .org/obp
3.1
alert data
information that represents abnormal conditions of shipboard machinery and equipment
3.2
analogue data
numerical information obtained from sensors such as temperature sensors and pressure sensors
Note 1 to entry: Analogue data is a physical value converted from raw electric signals, such as 4-20 mA or 0-5 V.
3.3
codebook
list of standardised names
3.4
data
measurement value from shipboard machinery and equipment to which a timestamp is added
3.5
Data Channel
virtual channel for data transmission from shipboard machinery and equipment to shipboard data
server, defining static properties of data
3.6
Data Channel ID
identifier for Data Channel that identifies Data Channel universally and on-board a ship
Note 1 to entry: There are three types of Data Channel ID: Universal ID, Local ID and Short ID.
3.7
Data Channel List
list of definitions for Data Channel that define Data Channel ID and Data Channel Property, and is shared
through the shipboard data server
3.8
Data Channel Property
attributes of Data Channel, such as units and ranges
3.9
Data Set
set of Data having the same timestamp
3.10
Extensible Markup Language
XML
text-based data description language used for exchanging data on the Internet
3.11
Hyper Text Transfer Protocol
HTTP
communication protocol used to exchange HTML (Hyper Text Markup Language) or other content on
the Internet
3.12
IMO Number
unique reference number for ships that is given by the International Maritime Organisation (IMO)
3.13
logical structure
structure of data that is independent of physical implementation
3.14
measurement value
numeric value or a status symbol, produced as a result of measuring, calculating or estimating the state
of various objects
3.15
metadata
data that describes information about other data
2 © ISO 2018 – All rights reserved

3.16
Name Object
building block of Data Channel ID used to define the hierarchical structure of Data Channel ID
3.17
Namespace
set of names that is used in order to avoid conflicts of names
3.18
Shipboard Data Server
ship’s “information hub” that stores data from shipboard machinery and equipment, shares data at sea
including machine data, and sends stored data outboard
Note 1 to entry: See ISO 19847 for details.
3.19
shipboard machinery and equipment
various systems located in ships machinery space, such as main engine, generator, pumps, fans, valves,
pipelines and electric control systems
3.20
status data
information that represents the condition of shipboard machinery and equipment
3.21
Time Series Data
collection of a Data Set
3.22
XML Schema
data definition language used for XML
4 Abbreviated terms
ABNF Augmented Backus Naur Form
AMS Alarm Monitoring System
BNF Backus Naur Form
IAS Integrated Automation System
IMO International Maritime Organisation
HIN Hull Identification Number
HTML Hyper Text Markup Language
HTTP Hypertext Transfer Protocol
RFC Request for Comments
SI The International Systems of Units
URI Uniform Resource Identifier
UTC Universal Time Coordinated
UTF-8 UCS Transformation Format 8
XML Extensible Markup Language
5 Data Channel
5.1 General
Data Channel is composed of Data Channel ID and Data Channel Property.
Data Channel ID is an identifier for Data Channel, and Data Channel Property represents attributes of
Data Channel.
5.2 Data Channel ID
There are three types of Data Channel ID:
— Universal ID;
— Local ID;
— Short ID.
Universal ID is for identifying on-board Data Channel universally.
Local ID, meanwhile, is for identifying on-board Data Channel locally. For instance, on-board computer
systems, such as the Integrated Automation System (IAS) and the Alarm Monitoring System (AMS), have
their own Data Channel List, which is composed of unique Channel ID. This Channel ID can correspond
to Local ID.
Short ID is an optional short alternative identifier of Local ID for usability and data compression. This
short identifier, for instance, can be used as Data Channel identifier in the Time Series Data format.
Local ID and Short ID shall be unique for a ship.
These IDs shall be case-insensitive to avoid unexpected mistyping.
NOTE Data Channel of the same kind of sensors on different ships is expected to have a same Local ID.
Conversely, even if Data Channel has a same meaning, Short ID may be different for each ship.
5.2.1 Universal ID
Universal ID is an URI conforming to the requirements below, in addition to those of the URI definition.
The URI definition allows for many different compositions, but the Universal ID will be a subset of these
and shall be in the following format.
Universal ID composition is defined by using Augmented BNF(ABNF), which is defined in RFC 5234, as
follows.
4 © ISO 2018 – All rights reserved

UniversalID = [protocol] "//" NamingEntity ShipID LocalID
NamingEntity = authority
ShipID = path-element
path-element = "/" unreserved
path-elements = path-element | path-element path-elements
Definition of the “Local ID” element is mentioned in 5.2.2.
The “authority” and “unreserved” element is defined in the URI definition. The “protocol” element is
optional.
NOTE 1 Though path element of URI that is defined in RFC 3986 accepts much more characters, such as
RFC 3986 “sub-delimiters”, “:”, “@”, etc., this document only accepts RFC 3986 “unreserved” characters since
these characters may be used as control character in ISO 19847. (Definition of sub-delimiters and unreserved are
defined in RFC 3986).
The slash (“/”) is a reserved character for describing hierarchies.
a) Naming Entity
Naming Entity element shall be a domain owned or controlled by the entity producing Local ID.
EXAMPLE
— data.shipdatacenter.jp
— data.dnvgl.com
b) Ship ID
Ship ID is for identifying ships universally.
Usually, an IMO number or HIN should be used for Ship ID.
If ships have no IMO number or HIN, an identifier provided by countries or regions, or other means
may be used instead.
EXAMPLE
— /IMO1234567
— /JP-HXAB7A33G293
5.2.2 Local ID
Local ID consists of Naming Rule and Local Data Name.
Local ID composition is defined by using ABNF as follows
LocalID = NamingRule LocalDataName
NamingRule = path-element
LocalDataName = path-elements
path-element = "/" unreserved
path-elements = path-element | path-element path-elements
a) Naming Rule
Naming Rule shall be the designated name for the rule used to name Data Channel.
This name can be set freely under the supervision of Naming Entity, and shall have a symbol that
represents Naming Entity in front to eliminate duplications.
A Naming Rule is a set of requirements that define a naming scheme (or an identification scheme)
for components and systems on-board the ship. A Naming Rule shall define how identification
strings are composed, and the method of developing an identification string.
EXAMPLE
— /jsmea_mac
— /dnvgl-vis
b) Local Data Name
Local Data Name is an identifier for Data Channel that is named in accordance with Naming Rule.
The syntax of the identification string shall be disclosed and precisely defined using ABNF.
EXAMPLE
— /MainEngine/Cylinder1/ExhaustGas/Temp
— /411.1/C101.31+1/ExhGas+t(C)
5.2.3 Short ID
Short ID is an optional short alternative to Local ID. There must be a one-to-one correspondence
between Data Channel and Short ID; Short ID shall therefore be unique for a ship.
Definition of Short ID is as follows.
ShortID = unreserved
Short ID shall be as short as practical and represented as machine-friendly symbols, human-friendly
short word, or a combination of those symbols and short word.
EXAMPLE
— 0001
— TAH001
— ME_RPM
6 © ISO 2018 – All rights reserved

5.2.4 Example of Data Channel ID
In the following example, Ship ID, Naming Rule and Local Data Name will be understood as the above
definition, but without the leading slash.
Universal ID http: //data .shipdatacenter .jp/imo1234567/jsmea
_mac/MainEngine/Cylinder1/ExhaustGas/Outlet/Temp
Local ID /jsmea_mac/MainEngine/Cylinder1/ExhaustGas/Outlet/Temp
Short ID 0001
Ship ID imo1234567
Naming Entity data.shipdatacenter.jp
Naming Rule jsmea_mac
Local Data Name MainEngine/Cylinder1/ExhaustGas/Outlet/Temp

Universal ID http: //data .dnvgl .com/imo1234567/dnvgl -vis/411 .1/C101 .31+1/ExhGas+t(C)
Local ID /dnvgl-vis/411.1/C101.31+1/ExhGas+t(C)
Short ID 0001
Ship ID imo1234567
Naming Entity data.dnvgl.com
Naming Rule dnvgl-vis
Local Data Name 411.1/C101.31+1/ExhGas+t(C)
NOTE 1 It is not a requirement that the Universal ID be a resolvable URI, i.e., the URI is not necessarily a
valid URL.
5.3 Data Channel Property
Data Channel Property shall be defined to provide the attributes of Data Channel.
The reserved property types are as follows.
— Data Channel Type
— Format
— Range
— Unit
— Quality Coding
— Name
— Remarks
The properties above shall be described in accordance with the rules in this Clause.
Properties that are not listed above may be used if these are clearly distinguished from the properties
defined in the standard.
Details of each property are as follows.
a) Data Channel Type
Data Channel Type is used to identify the types of Data Channel, such as row numeric value, average
value, alarms and status. Data Channel Type is composed of the following sub-properties.
— Type
— Update Cycle
— Calculation Period
Type sub-property defines type of Data Channel and the value of the property follows the definitions
mentioned in Table 1.
Table 1 — Type name of Data Channel Type
Type Description
Inst Measuring value at a certain point in time.
Average Average of the value within a certain time period.
"Average" does not mean average of values from multiple sensors at the same time
but average of time-series values from single sensor.
Max Maximum value within a certain time period.
"Maximum" does not mean maximum of values from multiple sensors at the same
time but maximum of time-series values from single sensor.
Min Minimum value within a certain time period.
"Minimum" does not mean minimum of values from multiple sensors at the same
time but minimum of time-series values from single sensor.
StandardDeviation Standard deviation of the value within a certain time period.
"StandardDeviation" does not mean standard deviation of values from multiple sen-
sors at the same time but standard deviation of time-series values from single sensor.
Calculated Value obtained from calculation instead of measurement.
SetPoint Target value for automatic control.
ControlOutput Manipulated value of automatic control.
Alert Alarm values that can be obtained are also described.
Status Status values that can be obtained are also described.
ManuallyInput Value input by crew. Value assumed here is reading of indicator.
Update Cycle represents the cycle of updating measurement value. This sub-property shall be used
when measurement value is updated periodically.
When a value of Data Channel is a result of calculation that uses measurement value of specific time
periods, Calculation Period shall be used to describe the said period.
Update Cycle and Calculation Period shall be described with a decimal number that is larger than
zero. The unit of Update Cycle and Calculation Period shall be the “second”.
Type sub-property is mandatory and the others are optional.
EXAMPLES
— Type  Average
— Calculation Period 60
— Update Cycle 1
b) Format
Format is used for describing data formats and defined by the following sub-properties.
— Type
— Restriction
8 © ISO 2018 – All rights reserved

Type sub-property is mandatory and Restriction sub-property is optional. More than one
Restriction sub-property may exist under the Format property.
Available Types are as follows. Definitions of these data types comply with W3C XML Schema
Definition Language (XSD) 1.1 Part 2: Datatype.
Table 2 — Available Datatype for Format property
Type Description
Decimal Decimal represents a subset of the real numbers, which can be represented by
decimal numerals. The value space of decimal is the set of numbers that can be
obtained by dividing an integer by a non-negative power of ten, i.e., expressible as
n
i / 10 where i and n are integers and n ≥0. Precision is not reflected in this value
space; the number 2.0 is not distinct from the number 2.00. The order relation on
decimal is the order relation on real numbers, restricted to this subset.
Integer Integer is·derived·from decimal by fixing the value of fraction digits to be 0 and
disallowing the trailing decimal point. This results in the standard mathematical
concept of the integer numbers. The value space of integer is the infinite set {.,-2,-
1,0,1,2,.}. The base type of integer is decimal.
Boolean Boolean represents the values of two-valued logic.
String The string datatype represents character strings in XML.
DateTime Date and time data types are used for values that contain date and time.
Format shall follow ISO 8601 "YYYY -MM -DDThh: mm: ssZ" where:
YYYY indicates the year
MM indicates the month
DD indicates the day
T indicates the start of the required time section
hh indicates the hour
mm indicates the minute
ss indicates the second
Z indicates UTC
Following restrictions defined in W3C XML Schema are available to define acceptable values.
Validation rules and available constraint for each data types shall follow W3C XML Schema.
Table 3 — Restrictions for Format property
Restriction Description Data Type
Enumeration Defines a list of acceptable values. string
FractionDigits Specifies the maximum number of decimal places allowed. nonNegativeInteger
Must be equal to or greater than zero.
Length Specifies the exact number of characters or list items allowed. nonNegativeInteger
Must be equal to or greater than zero.
MaxExclusive Specifies the upper bounds for numeric values (the value must A value from the ·value space·
be less than this value). of the {base type definition}.
MaxInclusive Specifies the upper bounds for numeric values (the value must A value from the ·value space·
be less than or equal to this value). of the {base type definition}.
MaxLength Specifies the maximum number of characters or list items nonNegativeInteger
allowed. Must be equal to or greater than zero.
MinExclusive Specifies the lower bounds for numeric values (the value must A value from the ·value space·
be greater than this value). of the {base type definition}.
MinInclusive Specifies the lower bounds for numeric values (the value must A value from the ·value space·
be greater than or equal to this value). of the {base type definition}.
Table 3 (continued)
Restriction Description Data Type
MinLength Specifies the minimum number of characters or list items nonNegativeInteger
allowed. Must be equal to or greater than zero.
Pattern Defines the exact sequence of characters that are acceptable. string
TotalDigits Specifies the exact number of digits allowed. Must be greater positiveInteger
than zero.
WhiteSpace Specifies how white space (line feeds, tabs, spaces, and car-
riage returns) is handled.
EXAMPLES
— Type Decimal
— Restriction TotalDigits 8, FractionDigits 3
c) Range
Range is for describing Data Range. Range property is composed of the following sub-properties.
— Low
— High
Low sub-property represents lower limit of the analogue data, and High sub-property represents
its upper limit.
The value type of these sub-properties is decimal value or empty. The value of these sub-properties
can be empty only if lower and/or upper limit cannot be specified.
Further, High value must be greater than and not equal to Low value.
Range property is mandatory only of the analogue data.
NOTE Range does not mean upper and lower boundary of the value. The value can exceed the range in
case of sensor failure or other abnormal condition.
EXAMPLES
— Low 0
— High 120
d) Unit
Unit defines the unit and quantity applied to the measurement value. Unit property is composed of
the following sub-properties.
— Unit Symbol
— Quantity Name
Unit symbols and quantity names defined in ISO 80000 or Table 4 shall be used for Unit Symbol and
Quantity Name sub-properties.
Unit Symbol sub-property represents unit symbol of the measurement value (e.g., “m” for length
and “kg” for mass). The value of Unit Symbol sub-property can be empty only for non-dimensional
quantities.
Quantity Name sub-property may be used to identify the variable that is measured or computed for
the physical item defined by the Data Channel.
10 © ISO 2018 – All rights reserved

The measurement value shall be described according to the Unit defined in this property.
NOTE On-board computer applications (Data consumer) can convert Unit according to ISO 80000.
EXAMPLES
— Unit Symbol kW
— Quantity Name active power
— Unit Symbol Pa
— Quantity Name pressure
Table 4 — Additional units and quantities of measurement value
Quantity Name Unit Symbol Remarks
Cargo capacity TEU Twenty-foot Equivalent Unit
FEU Forty-foot Equivalent Unit
e) Quality Coding
Quality Coding represents a name of data quality evaluation scheme and the scheme shall be able to
distinguish at least between valid and invalid measurement values of the Data Channel.
EXAMPLES
— "OPC-QUALITY".
— "IEC 61162-STATUS".
In the case of "IEC 61162-STATUS", "A" (Data valid) and "V" (Data invalid) are used for the data
quality.
f) Name
Name can be used to describe names assigned for on-board control systems and other instruments.
EXAMPLE
— “Main Engine Revolution”.
g) Remarks
In Remarks, arbitrary complementary information on Data Channel is described.
Remarks should include locations, manufacturers and types of equipment.
EXAMPLE
— “Location: ECR, Manufacturer: AAA Company, Type: TYPE-AAA”.
6 Time Series Data
6.1 General
Time Series Data is a collection of measurement values in which all the values have a corresponding
time of measurement. Usually such data is arranged and recorded in chronological order.
6.2 Type of Time Series Data
For practical purposes (efficient data transport), two distinct representations of Time Series Data are
defined:
— Tabular Data;
— Event Data.
These representations are used depending on update interval of measurement values.
6.2.1 Tabular Data
Tabular Data is a vector of a fixed number of values expected to be reported at regular interval. Data
Channel List defines the interval.
Some examples of Tabular Data are:
— multiple raw numeric values from sensors/transmitters sampled at the same time;
— result of the calculation (e.g. time average, standard deviation, etc.) to be performed regularly.
Measurement values are grouped per timestamp, thus Tabular Data forms like Table 5.
Table 5 — Example of Tabular Data
Time Stamp Data Channel 1 Data Channel 2 Data Channel 3 Data Channel 4
2017-01-01T00:00:00Z 101.2 0.30 10.2 CLOSE
2017-01-01T00:00:01Z 0.0 0.30 10.2 CLOSE
2017-01-01T00:00:02Z 110.9 0.32 10.2 OPEN
6.2.2 Event Data
Event Data is a collection of data for which the number of values at a specific time is not fixed.
Some examples of Event Data are:
— alarm information;
— status information;
— manually input data.
Event Data typically forms in tabular form like Table 6:
Table 6 — Example of Event Data by tabular form
Time Stamp Data Channel 1 Data Channel 2 Data Channel 3 Data Channel 4
2017-01-01T00:00:00Z 101.2 — — —
2017-01-01T00:00:01Z — — — —
2017-01-01T00:00:02Z 110.9 0.32 — OPEN
Tabular form mentioned above is not efficient for Event Data, thus measurement values are grouped per
both timestamp and Data Channel ID and forms like Table 7:
12 © ISO 2018 – All rights reserved

Table 7 — Example of Event Data
Time Stamp Data Channel ID Value
2017-01-01T00:00:00Z Data Channel 1 101.2
2017-01-01T00:00:02Z Data Channel 1 110.9
2017-01-01T00:00:02Z Data Channel 2 0.32
2017-01-01T00:00:02Z Data Channel 4 OPEN
6.3 Time Series Data Composition
Each row of Tabular/Event Data is called Data Set.
Tabular Data is composed of a collection of Data Set without Data Channel IDs, since value can be
identified by its order.
Tabular Data of Table 5 is described as follows.
DataSet("2017-01-01T00:00:00Z","101.2","0.30","10.2","CLOSE")
DataSet("2017-01-01T00:00:01Z","0.0","0.30","10.2","CLOSE")
DataSet("2017-01-01T00:00:02Z","110.9","0.32", "10.2","OPEN")
Event Data is composed of a collection of Data Set with Data Channel ID, since a number of values at a
specific time cannot be fixed.
Event Data of Table 7 is described as follows.
DataSet("2017-01-01T00:00:00Z ", "DataChannel1", "101.2")
DataSet("2017-01-01T00:00:02Z ", "DataChannel1", "110.9")
DataSet("2017-01-01T00:00:02Z ", "DataChannel2", "0.32" )
DataSet("2017-01-01T00:00:02Z ", "DataChannel4", "OPEN" )
7 Data structure
7.1 General
Data structure is the definition of logical structures that are independent from data implementation
languages, such as XML, JSON, CSV and others.
This Clause defines two types of data structure. One is for Data Channel List, the list of Data Channel
definitions in Clause 5, and the other is for serialisation and transport of Time Series Data in Clause 6.
These structures can be described by using XML, JSON and CSV.
In addition, standard data type, which is used to define the data structure and also independent of
implementation languages, is defined.
Standard data type can be replaced with the data types defined in the implementation language.
Data implemented in accordance with the data structure can be shared between and/or among
computer applications.
7.2 Implementation language
Data structure defined in this Clause shall be implemented in accordance with Annex A.
7.3 Standard data types
To define the data Structure, the following standard data types derived from UML primitive types
listed in Table 8 are used.
Table 8 — Standard data types
Standard data type Primitive type Restriction Remarks
Integer Integer
NonNegativeInteger Integer larger than −1
PositiveInteger Integer larger than 0
Real Real
Boolean Boolean
String String
DateTime String formatted by Refer to RFC3339 for ABNF expression.
ISO 8601
Null Null specifies the lack of a value (can be used for
any data types).
7.4 Structure of Data Channel List
7.4.1 Data model
Data Channel List shall consist of the following five elements.
a) Package
Package is a data package that is made up of Header, which is a set of metadata, and DataChannel,
which is a main data body.
b) Header
Header indicates when Data Channel List is created and who creates it.
c) DataChannel
DataChannel consists of Property and DataChannelId, which indicates Data Channel definitions.
d) DataChannelID
DataChannelID is an identifier of Data Channel defined in 5.2.
e) Property
Property defines the attributes of Data Channel defined in 5.3.
These elements are arranged in the hierarchic structure shown in Figure 1.
14 © ISO 2018 – All rights reserved

Figure 1 — Model of Data Channel List
7.4.2 Logical structure
Data Channel List shall have the logical structure shown in Figure 2.
Data Channel List has a Package element. The Package element is composed of a Header and a
DataChannelList element. The DataChannelList element includes one or more DataChannel elements
with its IDs and properties.
Further, NameObject element may be added to define structure of Local ID.
Figure 2 — Logical structure of Data Channel List
Details of each element are described below.
a) Package structure
Name Data type Note Mandatory/ Max
Option count
Header b) Header See b). Mandatory 1
DataChannelList d) DataChannelList See d). Mandatory 1
16 © ISO 2018 – All rights reserved

b) Header structure
Name Data type Note Mandatory/ Max
Option count
ShipID String See 5.2.1. Mandatory 1
DataChannelListID c) ConfigurationReference See c). Mandatory 1
Author String Author of Data Channel Optional 1
List.
DateCreated DateTime Date when Package is Optional 1
created.
c) ConfigurationReference structure
Name Data type Note Mandatory/ Max
Option count
ID String Identifier of Data Channel Mandatory 1
List itself.
TimeStamp DateTime Modified Date & Time. Mandatory 1
d) DataChannelList structure
Name Data type Note Mandatory/ Max
Option count
DataChannel e) DataChannel See e). Mandatory *
e) DataChannel structure
Name Data type Note Mandatory/ Max
Option count
DataChannelID f) DataChannelID See f). Mandatory 1
Property g) Property See g). Mandatory 1
f) DataChannelID structure
Name Data type Note Mandatory/ Max
Option count
LocalID String See 5.2.2. Mandatory 1
ShortID String See 5.2.3. Optional 1
NameObject m) NameObject Definition of Local Data Optional 1
Name structure.
g) Property structure
Name Data type Note Mandatory/ Max
Option count
DataChannelType h) DataChannelType See h) and 5.3 a). Mandatory 1
Format i) Format See i) and 5.3 b). Mandatory 1
Range k) Range See k) and 5.3 c). Mandatory* 1
Unit l) Unit See l) and 5.3 d). Mandatory* 1
* Range and Unit are required only when Data Channel Type is “Decimal”.
Name Data type Note Mandatory/ Max
Option count
QualityCoding String 5.3 e). Optional 1
Name String See 5.3 f). Optional 1
Remarks String See 5.3 g). Optional 1
* Range and Unit are required only when Data Channel Type is “Decimal”.
h) DataChannelType structure
Name Data type Note Mandatory/ Max
Option count
Type String Described in accordance Mandatory 1
with Data Channel Type
UpdateCycle Real Optional 1
format shown in 5.3 a).
CalculationPeriod Real Optional 1
i) Format structure
Name Data type Note Mandatory/ Max
Option count
Type String Described in accordance Mandatory 1
with Data Channel Type
Restriction j) Restriction Optional 1
format shown in 5.3 b).
j) Restriction structure
Name Data type Note Mandatory/ Max
Option count
Enumeration String Described in accordance Optional *
with Data Channel Type for-
FractionDigits Integer Optional 1
mat shown in 5.3 b) Table 3.
Length Integer Optional 1
MaxExclusive Real Optional 1
MaxInclusive Real Optional 1
MaxLength Integer Optional 1
MinExclusive Real Optional 1
MinInclusive Real Optional 1
MinLength Integer Optional 1
Pattern String Optional 1
TotalDigits Integer Optional 1
One of the following: Optional 1
“Preserve”
WhiteSpace
“Replace”
“Collapse”
k) Range structure
Name Data type Note Mandatory/ Max
Option count
Low Real Lower limit of measuring range. Mandatory 1
High Real Upper limit of measuring range. Mandatory 1
18 © ISO 2018 – All rights reserved

l) Unit structure
Name Data type Note Mandatory Max
/Option count
Unit symbol defined in ISO 80000 or
UnitSymbol String Mandatory 1
5.3 d) Table 4.
Quantity name defined in ISO 80000 or
QuantityName String Optional 1
5.3 d) Table 4.
m) NameObject stru
...