Ships and marine technology — Guidelines for implementation of a fleet management system network

This International Standard provides an overview and guide for the selection and implementation by shipowners and operators of a fleet management system (FMS) network of computer services. This includes a) guidelines for the general infrastructure, including wide area network, data transmission services and common database facilities, b) guidelines for the shipboard installations, including services to application programs, and c) guidelines for land-based installations, including services to application programs. This International Standard does not purport to address the requirements for safety-related systems, e.g. navigation, radio communication as well as systems used to control the operation of the ship. This International Standard does not purport to address any of the environmental considerations associated with the use of the fleet management system.

Navires et technologie maritime — Lignes directrices pour la mise en oeuvre d'un système de management d'une flotte par réseau

General Information

Status
Published
Publication Date
31-Oct-2001
Current Stage
9093 - International Standard confirmed
Completion Date
20-Aug-2022
Ref Project

Relations

Buy Standard

Standard
ISO 15849:2001 - Ships and marine technology -- Guidelines for implementation of a fleet management system network
English language
19 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 15849
First edition
2001-11-01
Ships and marine technology — Guidelines
for implementation of a fleet management
system network
Navires et technologie maritime — Lignes directrices pour la mise en
oeuvre d'un système de management d'une flotte par réseau

Reference number
ISO 15849:2001(E)
©
ISO 2001

---------------------- Page: 1 ----------------------
ISO 15849:2001(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be
edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file,
parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2001
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's
member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
©
ii ISO 2001 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 15849:2001(E)
Contents Page
1 Scope . 1
2 Terms and definitions . 1
3 Abbreviated terms . 3
4 FMS network architecture . 3
4.1 General architecture . 3
4.2 Network design . 4
4.3 Network management . 4
4.4 Network security . 5
4.5 Encryption . 5
4.6 Database model . 5
4.7 Database management system (DBMS) . 5
5 Shipboard information technology platform (SITP) . 6
5.1 Introduction . 6
5.2 The SITP data acquisition service . 6
5.3 SITP executive services . 7
5.4 Communications services . 10
5.5 SITP underlying system service . 11
6 Land-based information technology platform (LITP) . 12
6.1 General . 12
6.2 Data acquisition services . 12
6.3 Executive services . 12
6.4 Communications manager . 12
6.5 Configuration manager . 12
7 Application program interfaces (APIs) . 12
7.1 Introduction . 12
7.2 Overview of APIs . 12
7.3 API applications . 13
7.4 API levels of implementation . 13
8 System hardware . 14
8.1 System hardware . 14
8.2 Communications bus . 14
9 Fault tolerance . 14
9.1 Fault tolerance . 14
9.2 Robustness . 14
10 Demonstration and validation . 15
10.1 General . 15
10.2 Test philosophy . 15
10.3 System hardware test . 15
10.4 LAN software assessment . 15
©
ISO 2001 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 15849:2001(E)
10.5 Tests and trials . 15
11 Quality plan . 16
11.1 General . 16
11.2 Design and testing of the computer services . 16
12 Operation and maintenance . 17
13 Human interface . 17
13.1 General . 17
13.2 Visual display unit (VDU) . 17
13.3 Screen image paging . 17
14 Training and documentation . 17
14.1 General . 17
14.2 Documentation . 18
Bibliography. 19
©
iv ISO 2001 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 15849:2001(E)
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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
Draft International Standards adopted by the technical committees are circulated to the member bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this International Standard may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
International Standard ISO 15849 was prepared by Technical Committee ISO/TC 8, Ships and marine technology,
Subcommittee SC 10, Computer applications.
©
ISO 2001 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO 15849:2001(E)
Introduction
Competent information management is essential for safe and productive operation of ships and for regulatory
compliance. A short list of some of the functions affected includes decision aids for communications, cargo
operations, maintenance and repair, personnel records and environmental protection.
The shipbuilding and shipping industries have identified a need to develop comprehensive standards and guides for
implementing computer-based shipboard data-management systems.
It is the intent of this International Standard to provide guidelines for the design and implementation of an open
client/server architecture for computer and communication networks for shipboard and shore-based applications, as
well as guidelines to application software providers to allow ready integration of software applications.
Furthermore, it is the intent of this International Standard to provide guidelines that will promote and enable remote
support of the shipboard data systems/networks from support offices ashore.
This International Standard is also intended to assist vessel owners, designers, shipyards, equipment suppliers and
computer service providers in the development of contract technical specifications which detail the services to be
supported, performance required and criteria for acceptance for specific installations.
©
vi ISO 2001 – All rights reserved

---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 15849:2001(E)
Ships and marine technology — Guidelines for implementation of a
fleet management system network
1 Scope
This International Standard provides an overview and guide for the selection and implementation by shipowners and
operators of a fleet management system (FMS) network of computer services. This includes
a) guidelines for the general infrastructure, including wide area network, data transmission services and common
database facilities,
b) guidelines for the shipboard installations, including services to application programs, and
c) guidelines for land-based installations, including services to application programs.
This International Standard does not purport to address the requirements for safety-related systems, e.g. navigation,
radio communication as well as systems used to control the operation of the ship.
This International Standard does not purport to address any of the environmental considerations associated with the
use of the fleet management system.
2 Terms and definitions
For the purposes of this International Standard, the following terms and definitions apply.
2.1
application program
computer program that performs a task related to the process being controlled rather than to the functioning of the
computer itself
2.2
application program interface
API
software tool kit that can be used as a building block that facilitates connections primarily between applications and
other constituent network software, but that can also provide linkages for other elements of the network
2.3
black box test
test that is based on the design application and does not require a knowledge of the internal program structure
2.4
certification
process of formal approval, by an authority empowered to do so, of arrangements or systems for the reception,
storage or transmission of data and intelligence relative to the management, operation or control of vessels
2.5
client/server database engine
commercial database management system serving as a repository for all critical ship operating and configuration
information
©
ISO 2001 – All rights reserved 1

