ISO 19847:2024

International
Standard
ISO 19847
Second edition
Ships and marine technology —
2024-02
Shipboard data servers for sharing
field data at sea
Navires et technologie maritime — Serveurs de données
embarqués pour partager les données de terrain en mer
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 .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 6
5 General requirements for the shipboard data server . 7
5.1 Function and performance of the shipboard data server .7
5.1.1 Processing performance . .7
5.1.2 Storage function .10
5.1.3 Interface function .10
5.1.4 Condition monitoring function .11
5.1.5 Data backup and restoration functions .11
5.1.6 Function to protect against unauthorised access .11
5.1.7 Status reporting .11
5.2 Environmental performance of shipboard data server . 12
5.2.1 Power-supply performance . 12
5.2.2 Vibration-resistant feature . 12
5.2.3 Requirement for electromagnetic immunity and emission . 12
5.2.4 Temperature and humidity resistant requirements . 13
5.3 Installation requirements for shipboard data server . 13
5.3.1 Environment requirements . 13
5.3.2 Requirements for maintenance areas . 13
5.3.3 Requirement for networks and network security. 13
6 Data input/output and data management on shipboard data server. 14
6.1 General .14
6.2 Data management function .14
6.2.1 General .14
6.2.2 Management of system clock .14
6.2.3 Management of Data Channel List .14
6.2.4 Management of Data Source Information . 15
6.2.5 Management of Alias List . 15
6.3 Data input and output functions . 15
6.3.1 General . 15
6.3.2 Input function .16
6.3.3 Output function .17
6.3.4 Request-response data transport service.17
6.3.5 Streaming data transport service .18
6.3.6 File transport service .18
6.4 Alias function .18
6.4.1 General .18
6.4.2 Alias List .19
6.5 Data calculation function .19
6.5.1 General .19
6.6 Log management function . .19
7 Operation requirements . .20
7.1 General . 20
7.2 Protection from logical threats . 20
7.2.1 Access control . 20
7.2.2 Usage control .21
7.2.3 Network access . 22
7.2.4 System defence . . 22

iii
7.3 Protection from physical threats . 23
7.3.1 General . 23
7.3.2 Installation requirements . 23
7.3.3 Connection cables . 23
7.3.4 Power source management . 23
7.3.5 Interfaces for removable devices .24
7.3.6 Protection (others) .24
7.3.7 Equipment maintenance .24
7.4 Software maintenance . 25
7.4.1 General . 25
7.4.2 Maintenance mode . . . 25
7.4.3 Setting changes . 25
7.4.4 Software update . 25
7.4.5 Failure recovery . 26
7.4.6 Software version information . 26
8 Test requirements .26
8.1 Outline . 26
8.2 Test items . 26
8.2.1 Test environments . 26
8.2.2 Test methods .27
Annex A (informative) Ship-to-shore communication management .43
Annex B (informative) Structure of Alias List .45
Annex C (normative) Request-response protocol.49
Annex D (normative) Streaming protocol .60
Annex E (normative) File input and output protocol by the HTTP(S) .62
Annex F (informative) Data source information .64
Annex G (informative) User management of the shipboard data server . 74
Annex H (informative) Internal calculation function .77
Bibliography .86

iv
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 19847:2018), which has been technically
revised.
The main changes are as follows:
— In Clause 7, a specific security requirement on the shipboard data server has been added.
— In Clause 8, a test standard in a tabular arrangement of test objectives, conditions, methods, and test
criteria has been added.
— In Annex H, implementation requirements for the calculation function have been added.
— In Clause 5, additional examples of an output statement for reporting status have been added.
— In Clause 6, an additional output function with JSON data has been added.
— In Annex C, additional query parameters to designate date and time, search for partial matches of Local
IDs and obtain down sampling data have been added.
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.

v
Introduction
Shipboard computer applications to ensure ships operate safely and efficiently are becoming increasingly
popular.
These applications require access to data which is provided by shipboard machinery and equipment.
Navigational instruments can use the IEC 61162 series of standards when exchanging data, but access to
other shipboard machinery and systems to obtain data has not yet been standardized.
For the purpose of sharing field data at sea, including non-standardized machinery data, this document
specifies requirements for performance, function, service and safety for the shipboard data server that
stores data from shipboard machinery and equipment, and sends stored data off the ship.
The shipboard data server is connected to an information network that is specified in ISO 16425. The
requirements for cyber security on the shipboard data server are specified.

