Standard Classification for Hierarchy of Equipment Identifiers and Boundaries for Reliability, Availability, and Maintainability (RAM) Performance Data Exchange

SIGNIFICANCE AND USE
Capturing high quality Reliability, Availability, and Maintainability (RAM) performance data requires careful and consistent collection of equipment failure and repair data, operating hours, and repair time. A standard hierarchy of equipment boundaries has been needed for machinery data exchange among the stakeholders in shipbuilding, ship classification, and ship operations.
Industry and government will use a world standard method for setting the hierarchy of indentures and boundaries required for assigning failure and repair events to equipment for the tracking and calculation of equipment RAM performance.
Agreed boundaries and equipment identifiers make it possible to share equipment data among organizations, benchmark equipment performance, perform modeling and simulation of current and proposed systems, or use performance data to improve operations of commercial and Naval vessels.
RAM analysis is primarily based on the observation of individual components among which identical items contribute to the same data sample. This classification is designed to be used for the identification of individual (unique) components in such a way that identical components can be identified within a given data sample.
SCOPE
1.1 This classification is to serve as an international standard for marine equipment nomenclature, taxonomy, hierarchical data structure, unique identifiers, and boundary definition for the consistent acquisition and exchange of equipment RAM performance data. The standard addresses the classification of mechanical and software products.
1.2 RAM in an acronym for Reliability, Availability, & Maintainability where:
1.2.1 Reliability is the probability that an item can perform a required function under given conditions for a given time interval (t1, t2). It is generally assumed that the item is in a state to perform this required function at the beginning of the time interval.
1.2.2 Availability is the probability that an item is in a state to perform a required function under given conditions at a given instant of time, assuming that the required external resources are provided.
1.2.3 Maintainability is the probability that a given active maintenance action, for an item under given conditions of use can be carried out within a stated time interval, when the maintenance is performed under stated conditions and using stated procedures and resources.
1.3 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory requirements prior to use.

General Information

Status
Historical
Publication Date
30-Apr-2010
Current Stage
Ref Project

Relations

Buy Standard