---------------------- Page: 7 ----------------------
ISO 15849:2001(E)
2.6
client/server architecture
architecture of computers called servers that manage shared resources and provide access to those shared
resources as a service to their clients
2.7
computer system
functional unit, consisting of one or more computers and associated software, that uses common storage for all or
part of a program and also for all or part of the data necessary for the execution of the program
2.8
fault tolerance
built-in capacity of a system to provide continued correct execution in the presence of a limited number of hardware
or software faults
2.9
independent
independent, as applied to two systems, means that either system will operate with the failure of any part of the other
system
2.10
interface
interface attribute describes the methods and rules governing interaction between different entities
2.11
land-based communications hub
land-based computer system that provides uniform access to multiple maritime satellite services, as well as access
to public telephone networks, e-mail and the Internet
2.12
ship earth station
mobile earth station for maritime satellite service located aboard a ship
2.13
software
programs, procedures, rules and associated documentation pertaining to the operation of a computer system
2.14
validation
test and evaluation of an integrated computer system (hardware and software) to ensure compliance with the
functional, performance and interface requirements
2.15
ship information technology platform
SITP
integrated system of software, hardware, communication links and standardized procedures that provide common
services to shipboard systems in a standardized form
2.16
verification
process to determine if the product of each phase of the digital computer system development process satisfies the
requirements set by the previous phase
2.17
white box test
test where the test plan is based on knowledge of the internal structure of the module being tested
See black box test (2.3)
©
2 ISO 2001 – All rights reserved

---------------------- Page: 8 ----------------------
ISO 15849:2001(E)
2.18
workstation
computer and associated visual display unit (monitor) configured as an input/output (I/O) device to perform certain
tasks
3 Abbreviated terms
For the purposes of this International Standard, the following abbreviated terms apply.
ANSI American National Standards Institute
API application program interface
CCITT Consultative Committee for International Telegraphy and Telephony
DAC discretionary access control
DBMS data base management system
FMS fleet management system
FMSN fleet management system network
IBS integrated bridge systems
IEV International Electrotechnical Vocabulary
LAN local area network
NOS network operation system
LITP land-based information technology platform
NMEA National Marine Electronics Association
SITP shipboard information technology platform
STEP standard for the exchange of product data (ISO)
VDU visual display unit
WAN wide area network
4 FMS network architecture
4.1 General architecture
The FMS architecture is shown schematically in Figure 1. The FMS is based upon a wide-area enterprise network,
consisting of an unspecified number of SITPs and one or more shoreside LITPs which provides management
services for the shipping enterprise. In total, the SITP enables multiple shipboard computer systems to share data
with each other and to communicate with shore-based management and/or other vessels.
©
ISO 2001 – All rights reserved 3

