ASTM F1756-97a(2002)

Standard Guide for Implementation of a Fleet Management System Network

SCOPE
1.1 This guide provides an overview and guide for the selection and implementation by shipowners and operators of a Fleet Management System (FMS) network of computer services in a client/server architecture (see Fig. 1). The FMS is based upon a wide area enterprise network consisting of an unspecified number of Shipboard Information Technology Platforms (SITPs) and one or more shoreside Land-Based Information Technology Platforms (LITPs), which provides management services for the shipping enterprise. The FMS can be understood as a computer system comprised of one or more LITPs and one or more SITPs. It can be characterized as mission critical 24 365 (24 h/day, 365 days/year).
1.2 The SITP (see Fig. 1) provides a set of software services, including:
1.2.1 Communications Services, to communicate between vessels and with shore via multiple wireless communication technologies;
1.2.2 Data Acquisition Services, providing access to shipboard system data as required for use by other systems and management purposes; and,
1.2.3 Executive Services, providing software process administration and control.
1.2.4 In total, the SITP provides the capability for multiple shipboard computer systems to share data with each other and to communicate with shore-based management or other vessels or both.
1.3 The SITP is understood to consist of integrated hardware, software, a data repository, and standardized procedures, which provide the ability to send, receive, process, transfer, and store data or messages in digital form in a common mode from shipboard systems or administrative utilities or both, and from designated sources outside the network, for example, systems accessed through wireless communication services, such as satellite, VHF, HF, and so forth. Shipboard systems include navigational, machinery control and monitoring, cargo control, communications, and so forth. The SITP also will provide the capability for the remote administration and maintenance of associated computer systems aboard the vessel.
1.4 The SITP requires an underlying hardware and network infrastructure, including a shipboard computer local area network (LAN), file servers, workstations, wireless communications transceivers, cabling, other electronic and optical devices, video display units, keyboards, and so forth.
1.5 The SITP also requires underlying system software providing network operating system (NOS) services, DBMS services, and other system software.
1.6 There also is a layer of shipboard application systems, which are designed to capitalize on the FMS infrastructure to share data with other shipboard systems and management ashore. Those systems also would be able to capitalize on the remote management capabilities of the FMS.
1.7 The LITP is an asset that can exchange operating and administrative data from individual ships and maintain a DBMS to support fleet management and other maritime applications. The LITP will support data repositories, file servers, workstations or personal computers (PCs), and a communication hub providing connectivity to distributed satellite services, VHF (very high frequency), HF/MF (high frequency/medium frequency), and land lines. The DBMS makes possible the development of knowledge-based "decision aids" by providing the ability to retrieve, process, and analyze operational data.
1.8 This guide does not purport to address all the requirements for a SITP, which forms a path for data for direct control of the operation or condition of the vessel or the vessel subsystems.
1.9 In all cases, it shall be possible for all units of navigation equipment resident on the Navigation Equipment Bus to operate and display essential operating data independently of the FMS.
1.10 In all cases, it shall be possible for all units resident on the Control, Monitoring, and Alarm Bus to operate and display essential operating data independently of the FMS.
1.11 In all cases, it shall be possible for all units resident on th...

General Information

• Status: Historical
• Publication Date: 09-Nov-1997
• ICS: 47.020.01 - General standards related to shipbuilding and marine structures
• Technical Committee: F25 - Ships and Marine Technology
• Drafting Committee: F25.05 - Computer Applications

Relations

• Replaced By: ASTM F1756-97a(2008) - Standard Guide for Implementation of a Fleet Management System Network (Withdrawn 2015)
• Effective Date: 01-May-2008
• Referred By: ASTM F2001-15(2022) - Standard Guide for Vessel-Related Technical Information for Use in Developing an Electronic Database and Ship Safety Record
• Effective Date: 10-Nov-1997

Standards Content (Sample)

NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
An American National Standard
Designation:F1756–97a (Reapproved 2002)
Standard Guide for
Implementation of a Fleet Management System Network
This standard is issued under the fixed designation F 1756; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (e) indicates an editorial change since the last revision or reapproval.
1. Scope provide the capability for the remote administration and
maintenanceofassociatedcomputersystemsaboardthevessel.
1.1 This guide provides an overview and guide for the
1.4 The SITP requires an underlying hardware and network
selection and implementation by shipowners and operators of a
infrastructure, including a shipboard computer local area net-
Fleet Management System (FMS) network of computer ser-
work (LAN), file servers, workstations, wireless communica-
vices in a client/server architecture (see Fig. 1). The FMS is
tionstransceivers,cabling,otherelectronicandopticaldevices,
based upon a wide area enterprise network consisting of an
video display units, keyboards, and so forth.
unspecified number of Shipboard Information Technology
1.5 The SITP also requires underlying system software
Platforms (SITPs) and one or more shoreside Land-Based
providing network operating system (NOS) services, DBMS
Information Technology Platforms (LITPs), which provides
services, and other system software.
management services for the shipping enterprise.The FMS can
1.6 There also is a layer of shipboard application systems,
be understood as a computer system comprised of one or more
which are designed to capitalize on the FMS infrastructure to
LITPs and one or more SITPs. It can be characterized as
share data with other shipboard systems and management
mission critical 24 3 365 (24 h/day, 365 days/year).
ashore. Those systems also would be able to capitalize on the
1.2 The SITP (see Fig. 1) provides a set of software
remote management capabilities of the FMS.
services, including:
1.7 The LITP is an asset that can exchange operating and
1.2.1 Communications Services, to communicate between
administrative data from individual ships and maintain a
vessels and with shore via multiple wireless communication
DBMS to support fleet management and other maritime
technologies;
applications. The LITP will support data repositories, file
1.2.2 Data Acquisition Services, providing access to ship-
servers, workstations or personal computers (PCs), and a
board system data as required for use by other systems and
communication hub providing connectivity to distributed sat-
management purposes; and,
ellite services, VHF (very high frequency), HF/MF (high
1.2.3 ExecutiveServices,providingsoftwareprocessadmin-
frequency/medium frequency), and land lines. The DBMS
istration and control.
makespossiblethedevelopmentofknowledge-based“decision
1.2.4 In total, the SITP provides the capability for multiple
aids” by providing the ability to retrieve, process, and analyze
shipboard computer systems to share data with each other and
operational data.
tocommunicatewithshore-basedmanagementorothervessels
1.8 This guide does not purport to address all the require-
or both.
ments for a SITP, which forms a path for data for direct control
1.3 The SITP is understood to consist of integrated hard-
of the operation or condition of the vessel or the vessel
ware, software, a data repository, and standardized procedures,
subsystems.
which provide the ability to send, receive, process, transfer,
1.9 Inallcases,itshallbepossibleforallunitsofnavigation
and store data or messages in digital form in a common mode
equipment resident on the Navigation Equipment Bus to
from shipboard systems or administrative utilities or both, and
operate and display essential operating data independently of
from designated sources outside the network, for example,
the FMS.
systems accessed through wireless communication services,
1.10 In all cases, it shall be possible for all units resident on
such as satellite, VHF, HF, and so forth. Shipboard systems
the Control, Monitoring, andAlarm Bus to operate and display
include navigational, machinery control and monitoring, cargo
essential operating data independently of the FMS.
control, communications, and so forth. The SITP also will
1.11 In all cases, it shall be possible for all units resident on
the Communications Bus to operate and display essential
This guide is under the jurisdiction of ASTM Committee F25 on Ships and
operating data independently of the FMS.
Marine Technology and is the direct responsibility of F25.05 on Computer
1.12 Values shown in this guide are in SI units.
Applications.
Current edition approved Nov. 10, 1997. Published October 1998. Originally
published as F 1756 - 97. Last previous edition F 1756 - 97.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
F1756–97a (2002)
FIG. 1 Typical Architecture
1.13 This standard does not purport to address all of the IEEE 802 Standards for Local and Metropolitan Area
safety concerns, if any, associated with its use. It is the Networks—Overview and Architecture
responsibility of the user of this standard to establish appro-
IEEE 802 Standards for Local and Metropolitan Area
priate safety and health practices and determine the applica-
Networks—Interoperable LAN/MAN Security
bility of regulatory limitations prior to use.
IEEE 802.10e and 10f Supplements to IEEE 802.10
IEEE 1003
2. Referenced Documents
IEEE 1063 Standard for Software User Documentation
2.1 ASTM Standards:
2.4 IEC Documents:
E 919 Specification for Software Documentation for a
2 IEC 50 International Electrotechnical Vocabulary (IEV)
Computerized System
IEC 92–504 Electrical Installations in Ships; Special Fea-
E 1013 Terminology Relating to Computerized Systems
tures–Control and Instrumentation
F 1166 Practice for Human Engineering Design for Marine
Systems, Equipment, and Facilities IEC 533 Electromagnetic Compatability of Electrical and
F 1757 Guide for Digital Communication Protocols for Electronic Installations in Ships and of Mobile and Fixed
Computerized Systems Offshore Units
2.2 ANSI Standards:
IEC 945 Maritime Navigation and Radiocommunication
X3.172 Dictionary for Information Systems
Equipment and Systems
X3.172a Dictionary for Information Systems (Computer
IEC 1069 Industrial–Process Measurement and Control—
Security Glossary)
Evaluation of System Properties for the Purpose of Sys-
2.3 IEEE Standards:
tem Assessment, Part 1: General Considerations and
IEEE 1028–1988(R1993) Standard for Software Review
Methodology; Part 2: Assessment Methodology
and Audit
IEC 1162 Maritime Navigation and Radiocommunication
IEEE 1012–1986(1992) Standard for Verification and Vali-
Equipment and Systems—Digital Interfaces
dation Plans
IEC 1209 Integrated Bridge Systems (IBS) for Ships
IEEE 45 Recommended Practice for Electrical Installations
2.5 NMEA(National Marine ElectronicsAssociation) Stan-
on Shipboard
dard:
NMEA 0183 Standard for Interfacing Electronic Marine
Navigational Devices
Annual Book of ASTM Standards, Vol 14.01.
Annual Book of ASTM Standards, Vol 01.07.
Available fromAmerican National Standards Institute (ANSI), 25 W. 43rd St.,
4th Floor, New York, NY 10036.
5 6
Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE), Available from the National Marine Electronics Association (NMEA) Seven
445 Hoes Ln., P.O. Box 1331, Piscataway, NJ 08854–1331. Riggs Ave., Severna Park, MD 21146.
F1756–97a (2002)
3. Terminology 3.1.16 independent, n—independent as applied to two sys-
tems means that either system will operate with the failure of
3.1 Definitions: Definitions of terms in this guide and
any part of the other system excluding the source of power.
described below are in accordance with Terminology E 1013
3.1.17 interface, n—the interface attribute describes the
and ANSI X3.172 and X3.172a.
methods and rules governing interaction between different
3.1.1 application program, n—a computer program that
entities.
performs a task related to the process being controlled rather
3.1.18 integration tests, n—tests performed during the
than to the functioning of the computer itself.
hardware/software integration process before computer system
3.1.2 application programming interface (API), n—an API
validation to verify compatibility.
is a set of rules for linking various software components of a
3.1.19 land-based communications hub, n—a land-based
network.
computer system that provides uniform access to multiple
3.1.3 automatic information system (AIS), n—automatic
maritime satellite services, as well as access to public tele-
distribution of a ship’s voyage information to all interested
phone networks, e-mail, and the internet.
parties, that is, other ships, port state, owner, and so forth.
3.1.20 local area network (LAN), n—a network that con-
3.1.4 baseband network, n—only one transmission can be
nects computer systems resident in a small area. For purposes
on the network at any given time.
of this guide, the SITP is considered a shipboard LAN with
3.1.5 black box test, n—black box tests are based on the
access to similar shoreside and shipboard units through radio
design specification and do not require a knowledge of the
and satellite telecommunication services.
internal program structure.
3.1.21 MSAT—satellite communications service covering
3.1.6 certification, n—the process of formal approval, by an
North America
authority empowered to do so, of arrangements or systems for
3.1.22 multitasking, n—the capability to handle more than
the reception, storage, or transmission of data and intelligence
one task at a time
relative to the management, operation, or control of vessels.
3.1.23 NAVTEX, n—a system for the broadcast and auto-
3.1.7 client server database engine, n—a commercial data
matic reception of maritime safety information by means of a
base management system serving as a repository for all critical
narrow-band direct-printing telegraphy.
ship operating and configuration information.
3.1.24 network interface unit (NIU), n—the network inter-
3.1.8 computer program, n—a set of ordered instructions
face units (NIUs) provide for connection and message transla-
that specify operations in a form suitable for execution by a
tion to enable data streams from systems, both hardware and
digital computer.
software, which may use various standard and proprietary
3.1.9 computer system, n—a functional unit, consisting of
communicationprotocolstobestoredandaccessedintheFMS
one or more computers and associated software, that uses
database in a standard format.
common storage for all or part of a program and also for all or
3.1.25 ship information technology platform (computing),
part of the data necessary for the execution of the program.
n—an integrated system of software, hardware, communica-
3.1.10 configuration manager, n—utilities that determine
tion links, and standardized procedures that provide the ability
the data to be collected, the processing and storage rules, the
to collect, process, and store information in digital form.
standard software functions that facilitate the interfaces be-
3.1.26 ship earth station, n—a mobile earth station for
tween systems and the FMS process servers and other configu-
maritime service located aboard a ship. Typically, a small
ration parameters.
lightweight terminal with omnidirectional antenna with inter-
3.1.11 data replicator/message processor, n—a software
faces for a personal computer or any other data terminal
module that is responsible for receiving, decoding, and storing
equipment for message generation and display, for example,
communications and transmissions received from ships. This
Inmarsat C, or a steerable antenna mounted on a stabilized
module also prepares data for transmission to a ship through
platform, for example, Inmarsat A and B and M.
the land-based communications hub.
3.1.27 single failure criterion, n—a criterion applied to a
3.1.12 document management system, n—an application
system such that it is capable of performing its safety task in
that allows procedures manuals to be stored and accessed
the presence of any single failure.
electronically on shipboard and to be updated electronically.
3.1.28 software, n—programs, procedures, rules, and asso-
3.1.13 electronic mail system, n—a messaging and file
ciated documentation pertaining to the operation of a computer
transfer system for both ship and shore.
system.
3.1.14 fault tolerance, n—the built-in capacity of a system
3.1.29 software cycle—thesoftwarecycletypicallyincludes
to provide continued correct execution in the presence of a
a requirements phase, a design phase, an implementation
limited number of hardware of software faults.
phase, a test phase, an installation and checkout phase, and an
3.1.15 fleet management system (FMS), n—a system of
operation and maintenance phase.
computer services in a client/server architecture, based on a
3.1.30 validation—the test and evaluation of the integrated
wide area enterprise network consisting of an unspecified
number of SITPs and the LITP.The FMS can be understood as computersystem,hardwareandsoftware,toensurecompliance
with the functional, performance, and interface requirements.
a computer system comprised of one or many shipboard
systems and one of many shoreside systems. It can be 3.1.31 verification, n—the process to determine if the prod-
characterized as mission critical 24 3 365 (24 h/day, 365 uct of each phase of the digital computer system development
days/year). process satisfies the requirements set by the previous phase.
F1756–97a (2002)
3.1.32 voyage data recorder (VDR), n—a store of informa- or receiving information in the form of electronic or optical
tion, in a secure and retrievable form, concerning the position, signals. The process is enabled by communication protocols,
movement, physical status, command, and control of a vessel which define the rules that must be implemented in the
over the period leading up to a marine casualty. hardware and software. The text of this guide is predicated on
3.1.33 white box test, n—white box tests require a knowl- a network architecture conforming to the Open Systems
edge of the internal program structure and are based on the Interconnection Reference Model (OSI/RM). See Guide
internal design specification. F 1757.
3.1.34 workstation, n—a computer and associated visual 5.2 Network Management:
display unit (monitor) configured as an I/O unit to perform 5.2.1 The FMS is based upon a wi
...