Standard
ASTM F2446-04(2010) - Standard Classification for Hierarchy of Equipment Identifiers and Boundaries for Reliability, Availability, and Maintainability (RAM) Performance Data Exchange
English language
23 pages
sale 15% off
Preview
sale 15% off
Preview

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
Designation:F2446 −04 (Reapproved 2010) An American National Standard
Standard Classification for
Hierarchy of Equipment Identifiers and Boundaries for
Reliability, Availability, and Maintainability (RAM)
Performance Data Exchange
This standard is issued under the fixed designation F2446; 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 (´) indicates an editorial change since the last revision or reapproval.
1. Scope mendations issued by the World Trade Organization Technical
Barriers to Trade (TBT) Committee.
1.1 This classification is to serve as an international stan-
dard for marine equipment nomenclature, taxonomy, hierarchi-
2. Referenced Documents
cal data structure, unique identifiers, and boundary definition
2.1 ISO Standards:
fortheconsistentacquisitionandexchangeofequipmentRAM
ISO 3166-1:1997 Codes for the Representation of Names of
performance data. The standard addresses the classification of
Countries and Their Subdivisions — Part 1: Country
mechanical and software products.
Codes, 1997
1.2 RAM in an acronym for Reliability, Availability, &
ISO 10303 Industrial Automation Systems and Integration
Maintainability where:
— Product Data Representation and Exchange
1.2.1 Reliability is the probability that an item can perform
ISO 13584 Industrial Automation Systems and Integration
a required function under given conditions for a given time
— Parts Library
interval (t1, t2). It is generally assumed that the item is in a
ISO/IEC TR 12182 Information Technology — Categoriza-
state to perform this required function at the beginning of the
tion of Software, Technical Report, 1998
time interval.
ISO/TC 67/WG 4 ISO/FDIS 14224:1998(E), Petroleum and
1.2.2 Availability is the probability that an item is in a state
Natural Gas Industries — Collection and Exchange of
to perform a required function under given conditions at a
Reliability and Maintenance Data for Equipment, 1998
given instant of time, assuming that the required external
2.2 Other Standards:
resources are provided.
CenterforChemicalProcessSafetyoftheAmericanInstitute
1.2.3 Maintainability is the probability that a given active
of Chemical Engineers Guidelines for Improving Plant
maintenance action, for an item under given conditions of use 3
Reliability through Data Collection and Analysis, 1998
can be carried out within a stated time interval, when the
IEC 60050-191 International Electrotechnical Vocabulary,
maintenance is performed under stated conditions and using 4
Chapter 191, Dependability and Quality of Service
stated procedures and resources.
International Maritime Organization (IMO) Circular letter
1.3 This standard does not purport to address all of the
No. 1886/Rev. 2 Implementation of Resolution
safety concerns, if any, associated with its use. It is the
A.600(15)—IMO Ship Identification Number Scheme,
responsibility of the user of this standard to establish appro-
priate safety, health, and environmental practices and deter-
Naval Sea Systems Command Expanded Ship Work Break-
mine the applicability of regulatory limitations prior to use.
down Structure (ESWBS) for All Ships and Ship/Combat
1.4 This international standard was developed in accor-
Systems, Volumes 1 and 2, 1985
dance with internationally recognized principles on standard-
ization established in the Decision on Principles for the
Available from International Organization for Standardization (ISO), 1, ch. de
Development of International Standards, Guides and Recom-
la Voie-Creuse, Case postale 56, CH-1211, Geneva 20, Switzerland, http://
www.iso.ch.
Available from American Institute of Chemical Engineers, 3 Park Ave, New
York, N.Y. 10016-5991.
1 4
This classification is under the jurisdiction ofASTM Committee F25 on Ships Available from International Electrotechnical Commission (IEC), 3 rue de
and Marine Technology and is the direct responsibility of Subcommittee F25.05 on Varembé, Case postale 131, CH-1211, Geneva 20, Switzerland, http://www.iec.ch.
Computer Applications. Available from International Maritime Organization (IMO), 4 Albert
Current edition approved May 1, 2010. Published June 2010. Originally Embankment, London, SE1 7SR, U. K.
approved in 2004. Last previous edition approved in 2004 as F2446 – 04. DOI: Available from Naval Sea Systems Command, 1333 Isaac Hull Avenue, S. E.
10.1520/F2446-04R10. Washington Navy Yard, Washington D.C. 20376.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
F2446−04 (2010)
3. Terminology 3.1.9.3 location ID—when multiple identical components
arelocatedonthesamesite,thelocationIDidentifiesaspecific
3.1 Definitions:
piece of equipment within the site. Examples of location IDs
3.1.1 boundary—item boundaries define the subordinate
include bolt hole location and deck/port-to-starboard/aft-to-
components that are to be included in the item. The purpose of
forward sequencing. The method used for setting up location
the boundary definition is to ensure a common understanding
IDs is irrelevant for the standard. It is useful to the standard
of which components are to be included within a specific item.
implementer only and thus it is left to the standard implement-
3.1.2 class—a concept to group objects with similar
er’s discretion.
characteristics, with the purpose of describing common prop-
3.1.10 unique vessel identification—unique equipment iden-
erties.
tification requires a unique site or vessel identifier. This
3.1.2.1 Discussion—The ISO 10303 definition of a class is
classificationproposesthatcommercialvesselsbeidentifiedby
“a concept to group items with similar characteristics, with the
their International Maritime Organization (IMO) number. IMO
purpose of describing the common properties of the class
assigns a unique number to every commercial vessel in the
members. Each item belongs to at least one class. A class
world to be used for the vessel tracking. The structure of the
usually has a criterion for inclusion or exclusion of items.” A
IMO number comprises two parts: a variable seven-digit
class is only an abstraction that helps the categorization of
numeric number (the Lloyd’s Register number) and a constant
objects.
alphaprefix“IMO”(forexample,IMO1234567).Theconstant
3-alpha prefix by definition contributes nothing to the identi-
3.1.3 instance—the physical representation of the member
fication of the ship. Therefore, only the variable seven-digit
of an object class. For example, the main propulsion diesel
numeric element of the IMO number is used. The seven-digit
engineofvesselXYZisaninstanceofthediesel_engineobject
numeric number is maintained by Lloyd’s Register which
class.
assigns a number to a ship at any time following the initiation
3.1.4 object—any item that has properties and functions.
of its construction. This classification also proposes that navy
3.1.5 product identification—this classification proposes vessels be identified by Navy Specific Identification (Hull)
that products be uniquely identified using the following com-
Number preceded by the country code. The structure comprise
bination:ManufacturerCountryCode—ManufacturerNational of two parts: a variable 3-alpha prefix country code followed
Tax ID—Manufacturer Model Number—Manufacturer Model by five to seven digit alphanumeric hull number (for example,
Type. The manufacturer country code must be the ISO 3166-1 USA LPD17). The five to seven digit alphanumeric hull
code for the manufacturer’s country of origin. numbers are maintained by corresponding country navies.
3.1.6 property—an object’s attribute whose value character-
4. Significance and Use
izesaspecificclassinstance.Theprocessofinitializingasetof
4.1 Capturing high quality Reliability, Availability, and
properties for a specific instance is called instantiation.
Maintainability (RAM) performance data requires careful and
3.1.7 string—any list of ACSII characters with variable consistent collection of equipment failure and repair data,
operating hours, and repair time. A standard hierarchy of
length.
equipment boundaries has been needed for machinery data
3.1.8 string array—a dimensionless array of string values.
exchange among the stakeholders in shipbuilding, ship
3.1.9 unique component identification—this classification
classification, and ship operations.
proposes that components be uniquely identified using the
4.2 Industry and government will use a world standard
following combination: Site ID—Generic ID—Location ID.
method for setting the hierarchy of indentures and boundaries
The description of the various identifiers is as follows:
required for assigning failure and repair events to equipment
3.1.9.1 site ID—unique vessel identifier. In some cases, for the tracking and calculation of equipment RAM perfor-
shipping organizations manage their inventory at the fleet level mance.
in such a way that pieces of equipment are removed from one
4.3 Agreed boundaries and equipment identifiers make it
vessel to be brought back to shore for repairs or overhauls
possible to share equipment data among organizations, bench-
whilealreadyservicedpiecesofequipmentpreviouslyinstalled
mark equipment performance, perform modeling and simula-
on board another vessel are used as replacements.This method
tion of current and proposed systems, or use performance data
of managing inventory makes it impractical to associate a
to improve operations of commercial and Naval vessels.
specific component with a vessel ID. The following two
4.4 RAM analysis is primarily based on the observation of
alternativesareacceptable: (1)keepingtheIDofthefirstvessel
individual components among which identical items contribute
on which it was installed throughout the component’s entire
to the same data sample. This classification is designed to be
life time, and (2) assigning a warehouse ID to components that
usedfortheidentificationofindividual(unique)componentsin
can potentially be installed on multiple vessels.
such a way that identical components can be identified within
3.1.9.2 generic ID—the name or code of the object class to
a given data sample.
which the component belong. Standard implementers are free
5. Basis of Classification
to use either the class name or code, depending on data storage
preferences given that class names are string values whereas 5.1 The class library constitutes a generic list of objects to
class codes are numeric values. be used as a toolbox for the development of specific ship
F2446−04 (2010)
breakdown structures as shown in Fig. 1. Instances of object populated properties, including the list of required properties
classes will be created by assigning specific properties, includ- for RAM data exchange. Class names are meant to be
ing custom-designed properties serving organization specific
transparent to end-users once a specific hierarchy is estab-
functions and required properties aimed at facilitating global
lished. They will only facilitate the data exchange. End-users
identification and RAM assessment.
are expected to be presented with customized label names that
5.1.1 The class library includes systems, pieces of
are dependent on business logic, culture, and language. Label
equipment, elementary items (with some exceptions, elemen-
names are optional object properties populated by the standard
taryitemscanbeseenasparts),andsoftwareproducts.Itisthat
implementer.
standard implementers use the class library to build specific
5.3 Existing ship breakdown structures and identification
ship breakdown structures by using a parent/child relationship
systems will be made compatible by adding a reference to the
linking object class instances.
object class for each component. Standard implementers will
5.1.2 Each item has a parent to which it belongs.The parent
be required to collect and store a minimum set of properties,
of any item can be any other type of items. For example, the
identified as “required properties.” The storage structure of the
parent of a system is likely to be the ship, although in some
instances it is another system. The ship is an item of the class object class properties (for example, manufacturer, model
library because it is the primary ancestor of all items and the
number, Mean Time Between Failures, and so forth) is not
directparentofmostsystems.Asaprimaryancestor,ashiphas imposed by this classification . Standard implementers are free
no parent.
to use their own storage structure. Implementers are also able
5.1.3 The parent of an elementary item is a system, a piece
tocreateprivatedataexchangefordatathatistostaywithinthe
of equipment or another elementary item. Elementary items do
organization (see Appendix X1).
not have children.An item is always defined with respect to its
5.4 Thisclassificationprovidesalistofgenericcriteriatobe
parent.As a result, the identification of the parent is a required
used for the definition of equipment boundaries. Each bound-
property for all items. Within a given ship structure, the
ary criterion specifies whether a particular item is included in
combination of an item identifier and its parent identifier is not
the definition of pieces of equipment. Excluded items must not
unique. Indeed, several identical items with identical functions
be used when compiling the identification and RAM properties
are commonly found on board a specific ship. A location ID
to be exchanged.
(such as the bolt hole location, for example) is thus required to
uniquelyidentifyeachitem.Consequently,anitemofaspecific
6. Keywords
ship breakdown structure is fully identified by its own ID, the
ID of its parent, and a location ID.
6.1 availability; boundary; equipment; hierarchy; maintain-
ability; maintenance; reliability; ship; shipboard; shipboard
5.2 Equipment RAM data exchange will take place through
the exchange of object class instances, that is, objects with equipment; ship reliability; vessel
FIG. 1Object Instantiation Process for Population and Data Exchange
F2446−04 (2010)
ANNEX
(Mandatory Information)
A1. MECHANICAL AND SOFTWARE PRODUCT CLASS LIBRARY
A1.1 See Table A1.1, Table A1.2, Table A1.3, Table A1.4,
and Table A1.5.
TABLE A1.1 Boundary Criteria
Boundary
Boundary Element Included in Parent? Element Description
Code
b_00001 associated valves yes a valve that is required for the proper operation of the product
b_00002 attached indicating yes an integrated part of the product used for measuring and displaying a variable
instruments
b_00003 built-in tanks yes an integrated part of the product that is a container used for holding a liquid or
...

Questions, Comments and Discussion

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