---------------------- Page: 9 ----------------------
ISO 15849:2001(E)
Figure 1 — Schematic of SITP / LITP connectivity
The FMS provides multi-vendor connectivity, distributed processing and electronic data interchange between
networks, computers, workstations and peripherals. It also maintains databases and computer applications software
that promote safety of life at sea, protection of the environment and operational efficiencies throughout the life cycle
of the vessel/fleet. The FMS may incorporate satellite gateways to coastal communications hubs providing access to
land-based networks such as telephone lines, facsimile, e-mail Internet services, and expanded satellite services
through land-earth stations.
4.2 Network design
An underlying computer network is assumed to support the FMS. The functions of the FMS enable a communication
network that provides for the exchange of information between nodes or devices capable of transmitting or receiving
information in the form of electronic or optical signals. The process is enabled by communications protocols, which
define the rules that must be implemented in the hardware and software.
4.3 Network management
The FMS is based upon a WAN consisting of a number of LAN which are geographically dispersed over large areas
and which are continuously or intermittently linked through wireless communications by bridges and gateway
devices. The group responsible for managing the FMS will normally be located in the principle shoreside office. The
©
4 ISO 2001 – All rights reserved

---------------------- Page: 10 ----------------------
ISO 15849:2001(E)
primary task of the network management system is to oversee and report on the operation of the network, which may
comprise products from many different vendors.
It is the responsibility of the user of this International Standard to establish appropriate safety and health and
environmental practices and to determine the applicability of the various regulatory instruments.
4.4 Network security
A security function should be provided which is responsible for the following:
a) data confidentiality;
b) data integrity;
c) data authentication;
d) access control.
4.5 Encryption
Radio communications between SITPs and LITPs are exposed to electronic monitoring, and messages transmitted
in clear text will be exposed to eavesdropping and intrusion. Data encryption is the most effective protection against
such intrusions and should be available for security sensitive communications. The encryption protocol should
provide for multiple algorithms and the assignment of separate algorithms for different types of data. A critical
element of the encryption program is the control of data encyphering and data decyphering keys (a key management
system). This system is responsible for key origination, application, recording, assignment and deletion.
4.6 Database model
Database maintenance and availability are key features of the FMS. Each SITP and LITP will maintain separate
databases. Each site will incorporate a DBMS, including replication capability, as part of the SITP or LITP installation.
This DBMS should be independent of the core management software. Data modelling embraces the concept that
data should be structured in a neutral format separate from the applications software allowing for the exchange of
data between applications using the same data model.
4.7 Database management system (DBMS)
4.7.1 General
The database management system supports a data repository that provides for storage of data in digital form and
manages
a) persistent storage of data collected by the system,
b) data replication on demand, scheduled or event driven,
c) integration of information at multiple remote sites,
d) open database connectivity,
e) query language,
f) concurrency/multiple users,
g) referential integrity, and
h) translators for applicable data models.
©
ISO 2001 – All rights reserved 5

