ISO 15849:2001/Amd 1:2003
Standards Content (sample)
Ships and marine technology —
Guidelines for implementation of a fleet
management system network
AMENDMENT 1: Annex A
Navires et technologie maritime — Lignes directrices pour la mise en
œuvre d'un système de management d'une flotte par réseau
AMENDEMENT 1: Annexe A
---------------------- Page: 1 ----------------------
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 Secretariataccepts 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 2003
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 orISO'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
Published in Switzerland
ii © ISO 2003 — All rights reserved
---------------------- Page: 2 ----------------------
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 2.
The main task of technical committees is to prepare International Standards. 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 document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
Amendment 1 to ISO 15849:2001 was prepared by Technical Committee ISO/TC 8, Ships and marinetechnology, Subcommittee SC 10, Computer applications.
© ISO 2003 — All rights reserved iii
---------------------- Page: 3 ----------------------
Annex A indicates an example of the specifications for the design of the software of the Application Program
Interface (API) when it is applied to the SITP and the LITP, as required by the main text of ISO 15849
(Guidelines for the Fleet Management System Network, FMSN) to secure the effective execution of the mutualconnectivity with transparency.
iv © ISO 2003 — All rights reserved
---------------------- Page: 4 ----------------------
Ships and marine technology — Guidelines for implementation
of a fleet management system network
AMENDMENT 1: Annex A
© ISO 2003 — All rights reserved 1
---------------------- Page: 5 ----------------------
Example of specifications for the design of the software of the
Application Program Interface (API) when it is applied to the SITP and
The scope of this Annex is the software design guide for the purpose of applying the API for the functions ofthe SITP and the LITP that are specified in the main text of ISO 15849.
In this Annex, the concept is based on the use of CORBA (A.2.3) as the specification of a distributed object fora model.
A.2 Terms and definitions
For the purposes of this Annex, the following terms and definitions apply.
acquire data list
operation of acquiring the data list from the database, on the specified server
acquire ship information
polling operation from the specified server
Common Object Request Broker Architecture
standard of distributed object model as defined by the Object Management Group
station which became independent of the LITP-installed system and the SITP-installed system, when adatabase is arranged on this station
Interface Definition Language
language to define interface in each operation
NOTE CORBA's primary tool to insulate language.
when CORBA is used and the client and server communicate, a program (as a part of API) on the server sideto provide an application program to start the operation directly
2 © ISO 2003 — All rights reserved
---------------------- Page: 6 ----------------------
when CORBA is used and the client and server communicate, the client program that accesses the operation
on the server side provided with the corresponding pseudo-object (as a part of API) on the client sideA.2.8
common reference service provided by CORBA
NOTE The naming service responds to the inquiry from the object, relating the name of the object to its location inthe network.
naming service interface
program, which executes the API request from the user application, in the series of processes when a namingservice is used
Object Management Group
international standardization group which prescribes technology for the infrastructure which is necessary for
the development of the application in the environment of the dispersion of object oriented architecture andindependent of the hardware
Object Request Broker
software which provides the tasks of communication between stub and skeleton
operation of reading one particular datum from the database, on the specified serverA.2.13
program, which is established by the user of the FMSN in accordance with the requirement by theLITP-installed system to realize the functionality on the FMSN
NOTE The functionality on the FMSN serves to acquire the operational management information and/or the shipmanagement information.
interface in the API opened between the API and user application
NOTE This also defines four kinds of operation (Read data, Write data, Acquire data list and Acquire shipinformation) as described in the A.4.1.2 to A.4.3.2.
operation of writing one particular datum to the dat