ISO TC184/WG13/N11 |
Date: 2007-04-05 |
COPYRIGHT NOTICE:This ISO document is a working draft or Committee Draft and is copyright protected by ISO. While the reproduction of working drafts or Committee Drafts in any form for use by Participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from ISO. Requests for permission to reproduce this document for the purposes of selling it should be addressed as shown below (via the ISO TC 184/SC4 Secretariat’s member body) or to ISO's member body in the country of the requester.
Copyright Manager
ANSI 11 West 42nd Street New York, New York 10036 USA phone: +1-212-642-4900 fax: +1-212-398-0023 Reproduction for sales purposes may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. |
|
ABSTRACT:This part of ISO 8000 specifies the terminology for ISO 8000. It contains terms, definitions and abbreviations relating to data quality and other terms, definitions and abbreviations needed for the understanding of such terms. COMMENTS TO READER:Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. This document has been reviewed using the internal review checklist (see WG13 N16), the project leader checklist (see WG13 N9), and the convener checklist (see WG13 N10), and is ready for this ballot cycle. |
|
Project leader: Peter Benson Address: ECCMA 2980 Linden St Ste E2 Bethlehem, PA 18017-3283 USA Telephone: +1 610-861-5990 Facsimile: +1 610-861-5992 Electronic mail: peter.benson@eccma.org |
Part editor: Gerald Radack Address: Concurrent Technologies Corp. 441 Friendship Rd Ste 103 Harrisburg, PA 17111-1204 USA Telephone: +1 610 449 3853 Facsimile: +1 610 449 0853 Electronic mail: radack@ctc.com |
© ISO 2007
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 734 10 79
E-mail copyright@iso.ch
Web www.iso.ch
3.2 Terms relating to management
3.3 Terms relating to organization
3.4 Terms relating to process and product
3.5 Terms relating to characteristics
3.6 Terms relating to conformity
3.7 Terms relating to documentation
3.9 Terms relating to data quality
3.10 Terms relating to data quality characteristics
3.11 Terms relating to conceptual modeling
3.12 Terms relating to dictionaries
3.13 Terms relating to master data
Annex A (normative) Document identification
Annex B (informative) Supporting terms and definitions
B.2 Terms and definitions from other standards
Annex C (informative) Terms and definitions from other ISO TC184/SC4 standards
C.2 Terms and definitions from ISO TC184/SC4 standards
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.
In other circumstances, particularly when there is an urgent market requirement for such documents, a technical committee may decide to publish other types of normative document:
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an International Standard or be withdrawn.
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.
ISO/CD TS 8000-2 was prepared by Technical Committee ISO/TC 184, Industrial automation systems and integration, Subcommittee SC4, Industrial data.
A complete list of parts of ISO 8000 is available from the Internet:
Typical consequences of poor data quality include customer dissatisfaction and lost revenue as well as higher costs associated with additional time to reconcile data, loss of credibility in a system and associated compliance problems. Data quality is dependent both on the quality of the data capture process as well as the processes used to store and transfer data. Finally managing data quality is also about managing the understanding and the expectations of quality and this requires the ability to objectively measure the costs and benefits of data quality.
While data quality is most commonly associated with transactional data, it is important to keep in mind that business information, such as designs, processes, machine instructions and trading partner information, constitutes an ever-increasing proportion of a business's assets and an ever-increasing proportion of this is stored in electronic form. Managing data quality is therefore an essential element in protecting the value of electronic information.
While the bit is the fundamental building block of electronically stored data, data elements are the fundamental building block of electronically stored information. Data elements consist of labeled data values where the data label provides the meaning for the data value.
It follows that as data element values are the fundamental building blocks of electronically stored information, the quality of the data element values is a major determinant of the quality of the information and consequently the accuracy and reliability of the knowledge that can be derived from the information.
NOTE The history of the origination, cataloguing and transfer of ownership of information is commonly referred to as the provenance.
An assertion of accuracy is only meaningful if it is accompanied by reference to the standard or benchmark against which the data element values were assessed along with the identification of the organization that performed the test and the date and time the test was performed.
Where data is a product of an organization, an assertion of reliability is an assertion of the data quality management capabilities of the organization providing the data.
This Technical Specification provides general requirements for data quality, independent of syntax. It may be used with any other standard that specifies a syntax for a data set.
COMMITTEE DRAFT | ISO/CD TS 8000-2 |
This part of ISO 8000 contains the terminology for ISO 8000.
The following are within the scope of this part of ISO 8000:
The following referenced documents are indispensable for the application 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/IEC 8824-1:2002, Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic notation.
ISO 1087-1:2000, Terminology work — Vocabulary — Part 1: Theory and application.
ISO 9000:2005, Quality management systems — Fundamentals and vocabulary.
ISO 9001:2000, Quality management systems — Requirements.
ISO 10303-1, Industrial automation systems and integration — Product data representation and exchange — Part 1: Overview and fundamental principles.
ISO/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic notation.
ISO/IEC 11179-1:2004, Information technology — Metadata Registries (MDR) — Part 1: Framework.
ISO/IEC 11404:1996, Information technology — Programming languages, their environments and system software interfaces — Language-independent datatypes.
For the purposes of this part of ISO 8000, the terms and definitions given in part true of this Technical Specification apply.
degree to which a set of inherent characteristics fulfils requirements
NOTE 1 The term “quality” can be used with adjectives such as poor, good or excellent.
NOTE 2 “Inherent”, as opposed to “assigned”, means existing in something, especially as a permanent characteristic.
[ISO 9000:2005, clause 3.1.1]
need or expectation that is stated, generally implied or obligatory
NOTE 1 “Generally implied” means that it is custom or common practice for the organization, its customers and other interested parties, that the need or expectation under consideration is implied.
NOTE 2 A qualifier can be used to denote a specific type of requirement, e.g. product requirement, quality management requirement, customer requirement.
NOTE 3 A specified requirement is one that is stated, for example in a document.
NOTE 4 Requirements can be generated by different interested parties
NOTE 5 This definition differs from that provided in 3.12.1 of ISO/IEC Directives, Part 2:2004.
3.12.1
requirement
expression in the content of a document conveying criteria to
be fulfilled if compliance with the document is to be claimed and
from which no deviation is permitted
[ISO 9000:2005, clause 3.1.2]
set of interrelated or interacting elements
[ISO 9000:2005, clause 3.2.1]
system to establish policy and objectives and to achieve those objectives
[ISO 9000:2005, clause 3.2.2]
management system to direct and control an organization with regard to quality
[ISO 9000:2005, clause 3.2.3]
overall intentions and direction of an organization related to quality as formally expressed by top management
[ISO 9000:2005, clause 3.2.4]
something sought, or aimed for, related to quality
NOTE 1 Quality objectives are generally based on the organization's quality policy
NOTE 2 Quality objectives are generally specified for relevant functions and levels in the organization
[ISO 9000:2005, clause 3.2.5]
person or group of people who directs and controls an organization at the highest level
[ISO 9000:2005, clause 3.2.7]
coordinated activities to direct and control an organization with regard to quality
NOTE Direction and control with regard to quality generally includes establishment of the quality policy and quality objectives, quality planning, quality control, quality assurance and quality improvement.
[ISO 9000:2005, clause 3.2.8]
part of quality management focused on setting quality objectives and specifying necessary operational processes and related resources to fulfil the quality objectives
NOTE Establishing quality plans can be part of quality planning.
[ISO 9000:2005, clause 3.2.9]
part of quality management focused on fulfilling quality requirements
[ISO 9000:2005, clause 3.2.10]
part of quality management focused on providing confidence that quality requirements will be fulfilled
[ISO 9000:2005, clause 3.2.11]
part of quality management focused on increasing the ability to fulfil quality requirements
NOTE The requirements can be related to any aspect such as effectiveness, efficiency or traceability.
[ISO 9000:2005, clause 3.2.12]
extent to which planned activities are realized and planned results achieved
[ISO 9000:2005, clause 3.2.14]
relationship between the result achieved and the resources used
[ISO 9000:2005, clause 3.2.15]
group of people and facilities with an arrangement of responsibilities, authorities and relationships
EXAMPLE Company, corporation, firm, enterprise, institution, charity, sole trader, association, or parts or combination thereof.
NOTE 1 The arrangement is generally orderly.
NOTE 2 An organization can be public or private.
NOTE 3 This definition is valid for the purposes of quality management system standards. The term “organization” is defined differently in ISO/IEC Guide 2.
[ISO 9000:2005, clause 3.3.1]
The following material was added by this part of ISO 8000 and is not part of ISO 9000:2005.
NOTE 4 As one or more people constitute a group, a sole trader is an organization.
NOTE 5 ISO/IEC Guide 2 defines "organization" as:
4.2
organization
body that is based on the membership of other bodies or individuals and has an established constitution and its own administration
organization or person that receives a product
EXAMPLE Consumer, client, end-user, retailer, beneficiary and purchaser.
NOTE A customer can be internal or external to the organization.
[ISO 9000:2005, clause 3.3.5]
organization or person that provides a product
EXAMPLE Producer, distributor, retailer or vendor of a product, or provider of a service or information.
NOTE 1 A supplier can be internal or external to the organization.
NOTE 2 In a contractual situation, a supplier is sometimes called "contractor".
[ISO 9000:2005, clause 3.3.6]
person or group having an interest in the performance or success of an organization
EXAMPLE Customers, owners, people in an organization, suppliers, bankers, unions, partners or society.
NOTE A group can comprise an organization, a part thereof, or more than one organization.
[ISO 9000:2005, clause 3.3.7]
set of interrelated or interacting activities which transforms inputs into outputs
NOTE 1 Inputs to a process are generally outputs of other processes.
NOTE 2 Processes in an organization are generally planned and carried out under controlled conditions to add value.
NOTE 3 A process where the conformity of the resulting product cannot be readily or economically verified is frequently referred to as a “special process”.
[ISO 9000:2005, clause 3.4.1]
result of a process
NOTE 1 There are four generic product categories, as follows:
Many products comprise elements belonging to different
generic product categories. Whether the product is then called
service, software, hardware or processed material depends on the
dominant element. For example, the offered product "automobile"
consists of hardware (e.g. tyres), processed materials (e.g. fuel,
cooling liquid), software (e.g. engine control software, driver's
manual), and service (e.g. operating explanations given by the
salesman).
NOTE 2 Service is the result of at least one activity necessarily
performed at the interface between the supplier and customer and is generally
intangible. Provision of a service can involve, for example, the
following:
Software consists of information and is generally intangible
and can be in the form of approaches, transactions or procedures.
Hardware
is generally tangible and its amount is a countable characteristic.
Processed materials are generally tangible and their amount is a
continuous characteristic. Hardware and processed materials often
are referred to as goods.
NOTE 3 Quality assurance is mainly focused on intended product.
[ISO 9000:2005, clause 3.4.2]
The following material was added by this part of ISO 8000 and is not part of ISO 9000:2005.
NOTE 4 The notes from the ISO 9000 definition have been omitted.
unique process, consisting of a set of coordinated and controlled activities with start and finish dates, undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources
NOTE 1 An individual project can form part of a larger project structure.
NOTE 2 In some projects the objectives are refined and the product characteristics defined progressively as the project proceeds.
NOTE 3 The outcome of a project can be one or several units of product.
NOTE 4 Adapted from ISO 10006:2003.
[ISO 9000:2005, clause 3.4.3]
specified way to carry out an activity or a process
NOTE 1 Procedures can be documented or not.
NOTE 2 When a procedure is documented, the term “written procedure” or “documented procedure” is frequently used. The document that contains a procedure can be called a “procedure document”.
[ISO 9000:2005, clause 3.4.5]
ability to trace the history, application or location of that which is under consideration
NOTE When considering product, traceability can
relate to
[ISO 9000:2005, clause 3.5.4]
fulfilment of a requirement
NOTE The term “conformance” is synonymous but deprecated.
[ISO 9000:2005, clause 3.6.1]
nonfulfilment of a requirement
[ISO 9000:2005, clause 3.6.2]
information and its supporting medium
EXAMPLE Record, specification, procedure document, drawing, report, standard.
NOTE 1 The medium can be paper, magnetic, electronic or optical computer disc, photograph or master sample, or a combination thereof.
NOTE 2 A set of documents, for example specifications and records, is frequently called “documentation”.
NOTE 3 Some requirements (e.g. the requirement to be readable) relate to all types of documents, however there can be different requirements for specifications (e.g. the requirement to be revision controlled) and records (e.g. the requirement to be retrievable).
[ISO 9000:2005, clause 3.7.2]
document specifying the quality management system of an organization
NOTE 1 These procedures generally include those referring to quality management processes and to product realization processes.
NOTE 2 Quality manuals can vary in detail and format to suit the size and complexity of an individual organization.
[ISO 9000:2005, clause 3.7.4]
document specifying which procedures and associated resources shall be applied by whom and when to a specific project, product, process or contract
NOTE 1 These procedures generally include those referring to quality management processes and to product realization processes.
NOTE 2 A quality plan often makes reference to parts of the quality manual or to procedure documents.
NOTE 3 A quality plan is generally one of the results of quality planning.
[ISO 9000:2005, clause 3.7.5]
unit of data expressed as zero or one in binary notation
knowledge concerning objects, such as facts, events, things, processes, or ideas, including concepts, that within a certain context has a particular meaning
[ISO/IEC 2382-1:1993, clause 01.01.01]
re-interpretable representation of information in a formalized manner suitable for communication, interpretation, or processing
NOTE Data can be processed by humans or by automatic means.
[ISO/IEC 2382-1:1993, clause 01.01.02]
data stored as bits enabling it to be processed by machines
data that describes and defines other data
[ISO/IEC 11179-1:2004, clause 3.2.16]
unit of data for which the definition, identification, representation, and permissible values are specified by means of a set of attributes.
[ISO/IEC 11179-1:2004, clause 3.3.8]
concept that can be represented in the form of a data element, described independently of any particular representation
[ISO/IEC 11179-1:2004, clause 3.3.9]
data value
[ISO/IEC 11179-1:2004, clause 3.3.37]
set of permissible values
[ISO/IEC 11179-1:2004, clause 3.3.38]
meaning or semantic content of a value
NOTE Given a permissible value, representation of its value meaning shall be independent of (and shall not constrain) the representation of its corresponding value.
[ISO/IEC 11179-1:2004, clause 3.3.39]
expression of a value meaning allowed in a specific value domain
[ISO/IEC 11179-1:2004, clause 3.3.28]
set of distinct values, characterized by properties of those values, and by operations on those values
[ISO/IEC FDIS 11404:1996, clause 4.11]
characteristic of an object or entity
[ISO/IEC 11179-1:2004, clause 3.1.1]
instance of a specific value associated with a data element
reference to the property associated with a data element
logically meaningful grouping of data
EXAMPLE Computer-aided design (CAD) files, electronic data interchange (EDI) transactions.
specification of the content and format of a data set
record of a particular event or state in the provenance of a data element value at a particular point in time
coordinated activities to direct and control an organization with regard to data quality
degree to which a data element value is correct
controlled data set that constitutes the master copy
EXAMPLE The master database of motor vehicle registration maintained by the Department of Transportation of the Commonwealth of Pennsylvania, USA.
degree to which a data element value agrees with the authoritative source
data set whose content is copied from one or more authoritative sources or surrogate sources and that is deemed to be reliable
EXAMPLE A national database of motor vehicle registrations, compiled by the United States government from the master records at state motor vehicle agences, if deemed reliable, would be a surrogate source.
degree to which a data element value agrees with a surrogate source
degree to which a data element value correctly reflects the property of a real-world object or event
history of the origination, cataloguing and transfer of ownership of a data element value
extent to which an organization can be relied upon to produce data that is of consistent and repeatable quality
NOTE An organization's reliability may change over time. Therefore, any assertion of reliability should be prefixed by a time element.
representation of a
[ISO 1087-1:2000, clause 3.3.1]
abstraction of a property of an
NOTE Characteristics are used for describing
[ISO 1087-1:2000, clause 3.2.4]
The following material was added by this part of ISO 8000 and is not part of ISO 1087-1:2000.
EXAMPLE "Made of wood" is an example of a characteristic.
unit of knowledge created by a unique combination of
NOTE Concepts are not necessarily bound to particular languages. They are, however, influenced by the social or cultural background which often leads to different categorizations.
[ISO 1087-1:2000, clause 3.2.1]
The following material was added by this part of ISO 8000 and is not part of ISO 1087-1:2000.
EXAMPLE
anything perceivable or conceivable
NOTE 1 Objects may be material (e.g. an engine, a sheet of paper, a diamond), immaterial (e.g. conversion ratio, a project plan) or imagined (e.g. a unicorn).
[ISO 1087-1:2000, clause 3.1.1]
The following material was added by this part of ISO 8000 and is not part of ISO 1087-1:2000.
NOTE 2 Whereas a
statement that describes a given object in the extension of the concept
EXAMPLE For the concept "ergonomic chair", one of the object in the extension (a particular chair manufactured by company X) has the property: a "patented S-shaped back". This property is abstracted as a more generic statement or characteristic "has a back (by virtue that it is a chair) that is designed to accommodate the human back".
NOTE 1 Properties that are common to all the objects in the extension of a concept are abstracted into the characteristics that constitute the concept.
NOTE 2 This definition is intended to be compatible with the use of the term property in ISO 1087-1 and ISO 704.
NOTE 3 ISO 1087-1 uses the term property in the definition of characteristic but does not define it.
collection of concept dictionary entries that allows lookup by concept identifier
description of a concept containing, at a minimum, a globally unambiguous identifier and a definition
reference data
data that are centrally managed within an organization, are considered authoritative within the organization, and are intended to be used by multiple applications across the organization
NOTE 1 Master data typically includes records that describe customers, products, employees, materials, suppliers, services, and shareholders.
NOTE 2 Maser data is typically non-transactional in nature
process of transcribing, abstracting or validating data
For the purposes of this part of ISO 8000, the following abbreviations apply:
DE | data element |
DEC | data element concept |
DEV | data element value |
DRS | data requirements statement |
DQM | data quality management |
QA | quality assurance |
To provide for unambiguous identification of an information object in an open system, the object identifier
is assigned to this Technical Specification. The meaning of this value is defined in ISO 8824-1, and is described in ISO 10303-1.
This annex contains terms that are referenced by definitions in Clause this Technical Specification but differ from the definitions adopted for this Technical Specification. The definitions in this annex are included to enable understanding of the definitions that reference them. The definitions in Clause are considered normative for this Technical Specification.
distinguishing feature
NOTE 1 A characteristic can be inherent or assigned.
NOTE 2 A characteristic can be qualitative or quantitative.
NOTE 3 There are various classes of characteristic, such as the
following:
[ISO 9000:2005, clause 3.5.1]
any concrete or abstract thing that exists, did exist, or might exist, including associations among these things
EXAMPLE A person, object, event, idea, process, etc.
NOTE An entity exists whether data about it are available or not.
[ISO/IEC 2382-17:1999, clause 17.02.05]
meaningful data
[ISO 9000:2005, clause 3.7.1]
The following material was added by this part of ISO 8000 and is not part of ISO 9000:2005.
NOTE 1 To be considered information, data must be understood by the intended recipients. This means that it must be in a form suitable for human understanding and interpretation and in a language that the intended recipients can understand.
NOTE 2 Meaningful data may require the presence of multiple discrete data elements. For example, under typical business practice, an invoice date only constitues meaningful information if it is accompanied by at least three other pieces of data: invoicer, invoicee, and invoice amount. Of course, other data elements, such as invoice number, may be required within certain contexts.
This annex contains definitions from other TC184/SC4 standards for terms defined in Clause . The definitions in this annex are not applicable to this Technical Specification, but are included here for comparison purposes.
a piece of information stating a property of an enterprise entity
NOTE The concept provided here to the broad concept of entity as defined in European standard ENV 12204. The term entity used in the definition provided by the ENV 12204 has been replaced here by enterprise entity as in ISO 15531-1 to avoid any confusion and inconsistency with the reserved term “entity” defined in ISO 10303. The usage of this concept has been limited to the area of concern of ISO 15531 in order to enable the use of the term “enterprise entity” instead of “entity”, and the field of application of the term attribute is restricted to enterprise entities.
[ISO 15531-31:2004, clause 3.5.1]
a constant property, characteristic of a part, of which the value is fixed once the part is defined
EXAMPLE For a ball-bearing, the inner and outer diameters are part characteristics.
NOTE Changing the value of a characteristic of a part would mean changing the part.
[ISO 13584-24:2003, clause 3.12]
general notion or idea of something
[ISO 18876-1:2003, clause 3.1.3]
a represent ation of information in a formal manner suitable for interpretation, communication, or processing by human beings or computers
[ISO 10303-1:1994, clause 3.2.14]
facts, concepts, or instructions
[ISO 10303-1:1994, clause 3.2.20]
concept or a physical thing which may exist in the real world
[ISO 15531-31:2004, clause 3.5.7]
a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose
[ISO/IEC 6523-1:1998, clause 3.1]
structured set of activities involving various enterprise entities, that is designed and organised for a given purpose
NOTE The definition provided here is very close to that given in ISO 10303-49. Nevertheless ISO 15531 needs the notion of structured set of activities, without any predefined reference to the time or steps. In addition, from the point of view of flow management, some empty processes may be needed for a synchronisation purpose although they are not actually doing anything (ghost task).
[ISO 15531-1:2004, clause 3.6.29]
a thing or substance produced by a natural or artificial process
[ISO 10303-1:1994, clause 3.2.26]
a real world characteristic which is represented by either attributes or constraints.
[ISO 15531-31:2004, clause 3.5.10]
an information that may be represented by a data element type
[ISO 13584-42:1998, clause 3.4.10]
all the planned and systematic activities implemented within the quality system that can be demonstrated to provide confidence that a product or service will fulfil requirements for expected quality
NOTE Definition adapted from APICS dictionary.
[ISO 15531-1:2004, clause 3.6.42]
process plant life-cycle data that represents information about classes or individuals which are common to many process plants or of interest to many users
[ISO 15926-1:2004, clause 3.1.18]
a unit of data
[ISO 10303-11:2004, clause 3.3.22]
[1] ISO 10303-1:1994, Industrial automation systems and integration — Product data representation and exchange — Part 1: Overview and fundamental principles. 1st ed.
[2] ISO 10303-11:2004, Industrial automation systems and integration — Product data representation and exchange — Part 11: Description methods: The EXPRESS language reference manual. 2nd ed.
[3] ISO 13584-24:2003, Industrial automation systems and integration — Parts library — Part 24: Logical resource: Logical model of supplier library. 1st ed.
[4] ISO 13584-42:1998, Industrial automation systems and integration — Parts library — Part 42: Methodology for structuring part families. 1st ed.
[5] ISO 15531-1:2004, Industrial automation systems and integration — Industrial manufacturing management data — Part 1: General overview. 1st ed.
[6] ISO 15531-31:2004, Industrial automation systems and integration — Industrial manufacturing management data — Part 31: Resource information model. 1st ed.
[7] ISO 15926-1:2004, Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities — Part 1: Overview and fundamental principles. 1st ed.
[8] ISO 18876-1:2004, Industrial automation systems and integration — Integration of industrial data for exchange, access and sharing — Part 1: Architecture overview and description. 1st ed.
[9] ISO/IEC 2382-1:1993, Information technology — Vocabulary — Part 1: Fundamental terms. 3rd ed.
[10] ISO/IEC 2382-17:1999, Information technology — Vocabulary — Part 17: Databases. 2nd ed.
[11] ISO/IEC GUIDE 2:2004, Standardization and related activities — General vocabulary. 8th ed.
[12] APICS dictionary. 8th ed.
1) To be published
© ISO 2007 — All rights reserved