ISO/IEC 19770-4:2017 情報技術— IT資産管理—パート4：リソース使用率の測定 | ページ 6

3.1

asset

item, thing, or entity that has potential or actual value to an organization

Note 1 to entry: Value can be tangible or intangible, financial, or non-financial, and includes consideration of risks and liabilities. It can be positive or negative at different stages of the asset's life.

Note 2 to entry: For most organizations, physical assets usually refer to equipment, inventory, and properties owned by the organization. Physical assets are the opposite of intangible assets, which are non-physical assets such as leases, brands, digital assets, use rights, licenses, intellectual property rights, reputation or agreements.

Note 3 to entry: A grouping of assets referred to as an asset system could also be considered as an asset.

Note 4 to entry: ISO/IEC 19770-5 incorporated a slightly different definition of asset, taken from a development version of ISO 55000. This definition is sourced from the latest published version ISO/IEC 19770-5, which is in turn aligned with ISO 55000.

[SOURCE:ISO/IEC 19770‑5:2015, 3.2]

3.2

element

component of an info struct that provides information related to the entity represented by the info struct

[SOURCE:ISO/IEC 19770‑5:2015, 3.12]

3.3

extensible markup language

XML

license-free and platform-independent markup language that carries rules for generating text formats that contain structured data

[SOURCE:W3C Recommendation Extensible Markup Language (XML) 1.1 (Second Edition), 1.2]

3.4

globally unique identifier

GUID

16-byte string of characters that is generated in a manner that gives a high probability that the string is unique in any context

Note 1 to entry: Other globally unique identifier algorithms can be used in some situations. In general, alternative algorithms use uniform resource identifier (URI) based structures, so the id owner's registration identifier (regid) is included in the identifier.

Note 2 to entry: In this document, GUID as an all capitalized term refers specifically to the 16-byte version. If the term is in lowercase (guid), it refers to a general algorithm that can use either a URI, or a 16-byte-based identifier.

[SOURCE:ISO/IEC 19770‑5:2015, 3.16]

3.6

registration identifier

regid

unique identifier for an entity

Note 1 to entry: ISO/IEC 19770-5 incorporated a different definition of regid that defined a specific format.

[SOURCE:ISO/IEC 19770‑5:2015, 3.27]

3.7

software identification tag

SWID tag

information structure (3.13) containing identification information about a software configuration item, which may be authoritative if provided by a software creator

[SOURCE:ISO/IEC 19770‑5:2015, 3.40]

3.8

Resource Utilization Measurement

RUM

structure that provides information about resources associated with an IT asset (3.1) in order to facilitate its management

Note 1 to entry: In the case of a RUM, the structure specifically contains information about the consumption of resources in relation to an IT asset.

[SOURCE:ISO/IEC 19770‑5:2015, 3.18, modified – Note 1 to entry has been added.]

3.9

RUM creator

entity that initially creates a RUM

Note 1 to entry: This entity can be part of the organization that created the IT asset, in which case the RUM creator and IT asset manufacturer will be the same. The RUM creator can also be a third-party organization unrelated to the IT asset manufacturer (such as in the case where tags are created for legacy software by third-party organizations). The RUM creator can also be a separate software tool that is used to measure usage of an IT asset.

[SOURCE:ISO/IEC 19770‑5:2015, 3.19, modified – Note 1 to entry has been added.]

3.10

uniform resource identifier

URI

compact sequence of characters that identifies an abstract or physical resource available on the Internet

Note 1 to entry: The syntax that is used for URIs is defined in IETF RFC 3986.

[SOURCE:IETF RFC 3986, 1]

3.11

valid

status of a RUM that follows the specified XML Schema document and is valid from an XML perspective

[SOURCE:ISO/IEC 19770‑5:2015, 3.52]

3.12

version

unique string of number and letter values indicating a unique revision of an item

Note 1 to entry: Versions are often referred to in software to identify revisions of software that provide unique functionality or fixes. A version typically has multiple parts with at least a major version indicating large changes in functionality or user interface changes and a minor version indicating smaller changes in functionality or user interface changes.

[SOURCE:ISO/IEC 19770‑5:2015, 3.54]

3.13

information structure

structure that provides information about an IT asset (3.1) in order to facilitate its management