vi
International Standard ISO 19847:2024(en)
Ships and marine technology — Shipboard data servers for
sharing field data at sea
1 Scope
This document specifies requirements for shipboard data servers that are used to collect data from other
shipboard machinery and systems, and to further share the collected data in a safe and efficient manner.
This document specifies communication protocols with reference to the data structure of ISO 19848.
This document is intended for users and developers of shipboard data servers, as well as users and
developers of systems that record data on, or retrieve data from, shipboard data servers.
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-1, Date and time — Representations for information interchange — Part 1: Basic rules
ISO 16425, Ships and marine technology — Guidelines for the installation of ship communication networks for
shipboard equipment and systems
ISO 19848:2024, Ships and marine technology — Standard data for shipboard machinery and equipment
IEC 60092-504:2016, Electrical installations in ships — Part 504: Special features — Control and instrumentation
IEC 60945, Maritime navigation and radiocommunication equipment and systems — General requirements —
Methods of testing and required test results
IEC 61162-1, Maritime navigation and radiocommunication equipment and systems — Digital interfaces —
Part 1: Single talker and multiple listeners
IEC 61162-450:2018, Maritime navigation and radiocommunication equipment and systems — Digital interfaces
— Part 450: Multiple talkers and multiple listeners — Ethernet interconnection
IEC 62923-1, Maritime navigation and radiocommunication equipment and systems — Bridge alert management
— Part 1: Operational and performance requirements, methods of testing and required test results
IEC 62923-2, Maritime navigation and radiocommunication equipment and systems — Bridge alert management
— Part 2: Alert and cluster identifiers and other additional features
INTERNET SOCIETY (ISOC) RFC 3986, Uniform Resource Identifier (URI): Generic Syntax [online]. Edited by T.
Berners-Lee, W3C/MIT, R. Fielding, Day Software, L. Masinter and Adobe Systems. January 2005 [viewed 2023-
05-13]. Available at https:// datatracker .ietf .org/ doc/ html/ rfc3986
IACS Rec.166, Recommendation on Cyber Resilience
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.

ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
actual recorded data
actual (sensor) data acquired from data providers (3.10) and recorded to the shipboard data server (3.38)
3.2
Alias ID
symbol to refer to one or more Local IDs (3.24) with different names
3.3
Alias List
list defining a list of virtual Data Channel IDs
Note 1 to entry: The Data Channel ID is the identifier for the Data Channel (3.7) that identifies Data Channel universally
and on-board a ship. There are three types of Data Channel ID: Universal ID, Local ID (3.24) and Short ID.
3.4
calculation function
functions to provide calculated data (e.g. min, max and average)
Note 1 to entry: The calculated data provided is in accordance with the calculation data structures specified in
ISO 19848.
3.5
calculation list
list which defines the calculation function (3.4) that executes calculations, and the input and output
parameters given to the calculation element
3.6
comma-separated value
CSV
method of storing tabular data in plain text in a file in which each row of the file forms a data record and in
which fields within one data record are separated by a comma character
3.7
Data Channel
virtual channel for data transmission from shipboard machinery and equipment to the shipboard data server
(3.38), defining static properties of data
[SOURCE: ISO 19848:2024, 3.5]
3.8
Data Channel List
list of definitions for the Data Channel (3.7) that define the Data Channel ID and the Data Channel Property,
and is shared through the shipboard data server (3.38)
Note 1 to entry: The Data Channel Property shows attributes of the Data Channel (3.7), such as units, ranges and
others.
[SOURCE: ISO 19848:2024, 3.7]
3.9
Data Channel Type
identification of the types of Data Channels (3.7), such as row numeric value, average value, alarms and
status
Note 1 to entry: See ISO 19848:2024, 5.2 a).

3.10
data provider
equipment that provides (sends) data to the shipboard data server (3.38) and has interfaces for providing
data
3.11
Data Source Information
description of communication protocols and formats in which a data provider (3.10) sends data
3.12
data sample
measurement datum that has a timestamp
3.13
eXtensible markup language
XML
text-based data description language used for exchanging data on the Internet
[SOURCE: ISO 19848:2024, 3.10]
3.14
file transfer protocol
FTP
protocol for transferring files between a server and clients
3.15
file transfer protocol over SSL/TLS
FTPS
protocol that encrypts data transmitted and received by file transfer protocol (3.14) with a secure sockets
layer (SSL) or transport layer security (TLS)
3.16
Function ID
identification for the calculation function with which the shipboard data server (3.38) performs the
calculation
3.17
hypertext transfer protocol
HTTP
communication protocol used to exchange hypertext markup language (HTML) or other contents on the
internet
3.18
hypertext transfer protocol over SSL/TLS
HTTPS
protocol in which web servers and clients encrypt data transmissions
3.19
internet control message protocol
ICMP
protocol consisting of communication rules that are used for purposes such as notifications of errors in the
processing of datagrams, and notifications of information relating to communication
Note 1 to entry: This protocol is according to RFC 792.
3.20
internet group management protocol
IGMP
protocol which is used on IPv4 networks to report multicast group memberships
Note 1 to entry: This protocol is according to RFC 1112, RFC 2236 and RFC 4604.

