| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO 2382-19:1980 |
Data processing — Vocabulary — Section 19 : Analog computing |
|
Withdrawn |
1980-06 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO 2382-19:1989 |
Information processing systems — Vocabulary — Part 19: Analog computing |
Serves for the international communication in information processing. Provides selected English and French terms and their definition in the field of concepts relating to analog and hybrid arithmetic units, function generators, converters and modes of operation of such components.
|
Withdrawn |
1989-05 |
Edition : 2 |
Number of pages : 10 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC CD 5259-4 |
Artificial intelligence — Data quality for analytics and machine learning (ML) — Part 4: Data quality process framework |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 2382-28:1995 |
Information technology — Vocabulary — Part 28: Artificial intelligence — Basic concepts and expert systems |
Defines basic concepts related to artificial intelligence and expert systems.
|
Withdrawn |
1995-12 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-29:1999 |
Information technology — Vocabulary — Part 29: Artificial intelligence — Speech recognition and synthesis |
|
Withdrawn |
1999-08 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-31:1997 |
Information technology — Vocabulary — Part 31: Artificial intelligence — Machine learning |
|
Withdrawn |
1997-12 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-32:1999 |
Information technology — Vocabulary — Part 32: Electronic Mail |
|
Withdrawn |
1999-01 |
Edition : 1 |
Number of pages : 41 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-34:1999 |
Information technology — Vocabulary — Part 34: Artificial intelligence — Neural networks |
|
Withdrawn |
1999-08 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-36:2008 |
Information technology — Vocabulary — Part 36: Learning, education and training |
ISO/IEC 2382-36:2008 is intended to facilitate international communication in information technology for learning, education and training . It presents, in two languages, terms and definitions of selected concepts relevant to the field of information technology for learning, education and training, and identifies relationships among the entries.
|
Withdrawn |
2008-05 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-36:2008/Cor 1:2012 |
Information technology — Vocabulary — Part 36: Learning, education and training — Technical Corrigendum 1 |
|
Withdrawn |
2012-04 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-36:2013 |
Information technology — Vocabulary — Part 36: Learning, education and training |
ISO/IEC 2382-36:2013 is intended to facilitate international communication in information technology for learning, education, and training. It presents, in two languages, terms and definitions of selected concepts relevant to the field of information technology for learning, education, and training and identifies relationships among the entries.
Translations into other languages are provided in annexes.
|
Withdrawn |
2013-11 |
Edition : 2 |
Number of pages : 28 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-36:2019 |
Information technology — Vocabulary — Part 36: Learning, education and training |
This document provides terms and definitions for vocabulary used in the field of learning, education and training (LET) to facilitate international communication in the field. This document also identifies and provides the relationships among the vocabulary ensuring a cohesive and harmonized approach.
|
Published |
2019-06 |
Edition : 3 |
Number of pages : 23 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-37:2012 |
Information technology — Vocabulary — Part 37: Biometrics |
ISO/IEC 2382-37:2012 establishes a systematic description of the concepts in the field of biometrics pertaining to recognition of human beings and reconciles variant terms in use in pre-existing biometric standards against the preferred terms, thereby clarifying the use of terms in this field.
|
Withdrawn |
2012-12 |
Edition : 1 |
Number of pages : 21 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC CD 5259-5 |
Artificial intelligence — Data quality for analytics and machine learning (ML) — Part 5: Data quality governance |
This document provides a data quality governance framework for analytics and machine learning to enable governing bodies of organizations to direct and oversee the implementation and operation of data quality measures, management, and related processes with adequate controls throughout the data life cycle. This document can be applied to any analytics and machine learning. This document does not define specific management requirements or process requirements specified in 5259-3 and 5259-4 respectively.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 2382-37:2017 |
Information technology — Vocabulary — Part 37: Biometrics |
ISO/IEC 2382-37:2017 establishes a systematic description of the concepts in the field of biometrics pertaining to recognition of human beings and reconciles variant terms in use in pre-existing biometric standards against the preferred terms, thereby clarifying the use of terms in this field.
Excluded from the scope of this document are concepts (represented by terms) from information technology, pattern recognition, biology, mathematics, etc. Biometrics uses such fields of knowledge as a basis.
In principle, mode specific terms are outside of scope of this document.
Words that are bolded are defined in this document. Words that are not bolded are understood in their natural language sense. The authority for natural language use of terms in this document is the Concise Oxford English Dictionary, Thumb Index Edition (tenth edition, revised, 2002). Words used in their natural language sense are considered out-of-scope for further definition in this document.
|
Withdrawn |
2017-02 |
Edition : 2 |
Number of pages : 27 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382-37:2022 |
Information technology — Vocabulary — Part 37: Biometrics |
This document establishes a systematic description of the concepts in the field of biometrics pertaining to recognition of human beings. This document also reconciles variant terms in use in pre-existing International Standards on biometrics against the preferred terms, thereby clarifying the use of terms in this field.
This document does not cover concepts (represented by terms) from information technology, pattern recognition, biology, mathematics, etc. Biometrics uses such fields of knowledge as a basis.
In principle, mode-specific terms are outside of scope of this document.
|
Published |
2022-03 |
Edition : 3 |
Number of pages : 34 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 2382:2015 |
Information technology — Vocabulary |
This standard of vocabulary taken from the multi-part ISO/IEC 2382 standard is presented in language-specific order and is intended to facilitate international communication in information technology. It presents, in two languages, terms and definitions of selected concepts relevant to this field.
In order to facilitate their translation into other languages, the definitions are drafted so as to avoid, as far as possible, any peculiarity attached to a language.
|
Published |
2015-05 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO 2784:1974 |
Continuous forms used for information processing — Sizes and sprocket feed holes |
Describes the sizes of continuous forms and the diameter and location of the sprocket feed holes. Applies to paper in continuous lengths intended for use with automatic data processing equipment for print-out of documents for administrative, commercial and technical use. References: ISO/R 187; ISO/R 215.
|
Published |
1974-03 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
35.020
Information technology (IT) in general
;
85.080.10
Office paper
|
| ISO/IEC TS 4213:2022 |
Information technology — Artificial intelligence — Assessment of machine learning classification performance |
This document specifies methodologies for measuring classification performance of machine learning models, systems and algorithms.
|
Published |
2022-10 |
Edition : 1 |
Number of pages : 33 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC DIS 4879 |
Information technology — Quantum computing — Terminology and vocabulary |
|
Under development |
|
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC DIS 5207 |
Information technology — Data usage — Terminology and use cases |
|
Under development |
|
Edition : 1 |
Number of pages : 51 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC DIS 5212 |
Information technology — Data usage — Guidance for data usage |
|
Under development |
|
Edition : 1 |
Number of pages : 25 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 5230:2020 |
Information technology — OpenChain Specification |
This document specifies the key requirements of a quality open source license compliance program in order to provide a benchmark that builds trust between organizations exchanging software solutions comprised of open source software.
|
Published |
2020-12 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC CD 5259-1 |
Artificial intelligence — Data quality for analytics and machine learning (ML) — Part 1: Overview, terminology, and examples |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC TS 5723:2022 |
Trustworthiness — Vocabulary |
This document provides a definition of trustworthiness for systems and their associated services, along with a selected set of their characteristics.
|
Published |
2022-07 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC DIS 5927 |
Augmented and Virtual Reality safety — Guidance on safe immersion, set up and usage |
|
Under development |
|
Edition : 1 |
Number of pages : 28 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 5965:2021 |
Information technology — Swordfish Scalable Storage Management API Specification |
This document defines the Swordfish Scalable Storage Management API.
Swordfish extends the Redfish Scalable Platforms Management API Specification, as defined by ISO 30115. It defines a comprehensive, RESTful API for storage management that addresses block storage, file systems, object storage, and storage network infrastructure. It is centered around common operational and business concerns of storage management, including:
Configuration and provisioning
Monitoring
Event and log management
Performance assessment
Diagnostics
Fault detection and remediation
Security
Accounting and resource consumption
Swordfish’s storage model is built around well-defined classes of service, which provide a means to map high-level business goals and objectives to specific, storage-based actions and requirements, in a clear and consistent way that can be applied uniformly across a broad spectrum of storage configurations and storage types (e.g., block storage, file systems, object stores). Common storage management functionality covered by class of service includes snapshots, replication, mapping and masking, and provisioning.
The Redfish specification provides the protocols and a core set of data models and behaviors for the management of systems. It defines the elements and behaviors that are mandatory for all Redfish implementations. Additionally it defines additional elements and behaviors that can be chosen by system vendors or manufacturers. The specifications also defines points at which OEM (system vendor) extensions can be provided by a given implementation. The specifications specifies normative requirements for Redfish Services and associated materials, such as Redfish Schema files. The Redfish specifications does not set requirements for Redfish clients, but willindicate what a Redfish client should do in order to access and utilize a Redfish Service successfully and effectively.
The Swordfish specification defines additional data models and behaviors for the management of storage systems and storage infrastructure. A Swordfish implementation shall conform to all requirements specified in the Redfish specifications.
Swordfish is suitable for a wide range of storage, from small-scale object drives, integrated RAID cards or RBODs providing storage services, to external disk arrays or file servers, to infrastructure providing storage services for converged, hyperscale and large scale cloud environments.
|
Published |
2021-08 |
Edition : 1 |
Number of pages : 190 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC PRF 5965 |
Information technology — Swordfish Scalable Storage Management API Specification |
This document defines the Swordfish Scalable Storage Management API.
Swordfish extends the Redfish Scalable Platforms Management API Specification, as defined by ISO 30115. It defines a comprehensive, RESTful API for storage management that addresses block storage, file systems, object storage, and storage network infrastructure. It is centered around common operational and business concerns of storage management, including:
Configuration and provisioning
Monitoring
Event and log management
Performance assessment
Diagnostics
Fault detection and remediation
Security
Accounting and resource consumption
Swordfish’s storage model is built around well-defined classes of service, which provide a means to map high-level business goals and objectives to specific, storage-based actions and requirements, in a clear and consistent way that can be applied uniformly across a broad spectrum of storage configurations and storage types (e.g., block storage, file systems, object stores). Common storage management functionality covered by class of service includes snapshots, replication, mapping and masking, and provisioning.
The Redfish specification provides the protocols and a core set of data models and behaviors for the management of systems. It defines the elements and behaviors that are mandatory for all Redfish implementations. Additionally it defines additional elements and behaviors that can be chosen by system vendors or manufacturers. The specifications also defines points at which OEM (system vendor) extensions can be provided by a given implementation. The specifications specifies normative requirements for Redfish Services and associated materials, such as Redfish Schema files. The Redfish specifications does not set requirements for Redfish clients, but willindicate what a Redfish client should do in order to access and utilize a Redfish Service successfully and effectively.
The Swordfish specification defines additional data models and behaviors for the management of storage systems and storage infrastructure. A Swordfish implementation shall conform to all requirements specified in the Redfish specifications.
Swordfish is suitable for a wide range of storage, from small-scale object drives, integrated RAID cards or RBODs providing storage services, to external disk arrays or file servers, to infrastructure providing storage services for converged, hyperscale and large scale cloud environments.
|
Under development |
2023-05 |
Edition : 2 |
Number of pages : 391 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO 7779:1988 |
Acoustics — Measurement of airborne noise emitted by computer and business equipment |
|
Withdrawn |
1988-06 |
Edition : 1 |
Number of pages : 39 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO 7779:1999 |
Acoustics — Measurement of airborne noise emitted by information technology and telecommunications equipment |
|
Withdrawn |
1999-08 |
Edition : 2 |
Number of pages : 61 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO 7779:1999/Amd 1:2003 |
Acoustics — Measurement of airborne noise emitted by information technology and telecommunications equipment — Amendment 1: Noise measurement specification for CD/DVD-ROM drives |
|
Withdrawn |
2003-03 |
Edition : 2 |
Number of pages : 4 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO 9296:2017 |
Acoustics — Declared noise emission values of information technology and telecommunications equipment |
ISO 9296:2017 is applicable to information technology and telecommunications equipment.
It specifies:
a) for a batch of equipment, the method for determining the following values:
- the declared mean A-weighted sound power level, LWA,m;
- the declared mean A-weighted emission sound pressure level, LpA,m;
- the statistical adder for verification, Kv;
- the statistical upper limit A-weighted sound power level, LWA,c;
b) how acoustical and product information is to be published electronically or in hard-copy format in technical documents or other product literature supplied to users by the manufacturer or declarer;
c) the method for verifying the noise emission values that are declared by the manufacturer or declarer.
|
Published |
2017-08 |
Edition : 2 |
Number of pages : 16 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO 7779:2010 |
Acoustics — Measurement of airborne noise emitted by information technology and telecommunications equipment |
ISO 7779:2010 specifies procedures for measuring and reporting the noise emission of information technology and telecommunications equipment.
The basic emission quantity is the A-weighted sound power level which may be used for comparing equipment of the same type but from different manufacturers, or for comparing different equipment.
Three basic noise emission standards for determination of the sound power levels are specified in ISO 7779:2010 in order to avoid undue restriction on existing facilities and experience. ISO 3741 specifies comparison measurements in a reverberation test room; ISO 3744 and ISO 3745 specify measurements in an essentially free field over a reflecting plane. Any one of these three basic noise emission standards can be selected and used exclusively in accordance with ISO 7779:2010 when determining sound power levels of a machine.
The A-weighted sound power level is supplemented by the A-weighted emission sound pressure level determined at the operator position(s) or the bystander positions, based on basic noise emission standard ISO 11201. This sound pressure level is not a worker's immission rating level, but it can assist in identifying any potential problems that could cause annoyance, activity interference, or hearing damage to operators and bystanders.
Methods for determination of whether the noise emission includes prominent discrete tones or is impulsive in character are specified in annexes.
ISO 7779:2010 is suitable for type tests and provides methods for manufacturers and testing laboratories to obtain comparable results.
The methods specified in ISO 7779:2010 allow the determination of noise emission levels for a functional unit tested individually.
The procedures apply to equipment which emits broadband noise, narrowband noise and noise which contains discrete-frequency components, or impulsive noise.
The sound power and emission sound pressure levels obtained can serve noise emission declaration and comparison purposes (see ISO 9296).
If sound power levels obtained are determined for a number of functional units of the same production series, they can be used to determine a statistical value for that production series (see ISO 9296).
|
Withdrawn |
2010-08 |
Edition : 3 |
Number of pages : 62 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO 7779:2018 |
Acoustics — Measurement of airborne noise emitted by information technology and telecommunications equipment |
This document specifies procedures for measuring and reporting the noise emission of information technology and telecommunications equipment.
NOTE 1 This document is considered part of a noise test code (see 3.1.2) for this type of equipment and is based on basic noise emission standards (see 3.1.1) ISO 3741, ISO 3744, ISO 3745, ISO 9295 and ISO 11201.
The basic emission quantity is the A-weighted sound power level, which can be used for comparing equipment of the same type but from different manufacturers, or for comparing different equipment.
Three basic noise emission standards for determination of the sound power levels are specified in this document in order to avoid undue restriction on existing facilities and experience. ISO 3741 specifies comparison measurements in a reverberation test room; ISO 3744 and ISO 3745 specify measurements in an essentially free field over a reflecting plane. Any of these three basic noise emission standards can be selected and used exclusively in accordance with this document when determining sound power levels of a machine.
The A-weighted sound power level is supplemented by the A-weighted emission sound pressure level determined at the operator position or the bystander positions, based on basic noise emission standard ISO 11201. This sound pressure level is not a level of noise immission at a work station (see 3.2.12), but it can assist in identifying any potential problems that could cause annoyance, activity interference or hearing damage to operators and bystanders.
Methods for determination of whether the noise emission includes prominent discrete tones are specified in Annex D.
This document is suitable for type tests and provides methods for manufacturers and testing laboratories to obtain comparable results.
The methods specified in this document allow the determination of noise emission levels for a functional unit (see 3.1.4) tested individually.
The procedures apply to equipment which emits broad-band noise, narrow-band noise and noise which contains discrete-frequency components, or impulsive noise.
The sound power and emission sound pressure levels obtained can serve noise emission declaration and comparison purposes (see ISO 9296[3]).
NOTE 2 The sound power levels and emission sound pressure levels obtained are not intended to be considered as installation noise immission levels; however, they can be used for installation planning (see ECMA TR/27[11]).
If sound power levels obtained are determined for a number of functional units of the same production series, they can be used to determine a statistical value for that production series (see ISO 9296[3]).
|
Published |
2018-11 |
Edition : 4 |
Number of pages : 69 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO/IEC FDIS 8183 |
Information technology — Artificial intelligence — Data life cycle framework |
This document provides an overarching data life cycle framework that is instantiable for any AI system from data ideation to decommission. This document is applicable to the data processing throughout the AI system life cycle including the acquisition, creation, development, deployment,maintenance and decommissioning. This document does not define specific services, platforms or tools. This document is applicable to all organizations, regardless of type, sizes and nature, that use data in the development and use of AI systems.
|
Under development |
|
Edition : 1 |
Number of pages : 10 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO 9295:1988 |
Acoustics — Measurement of high-frequency noise emitted by computer and business equipment |
Specifies four methods for the determination of sound power levels in the frequency range between 11,2 kHz and 22,4 kHz with the centre frequency of 16 kHz. The first three methods are based on the reverberation room technique, the fourth on a free field over a reflecting plane.
|
Withdrawn |
1988-11 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO 9295:2015 |
Acoustics — Determination of high-frequency sound power levels emitted by machinery and equipment |
ISO 9295:2015 specifies four methods for the determination of the sound power levels of high-frequency noise emitted by machinery and equipment in the frequency range covered by the octave band centred at 16 kHz, which includes frequencies between 11,2 kHz and 22,4 kHz. They are complementary to the methods described in ISO 3741 and ISO 3744. The first three methods are based on the reverberation test room technique. The fourth method makes use of a free field over a reflecting plane.
The test conditions which prescribe the installation and operation of the equipment are those specified in ISO 3741 or ISO 3744 as applicable.
|
Published |
2015-05 |
Edition : 2 |
Number of pages : 18 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO 9296:1988 |
Acoustics — Declared noise emission values of computer and business equipment |
Specifies the method of determining these values; acoustical and product information to be given in technical documents supplied to users by the manufacturer; the method for verifying the declared noise emission values given by the manufacturers.The basic values are the declared A-weighted sound power level and the declared A-weighted sound pressure level, at the operator or bystander positions.
|
Withdrawn |
1988-04 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.020
Information technology (IT) in general
;
17.140.20
Noise emitted by machines and equipment
|
| ISO/IEC TR 12382:1989 |
Permuted index of the vocabulary of information processing |
|
Withdrawn |
1989-04 |
Edition : 1 |
Number of pages : 246 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC TR 12382:1992 |
Permuted index of the vocabulary of information technology |
Contains a permuted index of all terms included in the parts 1 - 28 of ISO 2382. If any of these parts has been revised, the present TR refers to the revision.
|
Published |
1992-12 |
Edition : 2 |
Number of pages : 245 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC CD TS 12791 |
Information technology — Artificial intelligence — Treatment of unwanted bias in classification and regression machine learning tasks |
This document provides mitigation techniques that can be applied throughout the AI system life
cycle in order to treat unwanted bias. This document describes how to address unwanted bias
in AI systems that use machine learning to conduct classification and regression tasks. This
document is applicable to all types and sizes of organization.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC TR 13233:1995 |
Information technology — Interpretation of accreditation requirements in ISO/IEC Guide 25 — Accreditation of Information Technology and Telecommunications testing laboratories for software and protocol testing services |
Provides guidance for assessors and testing laboratories on the specific interpretation of the accreditation requirements applicable to testing (including validation of means of testing and test tools) in the field of information Technology and Telecommunications (IT&T), specifically in relation to software and protocol testing services. Does not apply to the accreditation of inspection, certification and quality assurance assessment activities.
|
Published |
1995-12 |
Edition : 1 |
Number of pages : 53 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.120.20
Product and company certification. Conformity assessment
|
| ISO/IEC 13236:1998 |
Information technology — Quality of service: Framework |
This QOS Framework is a structured collection of concepts and their relationships which describes QOS (Quality of
Service) and enables the partitioning of, and relationships between, the topics relevant to QOS in Information
Technology (IT) to be expressed by a common means of description. In particular, this QOS Framework is directed at IT
systems and their use in providing Open Distributed Processing services.
This QOS Framework is intended to assist those designing and specifying IT systems, and those defining
communications services and protocols, by providing guidance on QOS applicable to systems, services and resources of
various kinds. It describes how QOS can be characterized, how QOS requirements can be specified, and how QOS can
be managed.
This QOS Framework defines terminology and concepts for QOS in IT. It introduces the concept of QOS characteristics,
which represent the fundamental aspects of QOS that are to be managed in various ways; and it defines a number of
QOS characteristics of particular importance. These definitions are independent of how QOS is represented or controlled
in a real system.
This Framework describes how QOS requirements can be expressed, and identifies a number of QOS mechanisms (such
as three-party negotiation) that can be used as components of QOS management functions to meet QOS requirements of
various kinds. It also describes the circumstances in which various combinations of mechanisms may be appropriate.
This QOS Framework provides a basis for the specification of extensions and enhancements to existing or planned
standards, as a result of the need for, and application of, the QOS concepts defined in this Recommendation |
International Standard. It is not the intent of this Recommendation | International Standard to destabilise any existing
Recommendations | International Standards; rather, it is intended that this QOS Framework may be used by:
· developers of new or revised IT-related standards which define or use QOS mechanisms; and
· IT users expressing requirements for QOS.
This QOS Framework does not attempt to provide a basis for the specification of performance objectives or network
signalling of QOS in public communications networks. The QOS aspects of these communications services are
addressed by other ITU-T Recommendations.
The intent of this Recommendation | International Standard is to provide a common vocabulary to both service providers
and service users. Nothing in this Recommendation | International Standard should be construed as placing requirements
on either service providers or service users. It is hoped that a common approach and vocabulary for QOS will assist
multiple service providers to deliver end-to-end QOS to end-systems.
This QOS Framework specifically excludes the detailed specification of QOS mechanisms. It is not the intent of this
Recommendation | International Standard to serve as an implementation specification, to be a basis for appraising the
conformance of implementations, or to define particular services and protocols. Rather, it provides a conceptual and
functional framework for QOS which allows independent teams of experts to work productively on the development of
Recommendations | International Standards.
As applied to OSI, this QOS Framework is consistent with the OSI Basic Reference Model in that it describes operations
and mechanisms which are assignable to layers as specified in the OSI Basic Reference Model. It is consistent with the
OSI Management Framework (see ITU-T Rec. X.700 | ISO/IEC 7498-4) and the Systems Management Overview (see
ITU-T Rec. X.701 | ISO/IEC 10040) in its assignment of functions to management entities. In Annex A, this QOS
Framework presents a model of QOS for OSI which identifies the entities that participate in the management of QOS,
defines the flow of QOS-related information between them and describes how this information is used.
|
Published |
1998-12 |
Edition : 1 |
Number of pages : 48 |
Technical Committee |
35.020
Information technology (IT) in general
;
35.100.01
Open systems interconnection in general
|
| ISO/IEC TR 13243:1999 |
Information technology — Quality of service — Guide to methods and mechanisms |
|
Withdrawn |
1999-11 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
35.020
Information technology (IT) in general
;
35.100.01
Open systems interconnection in general
|
| ISO/IEC 13251:2004 |
Collection of graphical symbols for office equipment |
ISO/IEC 13251:2004 is a bilingual standard (English/French). It provides a certain number of graphical symbols that are typically used on office equipment such as computers, printers, telephones and copying machines.
It comprises four sections:
Section 1 giving general information, provisions and requirements about the use and application of graphical symbols;Section 2 providing an alphabetical index, a numerical index and a graphical overview of all the graphical symbols described in Section 4 of the Standard;Section 3 presenting the graphical symbols selected with the corresponding application, in numerical order;Section 4 containing the symbol originals for reproduction purposes, in numerical order, with the position and size of each graphical symbol described.
Each graphical symbol in Section 3 of the Standard is specified with:
the symbol itself;a number that is the application symbol number from the International Standard (ISO 7000 or IEC 60417) from which it is derived;its definition;a note for technical clarification when necessary.
|
Withdrawn |
2004-05 |
Edition : 1 |
Number of pages : 195 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.080.20
Graphical symbols for use on specific equipment
|
| ISO/IEC 13251:2019 |
Information technology — Collection of graphical symbols for office equipment |
This document provides a collection of graphical symbols which are used typically on office equipment to aid in the user operation of, for example, personal computers, printers, telephones and copying machines.
These graphical symbols are also used in other application areas if appropriate.
NOTE The graphical symbols in this document are collections of relevant graphical symbols standardized in IEC 60417 and ISO 7000.
|
Published |
2019-05 |
Edition : 2 |
Number of pages : 81 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.080.20
Graphical symbols for use on specific equipment
|
| ISO/IEC 19988:2017 |
Information technology — Core Business Vocabulary Standard |
ISO/IEC 19988:2017 specifies the structure of vocabularies and specific values for the vocabulary elements to be utilised in conjunction with ISO/IEC 19987.
|
Published |
2017-10 |
Edition : 2 |
Number of pages : 53 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC DIS 19988 |
Information technology — Core Business Vocabulary (CBV) |
|
Under development |
|
Edition : 3 |
Number of pages : 85 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC TR 14652:2004 |
Information technology — Specification method for cultural conventions |
ISO/IEC TR 14652:2004 specifies a description format for the specification of cultural conventions, a description format for character sets, and a description format for binding character names to ISO/IEC 10646, plus a set of default values for some of these items.
The specification is upward compatible with POSIX locale specifications - a locale conformant to POSIX specifications will also be conformant to the specifications in ISO/IEC TR 14652:2004, while the reverse condition will not hold. The descriptions are intended to be coded in text files to be used via Application Programming Interfaces, that are expected to be developed for a number of systems which comply with ISO/IEC 9945. An alignment effort has been undertaken for this specification to be aligned with the revision of the ISO/IEC 9945 standard published in 2003.
|
Withdrawn |
2004-09 |
Edition : 1 |
Number of pages : 119 |
Technical Committee |
35.020
Information technology (IT) in general
;
35.240.01
Application of information technology in general
|
| ISO/IEC 17788:2014 |
Information technology — Cloud computing — Overview and vocabulary |
ISO/IEC 17788:2014 provides an overview of cloud computing along with a set of terms and definitions. It is a terminology foundation for cloud computing standards.
ISO/IEC 17788:2014 is applicable to all types of organizations (e.g., commercial enterprises, government agencies, not-for-profit organizations).
|
Published |
2014-10 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 17963:2013 |
Web Services for Management (WS-Management) Specification |
ISO/IEC 17963:2013 describes a Web services protocol based on SOAP for use in management‑specific domains. These domains include the management of entities such as PCs, servers, devices, Web services and other applications manageable entities. Services can expose only a WS-Management interface or compose the WS-Management service interface with some of the many other Web service specifications.
A crucial application for these services is in the area of systems management. To promote interoperability between management applications and managed resources, ISO/IEC PAS 17963:2012 identifies a core set of Web service specifications and usage requirements that expose a common set of operations central to all systems management. This includes the ability to do the following:
a) get, put (update), create, and delete individual resource instances, such as settings and dynamic values;
b) enumerate the contents of containers and collections, such as large tables and logs;
c) subscribe to events emitted by managed resources;
d) execute specific management methods with strongly typed input and output parameters.
In each of these areas of scope, ISO/IEC 17963:2013 defines minimal implementation requirements for conformant Web service implementations. An implementation is free to extend beyond this set of operations, and to choose not to support one or more of the preceding areas of functionality if that functionality is not appropriate to the target device or system.
ISO/IEC 17963:2013 intends to meet the following requirements:
a) constrain Web services protocols and formats so that Web services can be implemented with a small footprint in both hardware and software management services;
b) define minimum requirements for compliance without constraining richer implementations;
c) ensure backward compatibility and interoperability with WS-Management version 1.0;
d) ensure composability with other Web services specifications.
|
Published |
2013-02 |
Edition : 1 |
Number of pages : 208 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC DIS 18974 |
Information technology — OpenChain security assurance specification |
|
Under development |
|
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 19099:2014 |
Information technology — Virtualization Management Specification |
ISO/IEC 19099:2014 specifies the following:
Resource Allocation Profile, which sets the basic resource allocation pattern for resource pools, allocations, and setting data. It also defines the resource-pool-lifecycle management and relationships.
System Virtualization Profile - an autonomous profile that specifies the minimum top-level object model needed for the representation of host systems and the discovery of hosted virtual computer systems. In addition, it specifies a service for the manipulation of virtual computer systems and their resources, including operations for the creation, deletion, and modification of virtual computer systems and operations for the addition or removal of virtual resources to or from virtual computer systems.
Allocation Capabilities Profile, which extends the management capability of referencing profiles by adding the ability to represent the default, supported and range of property values for resource allocation requests for a given resource, and the mutability of properties in a Resource Allocation Setting Data instance.
Processor Resource Virtualization Profile - a component profile that extends the management capabilities of the specialized profiles by adding the support to represent and manage the allocation of processor resources to virtual systems.
Memory Resource Virtualization Profile - a component DMTF management profile that extends the management capabilities of the referencing profile by adding the support to represent and manage the allocation of memory to virtual systems.
Storage Resource Virtualization Profile - a component profile that extends the management capabilities of the referencing profile by adding the support to represent and manage the allocation of storage to virtual systems.
Ethernet Port Resource Virtualization Profile - a component DMTF management profile that extends the management capabilities of the referencing profile by adding the support to represent and manage the allocation of Ethernet ports to virtual systems.
Virtual System Profile - an autonomous profile that defines the minimum object model needed to provide for the inspection of a virtual system and its components. In addition, it defines optional basic control operations for activating, deactivating, pausing, or suspending a virtual system.
Generic Device Resource Virtualization Profile - a concrete component profile that specializes the abstract Resource Allocation Profile and the abstract Allocation Capabilities Profile.
|
Published |
2014-05 |
Edition : 1 |
Number of pages : 416 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 19395:2015 |
Information technology — Sustainability for and by information technology — Smart data centre resource monitoring and control |
ISO/IEC 19395:2015 provides Messages that facilitate integrated or "smart" monitoring and control of Resources in those islands. The Messages are exchanged between the Management Function and Resources. ISO/IEC 19395:2015 acknowledges that those Resources may be composed of other Resources (e.g. a rack may contain servers, ventilators, etc.). In addition, e.g. those servers may be viewed from their computing, energy consumption or dissipation aspects which ISO/IEC 19395:2015 models as Resource Components and groups into IT, power and fluid Domains, respectively.
|
Published |
2015-01 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 20546:2019 |
Information technology — Big data — Overview and vocabulary |
This document provides a set of terms and definitions needed to promote improved communication and understanding of this area. It provides a terminological foundation for big data-related standards.
This document provides a conceptual overview of the field of big data, its relationship to other technical areas and standards efforts, and the concepts ascribed to big data that are not new to big data.
|
Published |
2019-02 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO 4330:1979 |
Photography — Determination of the curl of photographic film |
|
Withdrawn |
1979-04 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
37.040.20
Photographic paper, films and plates. Cartridges
|
| ISO/IEC 19510:2013 |
Information technology — Object Management Group Business Process Model and Notation |
The primary goal of ISO/IEC 19510:2013 is to provide a notation that is readily understandable by all business users, from the business analysts that create the initial drafts of the processes, to the technical developers responsible for implementing the technology that will perform those processes, and finally, to the business people who will manage and monitor those processes. Thus, ISO/IEC 19510:2013 creates a standardized bridge for the gap between the business process design and process implementation.
ISO/IEC 19510:2013 represents the amalgamation of best practices within the business modelling community to define the notation and semantics of Collaboration diagrams, Process diagrams, and Choreography diagrams. The intent of ISO/IEC 19510:2013 is to standardize a business process model and notation in the face of many different modelling notations and viewpoints. In doing so, ISO/IEC 19510:2013 will provide a simple means of communicating process information to other business users, process implementers, customers, and suppliers.
ISO/IEC 19510:2013 is identical to OMG BPMN 2.0.1.
|
Published |
2013-07 |
Edition : 1 |
Number of pages : 507 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 19540-1:2022 |
Information technology — Object Management Group Unified Architecture Framework (OMG UAF) — Part 1: Domain Metamodel (DMM) |
There are four parts to this specification, two are normative and two informative. The normative parts are:
The UAF Domain Metamodel (DMM) (this document) that provides the definition of concepts, relationships and viewpoints for the framework. The UAF DMM is the basis for any implementation of UAF including non-UML/SysML implementations.
The UAF Profile (UAFP) (see document dtc/19-06-15) is a UML/SysML implementation of the UAF DMM
The informative parts are:
The UAF Traceability, Annex A (see document dtc/19-06-17), which details the mappings between the UAF and the various frameworks and languages that contribute to the UAF.
The UAF Example Model, Annex B (see document dtc/19-06-18), which illustrates a practical usage of UAF.
|
Published |
2022-03 |
Edition : 1 |
Number of pages : 212 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 19540-2:2022 |
Information technology — Object Management Group Unified Architecture Framework (OMG UAF) — Part 2: Unified Architecture Framework Profile (UAFP) |
This document is a normative supplement to the UAF DMM document (c4i/19-06-16).
This document specifies a UAF profile to enable practitioners to express architectural model elements and organize them in a set of domains, model kinds, and view specification (specified in the UAF DMM) that support the specific needs of end users in defense and commercial industry.
UAFP 1.1 defines a set of stereotypes and model elements and relationships to satisfy the requirements of the UPDM 3.0 RFP and the UAF DMM. The profile specification documents the language architecture in terms of UML profiling mechanism.
A number of UAFP stereotypes inherit from SysML stereotypes where reuse of SysML semantics is necessary. The reusable portions of the SysML specification are not included directly in the specification but are made explicit through the stereotype inheritance.
|
Published |
2022-03 |
Edition : 1 |
Number of pages : 211 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC TR 19765:2007 |
Information technology — Survey of icons and symbols that provide access to functions and facilities to improve the use of information technology products by the elderly and persons with disabilities |
Different users of information technology products possess different sets of abilities. Some abilities may not ever be present in a user as they may have been born without them. Some abilities are acquired, developed or deteriorate over time due to education, maturity, injury, illness or age. Just as it is possible that a user possesses a combination of abilities, it is also possible that they may lack a combination of abilities.
ISO/IEC TR 19765:2007 presents icons and symbols currently used to provide access to facilities and tools to support the needs of elderly and disabled users of information technology (IT) products, and could form the basis of a future International Standard which would provide a recommended collection of icons and symbols.
These icons and symbols have been collected from a variety of sources including other standards, contemporary software products, web sites and hardware devices. These sources are cross-referenced and listed in a bibliography.
The icons and symbols presented in ISO/IEC TR 19765:2007 are categorized by modality and method of use.
|
Withdrawn |
2007-07 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.080.50
Graphical symbols for use on information technology and telecommunications technical drawings and in relevant technical product documentation
;
11.180.99
Other standards related to aids for disabled and handicapped people
|
| ISO/IEC 19988:2015 |
Information technology — GS1 Core Business Vocabulary (CBV) |
ISO/IEC 19988:2015 This GS1 Standard defines the Core Business Vocabulary (CBV). The goal of this standard is to specify various vocabulary elements and their values for use in conjunction with the EPCIS standard [EPCIS1.1], which defines mechanisms to exchange information both within and across organization boundaries. The vocabulary identifiers and definitions in this standard will ensure that all parties who exchange EPCIS data using the Core Business Vocabulary will have a common understanding of the semantic meaning of that data.
ISO/IEC 19988:2015 is intended to provide a basic capability that meets the above goal. In particular, this standard is designed to define vocabularies that are core to the EPCIS abstract data model and are applicable to a broad set of business scenarios common to many industries that have a desire or requirement to share data. This standard intends to provide a useful set of values and definitions that can be consistently understood by each party in the supply chain.
Additional end user requirements may be addressed by augmenting the vocabulary elements herein with additional vocabulary elements defined for a particular industry or a set of users or a single user. Additional values for the standard vocabulary types defined in this standard may be included in follow-on versions of this standard.
|
Withdrawn |
2015-09 |
Edition : 1 |
Number of pages : 62 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 15041:1997 |
Information technology — Data interchange on 90 mm optical disk cartridges — Capacity: 640 Mbytes per cartridge |
|
Published |
1997-04 |
Edition : 1 |
Number of pages : 126 |
Technical Committee |
35.220.30
Optical storage devices
|
| ISO/IEC 20000-1:2005 |
Information technology — Service management — Part 1: Specification |
ISO/IEC 20000-1:2005 defines the requirements for a service provider to deliver managed services. It is based on BS 15000-2, which has been superseded.
It may be used
by businesses that are going out to tender for their services;to provide a consistent approach by all service providers in a supply chain;to benchmark IT service management;as the basis for an independent assessment;to demonstrate the ability to meet customer requirements; to improve services.
ISO/IEC 20000-1:2005 promotes the adoption of an integrated process approach to effectively deliver managed services to meet business and customer requirements. For an organization to function effectively it has to identify and manage numerous linked activities. Co-ordinated integration and implementation of the service management processes provides the ongoing control, greater efficiency and opportunities for continual improvement.
Organizations require increasingly advanced facilities (at minimum cost) to meet their business needs. With the increasing dependencies in support services and the diverse range of technologies available, service providers can struggle to maintain high levels of customer service. Working reactively, they spend too little time planning, training, reviewing, investigating, and working with customers. The result is a failure to adopt structured, proactive working practices. Those same service providers are being asked for improved quality, lower costs, greater flexibility, and faster response to customers.
In contrast, effective service management delivers high levels of customer service and customer satisfaction. It also recognizes that services and service management are essential to helping organizations generate revenue and be cost-effective. The ISO/IEC 20000 series enables service providers to understand how to enhance the quality of service delivered to their customers, both internal and external.
The ISO/IEC 20000 series draws a distinction between the best practices of processes, which are independent of organizational form or size and organizational names and structures. The ISO/IEC 20000 series applies to both large and small service providers, and the requirements for best practice service management processes are independent of the service provider's organizational form. These service management processes deliver the best possible service to meet a customer's business needs within agreed resource levels, i.e. service that is professional, cost-effective and with risks which are understood and managed.
|
Withdrawn |
2005-12 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-1:2011 |
Information technology — Service management — Part 1: Service management system requirements |
ISO/IEC 20000-1:2011 is a service management system (SMS) standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include the design, transition, delivery and improvement of services to fulfil agreed service requirements.
ISO/IEC 20000-1:2011 can be used by:
an organization seeking services from service providers and requiring assurance that their service requirements will be fulfilled;
an organization that requires a consistent approach by all its service providers, including those in a supply chain;
a service provider that intends to demonstrate its capability for the design, transition, delivery and improvement of services that fulfil service requirements;
a service provider to monitor, measure and review its service management processes and services;
a service provider to improve the design, transition, delivery and improvement of services through the effective implementation and operation of the SMS;
an assessor or auditor as the criteria for a conformity assessment of a service provider's SMS to the requirements in ISO/IEC 20000-1:2011.
|
Withdrawn |
2011-04 |
Edition : 2 |
Number of pages : 26 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-1:2018 |
Information technology — Service management — Part 1: Service management system requirements |
This document specifies requirements for an organization to establish, implement, maintain and continually improve a service management system (SMS). The requirements specified in this document include the planning, design, transition, delivery and improvement of services to meet the service requirements and deliver value. This document can be used by:
a) a customer seeking services and requiring assurance regarding the quality of those services;
b) a customer requiring a consistent approach to the service lifecycle by all its service providers, including those in a supply chain;
c) an organization to demonstrate its capability for the planning, design, transition, delivery and improvement of services;
d) an organization to monitor, measure and review its SMS and the services;
e) an organization to improve the planning, design, transition, delivery and improvement of services through effective implementation and operation of an SMS;
f) an organization or other party performing conformity assessments against the requirements specified in this document;
g) a provider of training or advice in service management.
The term "service" as used in this document refers to the service or services in the scope of the SMS. The term "organization" as used in this document refers to the organization in the scope of the SMS that manages and delivers services to customers. The organization in the scope of the SMS can be part of a larger organization, for example, a department of a large corporation. An organization or part of an organization that manages and delivers a service or services to internal or external customers can also be known as a service provider. Any use of the terms "service" or "organization" with a different intent is distinguished clearly in this document.
|
Published |
2018-09 |
Edition : 3 |
Number of pages : 31 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-2:2005 |
Information technology — Service management — Part 2: Code of practice |
ISO/IEC 20000-2:2005 represents an industry consensus on guidance to auditors and offers assistance to service providers planning service improvements or to be audited against ISO/IEC 20000-1. ISO/IEC 20000-2:2005 is based on BS 15000-2, which has been superseded.
Organizations require increasingly advanced facilities (at minimum cost) to meet their business needs. With the increasing dependencies in support services and the diverse range of technologies available, service providers can struggle to maintain high levels of customer service. Working reactively, they spend too little time planning, training, reviewing, investigating, and working with customers. The result is a failure to adopt structured, proactive working practices. Those same service providers are being asked for improved quality, lower costs, greater flexibility, and faster response to customers.
In contrast, effective service management delivers high levels of customer service and customer satisfaction. It also recognizes that services and service management are essential to helping organizations generate revenue and be cost-effective. The ISO/IEC 20000 series enables service providers to understand how to enhance the quality of service delivered to their customers, both internal and external.
The ISO/IEC 20000 series draws a distinction between the best practices of processes, which are independent of organizational form or size and organizational names and structures. The ISO/IEC 20000 series applies to both large and small service providers, and the requirements for best practice service management processes are independent of the service provider's organizational form. These service management processes deliver the best possible service to meet a customer's business needs within agreed resource levels, i.e. service that is professional, cost-effective and with risks which are understood and managed.
The variety of terms used for the same process, and between processes and functional groups (and job titles) can make the subject of service management confusing to the new manager. Understanding the terminology is a tangible and significant benefit from ISO/IEC 20000.
|
Withdrawn |
2005-12 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20547-1:2020 |
Information technology — Big data reference architecture — Part 1: Framework and application process |
This document describes the framework of the big data reference architecture and the process for how a user of the document can apply it to their particular problem domain.
|
Published |
2020-08 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 9798-3:1998/Cor 2:2012 |
Information technology — Security techniques — Entity authentication — Part 3: Mechanisms using digital signature techniques — Technical Corrigendum 2 |
|
Withdrawn |
2012-03 |
Edition : 2 |
Number of pages : 2 |
Technical Committee |
35.030
IT Security
|
| ISO/IEC 20000-2:2012 |
Information technology — Service management — Part 2: Guidance on the application of service management systems |
ISO/IEC 20000-2:2012 provides guidance on the application of service management systems (SMS) based on the requirements in ISO/IEC 20000-1.
ISO/IEC 20000-2:2012 enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately, and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.
This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation and resources. The SMS provides ongoing control, greater effectiveness, efficiency and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.
|
Withdrawn |
2012-02 |
Edition : 2 |
Number of pages : 85 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-2:2019 |
Information technology — Service management — Part 2: Guidance on the application of service management systems |
This document provides guidance on the application of a service management system (SMS) based on ISO/IEC 20000-1. It provides examples and recommendations to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.
|
Published |
2019-08 |
Edition : 3 |
Number of pages : 63 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-2:2019/Amd 1:2020 |
Information technology — Service management — Part 2: Guidance on the application of service management systems — Amendment 1 |
|
Published |
2020-08 |
Edition : 3 |
Number of pages : 1 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-3:2012 |
Information technology — Service management — Part 3: Guidance on scope definition and applicability of ISO/IEC 20000-1 |
ISO/IEC 20000-3:2012 is useful for service providers, consultants and assessors. It includes practical guidance on scope definition, applicability and demonstration of conformity to the requirements in ISO/IEC 20000-1. Guidance on the different types of conformity assessment and assessment standards is included.
Although the requirements in ISO/IEC 20000-1 do not change with organizational structure, technology or service, operating the processes in a particular service environment will result in specific skill, tool and information requirements. Service management processes can cross many organizational, legal and national boundaries as well as different time zones. Service providers can provide a range of services to several different types of customers, both internal and external. Service providers can also depend on a complex supply chain for the delivery of services. This dependency can make the agreement and application of scope a complex stage in the service provider's use of ISO/IEC 20000-1.
ISO/IEC 20000-3:2012 will assist in establishing if ISO/IEC 20000-1 is applicable to a service provider's circumstances. It illustrates how the scope of an SMS can be defined, irrespective of whether the reader has experience of defining the scope of other management systems. The guidance takes the form of practical examples, typical scenarios and recommendations.
ISO/IEC 20000-3:2012 also assists in planning service improvements and in preparation for a conformity assessment against ISO/IEC 20000-1. It supplements the guidance on the application of ISO/IEC 20000-1 given in ISO/IEC 20000-2.
|
Withdrawn |
2012-08 |
Edition : 1 |
Number of pages : 27 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20000-3:2009 |
Information technology — Service management — Part 3: Guidance on scope definition and applicability of ISO/IEC 20000-1 |
ISO/IEC TR 20000-3:2009 provides guidance on scope definition, applicability and demonstration of conformance for service providers aiming to meet the requirements of ISO/IEC 20000-1, or for service providers who are planning service improvements and intending to use ISO/IEC 20000 as a business goal. It can also assist service providers who are considering using ISO/IEC 20000-1 for implementing a service management system (SMS) and who need specific advice on whether ISO/IEC 20000-1 is applicable to their circumstances and how to define the scope of their SMS.
ISO/IEC TR 20000-3:2009 supplements the advice in ISO/IEC 20000-2, which provides generic guidelines for implementing an SMS in accordance with ISO/IEC 20000-1.
Service providers who wish to implement an SMS based on ISO/IEC 20000-1 are required to define the scope of their SMS. Most service providers are dependent on a complex supply chain for the delivery of the overall service. Most service providers provide a range of services to several different types of customer. This makes the definition of service management scope, and the agreement of the scope statement, a complex stage in the service provider's adoption of ISO/IEC 20000. ISO/IEC TR 20000-3:2009 provides guidance on the applicability of ISO/IEC 20000-1 and scope of the SMS based on practical examples.
ISO/IEC TR 20000-3:2009 takes the form of explanations, guidance and recommendations. It provides practical examples of the scope statements to service providers, irrespective of whether they have any previous experience with other management system standards.
|
Withdrawn |
2009-11 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-3:2019 |
Information technology — Service management — Part 3: Guidance on scope definition and applicability of ISO/IEC 20000-1 |
This document includes guidance on the scope definition and applicability to the requirements specified in ISO/IEC 20000-1.
This document can assist in establishing whether ISO/IEC 20000-1 is applicable to an organization's circumstances. It illustrates how the scope of an SMS can be defined, irrespective of whether the organization has experience of defining the scope of other management systems.
The guidance in this document can assist an organization in planning and preparing for a conformity assessment against ISO/IEC 20000-1.
Annex A contains examples of possible scope statements for an SMS. The examples given use a series of scenarios for organizations ranging from very simple to complex service supply chains.
This document can be used by personnel responsible for planning the implementation of an SMS, as well as assessors and consultants. It supplements the guidance on the application of an SMS given in ISO/IEC 20000-2.
Requirements for bodies providing audit and certification of an SMS can be found in ISO/IEC 20000-6 which recommends the use of this document.
|
Published |
2019-08 |
Edition : 2 |
Number of pages : 28 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO 4330:1987 |
Photography — Determination of the curl of photographic film |
|
Withdrawn |
1987-10 |
Edition : 2 |
Number of pages : 7 |
Technical Committee |
37.040.20
Photographic paper, films and plates. Cartridges
|
| ISO/IEC TR 20000-4:2010 |
Information technology — Service management — Part 4: Process reference model |
The purpose of ISO/IEC TR 20000-4:2010 is to facilitate the development of a process assessment model according to ISO/IEC 15504 process assessment principles. ISO/IEC 15504-1 describes the concepts and terminology used for process assessment. ISO/IEC 15504-2 describes the requirements for the conduct of an assessment and a measurement scale for assessing process capability.
The process reference model provided in ISO/IEC TR 20000-4:2010 is a logical representation of the elements of the processes within service management that can be performed at a basic level. Using the reference model in a practical application might require additional elements suited to the environment and circumstances.
The process reference model specified in ISO/IEC TR 20000-4:2010 describes at an abstract level the processes including the general service management system processes implied by ISO/IEC 20000-1. Each process of this process reference model is described in terms of a purpose and outcomes. The process reference model does not attempt to place the processes in any specific environment nor does it predetermine any level of process capability required to achieve the ISO/IEC 20000-1 requirements. The process reference model is not intended to be used for a conformity assessment audit or process implementation reference guide.
Any organization can define processes with additional elements in order to suit it to its specific environment and circumstances. The purpose and outcomes described in ISO/IEC TR 20000-4:2010 are, however, considered to be the minimum necessary to meet ISO/IEC 20000-1 requirements. Some processes address general strategic aspects of an organization. These processes have been identified in order to give coverage to all the requirements of ISO/IEC 20000-1.
The process reference model does not provide the evidence required by ISO/IEC 20000-1. The process reference model does not specify the interfaces between the processes.
|
Withdrawn |
2010-12 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TS 20000-5:2022 |
Information technology — Service management — Part 5: Implementation guidance for ISO/IEC 20000-1 |
This document provides guidance for organizations on how to implement a service management system (SMS). Organizations can use this document to implement the entire SMS in order to conform to the requirements specified in ISO/IEC 20000-1, or parts of an SMS for a selected subset of requirements. This document illustrates a generic plan to manage implementation activities for an SMS.
The intended users of this document are:
a) organizations that require support on how to implement an SMS;
b) consultants and advisors who support an organization during SMS implementation.
This document can be used together with the other parts of ISO/IEC 20000 series.
|
Published |
2022-01 |
Edition : 1 |
Number of pages : 33 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20000-5:2010 |
Information technology — Service management — Part 5: Exemplar implementation plan for ISO/IEC 20000-1 |
ISO/IEC TR 20000-5:2010 is an exemplar implementation plan providing guidance to service providers on how to implement a service management system to fulfil the requirements of ISO/IEC 20000-1 or for service providers who are planning service improvements and intending to use ISO/IEC 20000 as a business goal. It could also be useful for those advising service providers on how to best achieve the requirements of ISO/IEC 20000-1.
ISO/IEC TR 20000-5:2010 includes advice for service providers on a suitable order in which to plan and implement improvements. It is suggested that a generic three-phase approach is used to implement a service management system. The phased approach provides a structured framework to prioritize and manage the implementation activities.
ISO/IEC TR 20000-5:2010 includes advice on development of a business case, the start up project, and a list of the main activities required to implement ISO/IEC 20000-1 successfully for each phase. It also provides supporting information, advice and guidance that may be useful for the implementation project, including developing objectives, developing policies, document and record management and sample process documentation.
ISO/IEC TR 20000-5:2010 is for guidance only. The service provider has the option of choosing their own implementation sequence to implement a service management system.
|
Withdrawn |
2010-05 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20000-5:2013 |
Information technology — Service management — Part 5: Exemplar implementation plan for ISO/IEC 20000-1 |
ISO/IEC TR 20000-5:2013 is an exemplar implementation plan providing guidance on how to implement a service management system (SMS) to fulfil the requirements of ISO/IEC 20000-1:2011. The intended users of ISO/IEC TR 20000-5:2013 are service providers, but it can also be useful for those advising service providers on how to implement an SMS.
ISO/IEC TR 20000-5:2013 includes advice for service providers on a suitable order in which to plan, implement and improve an SMS using, as an example, a generic three-phased approach to manage the implementation. The service provider can choose their own sequence to implement the SMS. Also included is advice on the development of a business case, the project initiation and other activities that are recommended for the implementation to be successful.
The phases described in ISO/IEC TR 20000-5:2013 do not include changes to the intended scope of the service provider's SMS. The scope itself is not subject to phased changes as a result of adopting the advice in ISO/IEC TR 20000-5:2013. Instead, each phase should improve the SMS in alignment with the service provider's agreed scope, building on the results of the previous phase.
The main activities for the development of the business case and initiation of the implementation project are shown. The main activities to implement the SMS based on ISO/IEC 20000-1:2011, in three phases, are listed. Many of the activities described in ISO/IEC TR 20000-5:2013 are intended to be met by actions over more than one phase, with each phase building upon the achievements of the earlier phase. Once the final phase is completed, the service provider's organization can achieve the benefits of an SMS that meets the requirements in ISO/IEC 20000-1:2011. Supporting information for the SMS implementation project is also provided.
Examples of policies to illustrate what a service provider can want to put in place are provided. Because policies depend on the organization and the strategy of the service provider, these example policies can be tailored to suit the organizational requirement.
Guidance on documentation management is provided, and templates are included for some of the documents specified in ISO/IEC 20000-1:2011 that can be amended to suit individual circumstances.
|
Withdrawn |
2013-11 |
Edition : 2 |
Number of pages : 41 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-6:2017 |
Information technology — Service management — Part 6: Requirements for bodies providing audit and certification of service management systems |
ISO/IEC 20000-6:2017 specifies requirements and provides guidance for certification bodies providing audit and certification of an SMS in accordance with ISO/IEC 20000‑1. It does not change the requirements specified in ISO/IEC 20000‑1. ISO/IEC 20000-6:2017 can also be used by accreditation bodies for accreditation of certification bodies.
A certification body providing SMS certification is expected to be able to demonstrate fulfilment of the requirements specified in ISO/IEC 20000-6:2017, in addition to the requirements in ISO/IEC 17021‑1.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
;
03.120.20
Product and company certification. Conformity assessment
|
| ISO/IEC TR 20000-7:2019 |
Information technology — Service management — Part 7: Guidance on the integration and correlation of ISO/IEC 20000-1:2018 to ISO 9001:2015 and ISO/IEC 27001:2013 |
This document provides guidance on the integrated implementation of a service management system (SMS) as specified in ISO/IEC 20000-1 with a quality management system (QMS) as specified in ISO 9001 and an information security management system (ISMS) as specified in ISO/IEC 27001. It is aimed at those organizations that are intending to either:
a) implement ISO 9001 when ISO/IEC 20000-1 is already implemented, or vice versa;
b) implement ISO/IEC 27001 when ISO/IEC 20000-1 is already implemented, or vice versa;
c) implement both ISO 9001 and ISO/IEC 20000-1 together, or implement both ISO/IEC 27001 and ISO/IEC 20000-1 together;
d) implement ISO/IEC 20000-1, ISO 9001 and ISO/IEC 27001 together; or
e) integrate existing management systems based on ISO/IEC 20000-1, ISO 9001 and ISO/IEC 27001.
In practice, an SMS, QMS or ISMS can also be integrated with other management system standards (MSS), such as ISO 22301 or ISO 55001.
Clause 4 provides an introduction to ISO/IEC 20000-1, the HLS of MSS specified in ISO/IEC Directives Part 1 and considerations for the integration of an MSS.
Clause 5 provides an introduction to ISO 9001, commonalities and differences with ISO/IEC 20000-1 and considerations for the integration of an SMS with a QMS.
Clause 6 provides an introduction to ISO/IEC 27001, commonalities and differences with ISO/IEC 20000-1 and considerations for the integration of an SMS with an ISMS.
Clause 7 looks at considerations for the integration of an SMS, a QMS, and an ISMS.
This document also provides correlation information for the terms and definitions of ISO/IEC 20000-1 with ISO 9001 and ISO/IEC 27001 in Annex A. Correlation of the clauses of ISO/IEC 20000-1 with ISO 9001 is shown in Annex B. Correlation of the clauses of ISO/IEC 20000-1 with ISO/IEC 27001 is shown in Annex C.
|
Withdrawn |
2019-07 |
Edition : 1 |
Number of pages : 57 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20000-9:2015 |
Information technology — Service management — Part 9: Guidance on the application of ISO/IEC 20000-1 to cloud services |
ISO/IEC TR 20000-9:2015 provides guidance on the use of ISO/IEC 20000‑1:2011 for service providers delivering cloud services. It is applicable to different categories of cloud service, such as those defined in ISO/IEC 17788/ITU-T Y.3500 and ISO/IEC 17789/ITU-T Y.3502, including, but not limited to, the following:
a) infrastructure as a service (IaaS);
b) platform as a service (PaaS);
c) software as a service (SaaS).
It is also applicable to public, private, community, and hybrid cloud deployment models.
The applicability of ISO/IEC 20000‑1 is independent of the type of technology or service model used to deliver the services. All requirements in ISO/IEC 20000‑1 can be applicable to cloud service providers.
The structure of ISO/IEC TR 20000-9:2015 does not follow the structure of ISO/IEC 20000‑1. The guidance is presented as a set of scenarios that can address many of the typical activities of a cloud service provider. The guidance in ISO/IEC TR 20000-9:2015 can also be useful for customers of cloud service providers.
This part of ISO/IEC TR 20000-9:2015 can be used as guidance for a cloud service provider in designing, managing, or improving an SMS to support cloud services.
ISO/IEC TR 20000-9:2015 does not add any requirements to those stated in ISO/IEC 20000‑1 and does not state explicitly how evidence can be provided to an assessor or auditor. The scope of ISO/IEC TR 20000-9:2015 excludes any specifications for products or tools.
|
Withdrawn |
2015-02 |
Edition : 1 |
Number of pages : 30 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20000-10:2018 |
Information technology — Service management — Part 10: Concepts and vocabulary |
This document describes the core concepts of ISO/IEC 20000 (all parts), identifying how the different parts support ISO/IEC 20000‑1:2018 as well as the relationships between ISO/IEC 20000-1 and other International Standards and Technical Reports. This document also includes the terminology used in all parts of ISO/IEC 20000, so that organizations and individuals can interpret the concepts correctly.
This document can be used by:
a) organizations seeking to understand the terms and definitions to support the use of ISO/IEC 20000 (all parts);
b) organizations looking for guidance on how to use the different parts of ISO/IEC 20000 to achieve their goal;
c) organizations that wish to understand how ISO/IEC 20000 (all parts) can be used in combination with other International Standards;
d) practitioners, auditors and other parties who wish to gain an understanding of ISO/IEC 20000 (all parts).
|
Published |
2018-09 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20000-10:2013 |
Information technology — Service management — Part 10: Concepts and terminology |
ISO/IEC TR 20000-10:2013 provides an overview of the concepts and the terminology of ISO/IEC 20000. It establishes a common framework for helping organizations to understand the purpose of all the parts of ISO/IEC 20000 and the relationships between the parts. ISO/IEC TR 20000-10:2013 is intended to become the authoritative source for definitions used in all the parts of ISO/IEC 20000. Terms defined in ISO/IEC TR 20000-10:2013 will be removed from other published parts of ISO/IEC 20000 as they are updated.
ISO/IEC TR 20000-10:2013 identifies other documents that have relationships with ISO/IEC 20000-1:2011 and identifies common areas with related International Standards to aid the use and integration of multiple International Standards in organizations.
ISO/IEC TR 20000-10:2013 can be used by any organization or individual involved in the planning, design, transition, delivery and improvement of services using ISO/IEC 20000. More specifically, it:
defines the terms used in ISO/IEC 20000;
promotes cohesion between the parts of ISO/IEC 20000 by explaining the concepts and terminology used across all parts;
contributes to the understanding of ISO/IEC 20000 by clarifying the relationships between all the parts;
clarifies the possible interfaces and integration between the service provider's SMS and other management systems;
provides an overview of other International Standards which can be used in combination with ISO/IEC 20000;
identifies common areas between ISO/IEC 20000-1 and other International Standards.
ISO/IEC TR 20000-10:2013 describes the core concepts of ISO/IEC 20000, identifying how the different parts interact to support ISO/IEC 20000-1:2011. It also describes the relationships between ISO/IEC 20000 and other International Standards and Technical Reports. ISO/IEC TR 20000-10:2013 also explains the terminology used in ISO/IEC 20000, so that organizations and individuals can interpret the concepts correctly.
|
Withdrawn |
2013-11 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20000-10:2015 |
Information technology — Service management — Part 10: Concepts and terminology |
ISO/IEC TR 20000-10:2015 describes the core concepts of ISO/IEC 20000, identifying how the different parts support ISO/IEC 20000‑1:2011 as well as the relationships between ISO/IEC 20000 and other International Standards and Technical Reports. This part of ISO/IEC 20000 also explains the terminology used in ISO/IEC 20000, so that organisations and individuals can interpret the concepts correctly.
ISO/IEC TR 20000-10:2015 is for
a) service providers considering using any part of ISO/IEC 20000 and looking for guidance on how to use the different parts of ISO/IEC 20000 to achieve their goal,
b) service providers that wish to understand how ISO/IEC 20000 can be used in combination with other International Standards, and
c) practitioners, auditors, and other parties who wish to gain an understanding of ISO/IEC 20000.
|
Withdrawn |
2015-11 |
Edition : 2 |
Number of pages : 26 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20547-2:2018 |
Information technology — Big data reference architecture — Part 2: Use cases and derived requirements |
ISO/IEC TR 20547-2:2018 provides examples of big data use cases with application domains and technical considerations derived from the contributed use cases.
|
Published |
2018-01 |
Edition : 1 |
Number of pages : 252 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC TS 20000-11:2021 |
Information technology — Service management — Part 11: Guidance on the relationship between ISO/IEC 20000-1 and service management frameworks: ITIL® |
This document provides guidance on the relationship between ISO/IEC 20000–1 and a commonly used service management framework, ITIL 4. It can be used by any organization or person wishing to understand how ITIL can be used with ISO/IEC 20000–1, including:
a) an organization that has claimed or demonstrated or intends to claim or demonstrate conformity to the requirements specified in ISO/IEC 20000–1 and is seeking guidance on the use of ITIL to establish and improve an SMS and the services;
b) an organization that already uses ITIL and is seeking guidance on how ITIL can be used to support efforts to demonstrate conformity to the requirements specified in ISO/IEC 20000–1;
c) an assessor or auditor who wishes to understand the use of ITIL as a support in achieving the requirements specified in ISO/IEC 20000–1.
Clause 4 describes how ITIL can support the demonstration of conformity to ISO/IEC 20000–1. Clause 5 correlates the ITIL documents to requirements in ISO/IEC 20000–1. The tables in Annex A correlate terms and clauses in ISO/IEC 20000–1 to ITIL and vice versa; the tables in Annex B correlate clauses in ISO/IEC 20000-1 to the ITIL 4 publications and vice versa.
|
Published |
2021-08 |
Edition : 1 |
Number of pages : 53 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20000-11:2015 |
Information technology — Service management — Part 11: Guidance on the relationship between ISO/IEC 20000-1:2011 and service management frameworks: ITIL® |
ISO/IEC TR 20000-11:2015 is a Technical Report that provides guidance on the relationship between ISO/IEC 20000?1:2011 and a commonly used service management framework, ITIL. It can be used by any organization or person wishing to understand how ITIL can be used with ISO/IEC 20000?1:2011, including:
a) a service provider that has demonstrated or intends to demonstrate conformity to the requirements specified in ISO/IEC 20000?1:2011 and is seeking guidance on the use of ITIL to establish and improve an SMS and the services;
c) a service provider that already uses ITIL and is seeking guidance on how ITIL can be used to support efforts to demonstrate conformity to the requirements specified in ISO/IEC 20000?1:2011;
d) an assessor or auditor who wishes to understand the use of ITIL as support to achieve the requirements specified in ISO/IEC 20000?1:2011.
The correlations provided in this part of ISO/IEC 20000 are for ISO/IEC 20000?1:2011 and ITIL?2011.
Clause 4 describes how ITIL can support the demonstration of conformity to ISO/IEC 20000?1:2011. Clause 5 relates chapters in ITIL to clauses in ISO/IEC 20000?1:2011. The tables in Annex A and Annex B relate terms, clauses and processes in ISO/IEC 20000?1:2011 to ITIL.
|
Withdrawn |
2015-12 |
Edition : 1 |
Number of pages : 47 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC TR 20000-12:2016 |
Information technology — Service management — Part 12: Guidance on the relationship between ISO/IEC 20000-1:2011 and service management frameworks: CMMI-SVC |
ISO/IEC TR 20000-12:2016 provides guidance on the relationship between ISO/IEC 20000‑1:2011 and CMMI-SVC V1.3 (through Maturity Level 3). Service providers can refer to this guidance as a cross-reference between the two documents to help them to plan and implement an SMS. An organization employing the practices in the indicated CMMI-SVC process areas can conform to many of the associated ISO/IEC 20000‑1 requirements.
The guidance in Clause 4 describes how CMMI-SVC can support the demonstration of conformity to ISO/IEC 20000‑1:2011. A description of the purpose and content of both publications in 4.1 and 4.2 is followed by Clause 5, which relates process areas in CMMI-SVC to clauses in ISO/IEC 20000‑1:2011. The tables in Annexes A and B relate terms, clauses, and paragraphs in ISO/IEC 20000‑1:2011 to CMMI-SVC. Table B.1 is a simplified summary of the correlation seen in Table 3 for those readers who want an overview. The tables indicate those aspects of ISO/IEC 20000‑1:2011 and CMMI-SVC that represent the greatest link between the two sets of documents, from the perspective of a service provider.
ISO/IEC TR 20000-12:2016 can be used by any organization or person who wishes to understand how CMMI-SVC can be used with ISO/IEC 20000‑1:2011, including the following:
a) a service provider that intends to demonstrate conformity to the requirements of ISO/IEC 20000‑1:2011 and is seeking guidance on the use of CMMI-SVC to establish and maintain the SMS and the services;
b) a service provider that has demonstrated conformity to the requirements of ISO/IEC 20000‑1:2011 and is seeking guidance on ways to use CMMI-SVC to improve the SMS and the services;
c) a service provider that already uses CMMI-SVC and is seeking guidance on how CMMI-SVC can be used to support efforts to demonstrate conformity to the requirements specified in ISO/IEC 20000‑1:2011;
d) an appraiser or assessor who wishes to understand the use of CMMI-SVC as support for the requirements specified in ISO/IEC 20000‑1:2011.
ISO/IEC TR 20000-12:2016 can also be used with the other parts of the ISO/IEC 20000 series.
|
Withdrawn |
2016-10 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC CD TS 20000-14 |
Information technology — Service management — Part 14: Guidance on the application of Service Integration and Management to ISO/IEC 20000-1 |
This TS aims to provide guidance to organizations that manage services in an environment that includes services sourced from multiple service providers through the incorporation of a service integration function and development of service integration and management ecosystem. Service integration and management can be applied to different sizes and types of organizations, and to different industry sectors.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.020
Information technology (IT) in general
;
03.080.99
Other services
|
| ISO/IEC 20005:2013 |
Information technology — Sensor networks — Services and interfaces supporting collaborative information processing in intelligent sensor networks |
ISO/IEC 20005:2013 specifies services and interfaces supporting collaborative information processing (CIP) in intelligent sensor networks which includes:
CIP functionalities and CIP functional model,
common services supporting CIP,
common service interfaces to CIP.
|
Published |
2013-07 |
Edition : 1 |
Number of pages : 44 |
Technical Committee |
35.020
Information technology (IT) in general
;
35.110
Networking
|
| ISO/IEC DIS 20237 |
Information technology — OASIS MQTT-based interoperability specification for the industrial internet of things (IIoT) — Sparkplug® version 3.0 |
|
Under development |
|
Edition : 1 |
Number of pages : 134 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 20547-3:2020 |
Information technology — Big data reference architecture — Part 3: Reference architecture |
This document specifies the big data reference architecture (BDRA). The reference architecture includes concepts and architectural views.
The reference architecture specified in this document defines two architectural viewpoints:
— a user view defining roles/sub-roles, their relationships, and types of activities within a big data ecosystem;
— a functional view defining the architectural layers and the classes of functional components within those layers that implement the activities of the roles/sub-roles within the user view.
The BDRA is intended to:
— provide a common language for the various stakeholders;
— encourage adherence to common standards, specifications, and patterns;
— provide consistency of implementation of technology to solve similar problem sets;
— facilitate the understanding of the operational intricacies in big data;
— illustrate and understand the various big data components, processes, and systems, in the context of an overall big data conceptual model;
— provide a technical reference for government departments, agencies and other consumers to understand, discuss, categorize and compare big data solutions; and
— facilitate the analysis of candidate standards for interoperability, portability, reusability, and extendibility.
|
Published |
2020-03 |
Edition : 1 |
Number of pages : 38 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 20547-4:2020 |
Information technology — Big data reference architecture — Part 4: Security and privacy |
This document specifies the security and privacy aspects applicable to the big data reference architecture (BDRA) including the big data roles, activities and functional components and also provides guidance on security and privacy operations for big data.
|
Published |
2020-09 |
Edition : 1 |
Number of pages : 59 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC TR 20547-5:2018 |
Information technology — Big data reference architecture — Part 5: Standards roadmap |
ISO/IEC TR 20547-5:2018 describes big data relevant standards, both in existence and under development, along with priorities for future big data standards development based on gap analysis.
|
Published |
2018-02 |
Edition : 1 |
Number of pages : 17 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC TR 20913:2016 |
Information technology — Data centres — Guidelines on holistic investigation methodology for data centre key performance indicators |
ISO/IEC TR 20913:2016 describes backgrounds, motivation, and general concept of holistic methodology for data centre key performance indicators (KPIs) to investigate the status of KPIs. It discusses the usefulness of holistic investigation methodology in terms of aggregating a KPI across different contexts, aggregation of two or more KPIs within a single context, aggregation of two or more KPIs across multiple contexts, and aggregation of the multiple KPIs into a single indicator. This document presents a conventional spider web chart-based data centre KPIs status observation method and a control chart method including upper bound and lower bound of the operational status of KPIs. This document presents SWOT analysis results for both methodologies. The methods described in this document are aimed at the self-monitoring of a data centre, not comparison among data centres.
Specifically, ISO/IEC TR 20913:2016
a) describes backgrounds, motivation, and general concept of holistic investigation methodology for data centre KPIs,
b) analyses the usefulness of holistic investigation methodology for aggregating KPIs,
c) describes a spider web chart-based KPIs status observation method and a control chart extending spider web chart to observe the operational status of KPIs,
d) describes alternative and/or additional methods of representing dissimilar KPIs to track holistic resource effectiveness of the data centre, and
e) presents SWOT analysis results for holistic investigation methods described in this document.
|
Published |
2016-11 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 20924:2018 |
Information technology — Internet of Things (IoT) — Vocabulary |
ISO/IEC 20924:2018(E) provides a definition of Internet of Things along with a set of terms and definitions forming a terminology foundation for the Internet of Things
|
Withdrawn |
2018-12 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 20924:2021 |
Information technology — Internet of Things (IoT) — Vocabulary |
ISO/IEC 20924:2021(E) provides a definition of Internet of Things along with a set of terms and definitions. This document is a terminology foundation for the Internet of Things.
|
Published |
2021-03 |
Edition : 2 |
Number of pages : 10 |
Technical Committee |
35.020
Information technology (IT) in general
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC TR 21565:2018 |
Information technology — Office equipment — Viewing environment guideline for office equipment |
ISO/IEC TR 21565:2018 provides an overview of office viewing environment and colour characterization guidelines for use with office equipment, in particular colour printing devices that have digital imaging capabilities, including multi-function devices.
|
Published |
2018-02 |
Edition : 1 |
Number of pages : 17 |
Technical Committee |
35.020
Information technology (IT) in general
|
| ISO/IEC 21823-1:2019 |
Internet of things (IoT) — Interoperability for IoT systems — Part 1: Framework |
ISO/IEC 21823-1:2019(E) provides an overview of interoperability as it applies to IoT systems and a framework for interoperability for IoT systems. This document enables IoT systems to be built in such a way that the entities of the IoT system are able to exchange information and mutually use the information in an efficient way. This document enables peer-to-peer interoperability between separate IoT systems.
This document provides a common understanding of interoperability as it applies to IoT systems and the various entities within them.
|
Published |
2019-02 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.020
Information technology (IT) in general
|