---------------------- Page: 11 ----------------------
ISO 15849:2001(E)
4.7.2 Database security
The DBMS should incorporate protection against
— improper access,
— improper modification of data (ensure data integrity), and
— improper denial of access;
It should provide for the following features.
a) Operational integrity. This addresses the serialization and isolation properties of transactions. Serialization
means that the concurrent run of a set of transactions will give identical results as a sequential run of the same
set of transactions.
b) Logical integrity of data – allowed range.
c) Accountability and auditing – record of all read or write access to data.
d) Privacy – control of employment, medical records, etc.
e) Delimitation – control of information transfer between programs.
5 Shipboard information technology platform (SITP)
5.1 Introduction
The SITP consists of the software and hardware required to support a distributed computing network based on the
client/server model. In general, the SITP will be optimized to respond to a single LITP. For cases where the SITP will
respond to multiple shoreside platforms, a hierarchy should be defined. The SITP consists of layers of computer
services and underlying layers of system services, including a NOS and a DBMS.
5.2 The SITP data acquisition service
The SITP data acquisition service is responsible for communicating with the various shipboard control systems or
data collection units in order to acquire operating data. The SITP data acquisition is responsible for the orderly
registration, control, audit and monitoring of SITP-compliant software processes on the server and supported
workstations for data acquisition. The SITP data acquisition should provide a framework in which custom interfaces
can be developed to a variety of control systems and data acquisition units. Data from the control systems should be
stored in the SITP database and be available for analysis and diagnostic applications software on the network. This
data can also be transmitted to shore-based monitoring services through the communications network using
gateways to provide one-way communications where required for control system isolation. A key objective of the
SITP is to facilitate sharing of data among shipboard systems.
The SITP data acquisition service allows the shipboard fleet management systems to acquire information from
sensors or databases in protected systems, e.g navigation and control systems. As the protected systems are critical
for the safety of the ship, access to these systems should normally be through a firewall that can guarantee the
integrity of the protected systems. The firewall will normally be considered as part of the protected systems and,
hence, need to comply with appropriate class and regulatory requirements. These requirements are not addressed
by this International Standard.
It shall be possible to manually input any shipboard information, which is required for the purpose of fleet
management, and is not available directly from other systems.
©
6 ISO 2001 – All rights reserved

---------------------- Page: 12 ----------------------
ISO 15849:2001(E)
5.3 SITP executive services
5.3.1 General
The standard SITP executive services, as indicated in Figure 2, are required in order to provide overall command and
control of the SITP. The SITP executive has overall responsibility to monitor the SITP and control the distributed
processes that operate as platform services. The SITP executive itself is a series of services, each of which are
responsible for specific tasks. The SITP provides a layer of insulation and control between high and low level
processes. It utilizes a set of structured APIs and internal communication channels for message exchange.
The following sections describe the services that may be provided by the SITP executive. These services are each
responsible for the orderly registration, control, audit and monitoring of SITP-compliant software processes on the
server and supported workstations for their specific function. All management data recorded through an SITP
executive process is available to any other SITP-compliant process.
Figure 2 — SITP architecture
5.3.2 Process management
Process management refers to starting, staging, pausing, resuming and stopping a process. An SITP process may
be an SITP internal process, network operating system process, or an SITP-compliant application. The process
management interfaces with the SITP-compliant process through the SITP APIs and with the process management
database. Each physical computer within the SITP will have a process management function. All SITP processes are
registered in the process management database that describes the important attributes of the process. All process
management information is available to SITP applications.
5.3.3 Messaging management
The SITP messaging management interfaces with an SITP-compliant process through the SITP API for applications
to transport data among all registered entities on the SITP WAN. This will allow applications to send and receive
arbitrary data to and from any other SITP application. This includes ship to shore, ship to ship and shore to ship. The
messaging management should allow for orderly classification of communication endpoints. The messaging
management will use communications facilities as a transport mechanism for inter-application messages. The
communication abstraction provided by the messaging management allows for additional transport mechanisms to
be used in the future.
©
ISO 2001 – All rights reserved 7

---------------------- Page: 13 ----------------------
ISO 15849:2001(E)
5.3.4 Replication management
The SITP replication management uses a generalized mechanism that allows SITP application providers to build
distributed applications that operate within the SITP environment. This service may also be provided through the
database software. The services provided include the following.
a) Rules-based distribution
Configurable distribution of transactions, at the table-level, between ship and shore-based system sites. SITP
can be configured to send all, or selected subsets of, information between system sites at flexible intervals.
Furthermore, a redistribution feature allows transactions to be forwarded to multiple sites based on system
configuration parameters.
b) Distribution control mechanisms
To maintain data integrity, strong control mechanisms are required to serialize, log and archive all incoming and
outgoing transmissions. Disaster recovery mechanisms are required to re-send failed transmissions, or allow
complete refresh synchronization between system sites. Confirmation of sent and received transmissions must
be passed between system sites to ensure data integrity.
c) Batched distribution
As sustained real-time connections between system sites can be costly, the platform will support batched groups
of transactions to be transmitted in compressed packets.
5.3.5 Logging management
The logging manag
...

Questions, Comments and Discussion

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