3.21
input parameter
variable which gives information to the calculation function which is needed to perform the calculation
3.22
java script object notation
JSON
open and text-based exchange format
Note 1 to entry: Data transmitted in JSON formats make it easy to read and write (for humans), parse and generate (for
computers).
Note 2 to entry: It is similar to eXtensible markup language (3.13).
3.23
Local Data Name
identifier for Data Channels (3.7), which is named in accordance with a Naming Rule (3.28)
Note 1 to entry: The syntax of the identification string shall be disclosed and precisely defined using the augmented
Backus-Naur form (ABNF).
Note 2 to entry: See ISO 19848:2024, 5.1.3 b).
3.24
Local ID
identification of an on-board Data Channel (3.7) locally, consisting of a Naming Rule (3.28) and a Local Data
Name (3.23)
3.25
management data
catalogues that allow access to, and interpretation of, recorded data
EXAMPLE Timestamped Data Source Information (3.11), Data Channel List (3.8) and Alias List (3.3).
3.26
malware
malicious code
software used or created to disrupt computer operation
[SOURCE: IEC 61162-460:2018, 3.23]
3.27
message queuing telemetry transport protocol
MQTT protocol
protocol for machine-to-machine (M2M)/Internet of Things (IoT) connectivity designed as an extremely
lightweight publish/subscribe messaging transport; it is also one of the streaming protocols
Note 1 to entry: It is standardized by the Advancing Open Standards for the Information Society (OASIS).
3.28
Naming Rule
set of requirements that define a naming scheme (or an identification scheme) for components and systems
on-board the ship
Note 1 to entry: See ISO 19848:2024, 5.1.3 a).
3.29
network file system
NFS
distributed file system and a protocol for distributed file systems and other protocol specifications
Note 1 to entry: This system is defined by RFC 1094, RFC 1813 and RFC 3530.

3.30
owner
specified person who can restrict editors and users
3.31
output parameter
variable which gives destinations to the calculation function to which calculation results are output
3.32
removable external data source
REDS
user removable non-network data source
®1)
EXAMPLE Compact Disc (CD), USB memory stick, Bluetooth devices
[SOURCE: IEC 61162-460:2018, 3.32]
3.33
REST API
program invocation convention for using web systems from outside, developed in accordance with the
architectural style called representational state transfer (REST)
Note 1 to entry: Resource operations are designated by HTTP (3.17) sources. Results are sent back in XML (3.13), JSON
(3.22) and other formats.
3.34
secure file transfer protocol
SFTP
protocol that uses the SSH (3.35) protocol to securely transfer files between computers
3.35
secure shell
SSH
cryptographic protocol that allows secure communications over an unsecured network
3.36
session
stateful or stateless dialogue established to exchange data between a shipboard data server (3.38) and
shipboard equipment or systems
3.37
server message block
SMB
®2)
protocol for sharing files and printers among several Windows computers in networks
3.38
shipboard data server
information hub of a ship that stores data from shipboard machinery and equipment, shares data at sea
including machine data, and sends stored data outboard
[SOURCE: ISO 19848:2024, 3.18]
3.39
syslog
standard for message logging
1) Bluetooth® is the trademark of products supplied by Bluetooth Special Interest Group. This information is given
for the convenience of users of this document and does not constitute an endorsement by ISO of the product named.
Equivalent products may be used if they can be shown to lead to the same results.
2) Windows® is the trademark of products supplied by the Microsoft Corporation. This information is given for the
convenience of users of this document and does not constitute an endorsement by ISO of the product named. Equivalent
products may be used if they can be shown to lead to the same results.

4 Abbreviated terms
AMS alarm monitoring system
BWMS ballast water management system
CSV comma-separated value
ECDIS electronic chart display and information system
FTP file transfer protocol
FTPS file transfer protocol over SSL/TLS
GNSS global navigation satellite system
HTML hypertext markup language
HTTP hypertext transfer protocol
HTTPS hypertext transfer protocol over SSL/TLS
IT Information technology
JSON java script object notation
M/E main engine
MQTT message queuing telemetry transport
NFS network file system
OPC UA open platform communications unified architecture
OT operational technology
REDS removable external data source
RFC request for comments
SFTP secure file transfer protocol
SMB server message block
SSH secure shell
SSL secure sockets layer
TCP transmission control protocol
TLS transport layer security
UDP user datagram protocol
URI uniform resource identifier
UTC coordinated universal time
UTM unified threat management
VDR voyage data recorder
XML eXtensible markup language

5 General requirements for the shipboard data server
5.1 Function and performance of the shipboard data server
5.1.1 Processing performance
5.1.1.1 General
Manufacturers supplying the shipboard data server shall specify how much data their products can process.
If the product exceeds the amount of data that can be processed, it is necessary to notify the requesting
party by returning the status code.
5.1.1.2 Input data processing performance
The shipboard data server using the request-response transport service shall process input data from a set
of 30 data samples per session, within one second, from at least five simultaneous sessions (e.g. VDR, GNSS,
alarm and monitoring systems, ballast systems and cargo systems). See Figure 1.
Figure 1 — Input data processing performance requirement

5.1.1.3 Output data processing performance
When the shipboard data server is using the request-response transport service:
— it shall be able to process the read request of a set of 30 data samples per session, from at least five
sessions simultaneously (e.g. main engine condition monitoring, weather-routing, optimum trim, remote
maintenance and performance analysis);
— the five sessions shall be processed in less than five seconds; and
— the size of the database shall meet the manufacturer’s limit.
When the shipboard data server is using the file transport service:
— it shall have a processing performance to respond to the read requests of a set of 30 data samples per
session;
— at least one session shall be processed in less than five seconds; and
— the size of database shall meet the manufacturer’s limit.
See Figure 2.
Figure 2 — Output data processing performance requirement
5.1.1.4 Streaming transport processing performance
When the shipboard data server is using the streaming transport service:
— it shall have a processing performance to input a set of 150 data samples in less than one second from at
least one session; and
— it shall have a processing performance to output a set of 150 data samples in less than one second, from at
least two sessions of a set of 150 input data samples (e.g. condition monitoring and performance analysis
system).
See Figure 3.
Figure 3 — Streaming transport processing performance requirements
5.1.2 Storage function
The shipboard data server shall be able to store input data (defined in 6.3.2) for at least 30 days.
The manufacturer shall specify, in a user or installation manual, the amount of storage space required per
record. Information on the total storage capacity within the ship data server shall also be provided.
The shipboard data server shall provide the means to assist the user in estimating if the total storage
capacity of the shipboard data server is sufficient for the required time period. In the manual or the help file,
the manufacturer shall give instructions on how to estimate the storage capacity.
NOTE The shipboard data server can have a redundant function to protect management data and actual recorded
data (e.g. redundant array of independent disks [RAID] 1, 3 and 5 systems).
5.1.3 Interface function
The shipboard data server shall be able to provide data input and output functions (see 6.3).

The shipboard data server shall have one or more ethernet interfaces where data are transmitted at 100
Mbit/s or greater.
NOTE The shipboard data server can also have other interfaces capable of serial communications or other means
of inputting data.
5.1.4 Condition monitoring function
The shipboard data server shall be able to monitor the status of the following conditions:
a) system failure of shipboard data server processor;
b) failure to access storage device;
c) failure of recording interface;
d) loss of UTC synchronization; and
e) storage device that is full or has insufficient capacity to store configured records for up to 30 days.
The shipboard data server shall be able to report the above statuses to other systems on-board (see 5.1.7)
and may provide local indications for these statuses.
5.1.5 Data backup and restoration functions
The shipboard data server shall have backup and restoration functions for:
— management data, and
— actual recorded data.
5.1.6 Function to protect against unauthorised access
The shipboard data server shall have protected settings, management data, actual recorded data and other
items from accidental and/or unauthorised access. See Clause 7.
5.1.7 Status reporting
The shipboard data server shall be provided with an interface to provide status report to the ship’s
personnel. The interface shall at least consist of one relay contact output and an indicator driven by relay,
capable of indicating normal/abnormal status of the shipboard data server to the ship’s personnel. The relay
and the indicator can be replaced by other means, as specified by the manufacturer, which allow the ship’s
personnel to identify a related failure of the shipboard data server.
For example, an alternate method to the relay and the indicator can be based on the provision of a specific
status display at the shipboard data server or on generating alerts in the shipboard data server and reporting
the alerts to other systems on-board by employing sentences ACN, ALF, ALC, ARC and HBT from IEC 61162-1.
If the shipboard data server is capable of providing the alerts to the ship’s personnel by using the above
sentences, it shall comply with IEC 62923-1 and IEC 62923-2.
When an alert occurs and a status report is made using the ALF statement, the following statement shown
in the example below will be output. If alerts in Table 1 are provided, they shall use the priority, category,
escalation and alert identifier in Table 1.
EXAMPLE $IIALF,1,1,0,223344.55,B,C,N,,3009,1,1,0, Recording failed*hh

Table 1 — Alert list
a a
Alert title Alert description text
Alert identi-
Pri Cat Escal
fier
(example) (example)
The system was stopped. Restart the system. If not
3063 System fault C B -
recovered, schedule maintenance.
No access to storage device, replace storage device
3009 Recording failed C B -
to new one.
Lost < Data
3003 Check the connection to < Data Provider > . C B -
b
Provider >
Recorded timestamp may deviate from UTC. Check
3156 Lost UTC sync C B -
c
the connection to the < Time Source > .
Recording will be stopped in 30 days. Backup old
3133 Data store low C B -
data and delete it until then.
a
The given text (as an example) may be adjusted according to the implementation.
b
< Data Provider > in the above list shall be changed according to the data provider’s name.
c
< Time Source > may be GNSS or NTP server.
Key
Pri   Priority
Cat   Category
Escal  Escalation
5.2 Environmental performance of shipboard data server
5.2.1 Power-supply performance
The shipboard data server shall satisfy the test requirements of the power supply performance specified in
IEC 60092-504.
Refer to IEC 60092-504:2016, Table 1, No.4 a), Electric of power supply variations, and No.4 b), Power supply
failure.
The shipboard data server, management data and actual recorded data shall be protected from damage,
even during temporary loss of electricity.
5.2.2 Vibration-resistant feature
The shipboard data server shall satisfy the test requirements of the vibration test specified in IEC 60092-504.
Refer to No.10, Vibration, of IEC 60092-504:2016, Table 1.
5.2.3 Requirement for electromagnetic immunity and emission
The shipboard data server shall satisfy the test requirements of the electromagnetic immunity tests
specified in IEC 60092-504. Refer to IEC 60092-504:2016, Table 1, Tests No. 13, 14, 15, 16 and 17.
The shipboard data server shall satisfy the test requirements of the electromagnetic emission tests specified
in IEC 60092-504. Refer to IEC 60092-504:2016, Table 1, Tests No. 19 and 20.
The electromagnetic immunity and emission tests shall be conducted according to the installation location.
For example, if installed on a ship bridge, the requirements of IEC 60945 shall be met. If installed in an
engine control room, the requirements of IEC 60092-504 shall be met.

5.2.4 Temperature and humidity resistant requirements
The shipboard data server shall satisfy the following requirements in IEC 60092-504:2016, Table 1:
— No.6, cold with gradual change of temperature;
— No.7, dry heat with gradual change of temperature; and
— No.8, damp heat cyclic.
Where electrical equipment is installed within environmentally controlled spaces, the ambient temperature
for which the equipment is suitable may be reduced from 45 °C and maintained at a value not less than 35 °C.
Also, according to the temperature conditions, the location of installation shall be drawn in the installation
manual.
For setting up the environmentally controlled space, refer to the following:
— the equipment shall not be used for emergency services;
— temperature control is achieved using at least two cooling units arranged so that if one of the cooling
units fails, the remaining unit(s) is capable of satisfactorily maintaining the design temperature;
— the equipment can be initially set to work safely within an ambient temperature of 45 °C until such a
time that the lesser ambient temperature may be achieved; the cooling equipment shall be rated for an
ambient temperature of 45 °C; and
— audible and visual alerts are provided, at a continually manned control station, to indicate any malfunction
of the cooling units.
5.3 Installation requirements for shipboard data server
5.3.1 Environment requirements
The manufacturer shall define the surrounding environment requirements for installing the shipboard data
server in installation manuals.
5.3.2 Requirements for maintenance areas
The manufacturer shall define the work areas that are needed for maintenance and provide details in
installation manuals.
5.3.3 Requirement for networks and network security
The shipboard data server shall be installed within networks that comply with network security related
requirements given in ISO 16425.
NOTE ISO 16425 sets network security related requirements on:
— network system design,
— network interface for shipboard equipment and systems,
— protection from malware, and
— protection from illicit access and equipment protection.

6 Data input/output and data management on shipboard data server
6.1 General
The shipboard data server shall have the following functions for data input/output and data management:
a) data management function;
b) data input and output functions;
c) alias function;
d) data calculation function;
e) log management function.
6.2 Data management function
6.2.1 General
The data management function comprises time stamping of the Data Channel List, the Data Source
Information, and the Alias List based on the system clock and administration of management data.
The shipboard data server shall accept change requests in management data only when the requests are
received f
...