BS ISO IEC 19770-5 pdf download

BS ISO IEC 19770-5 pdf download.Information technology — IT asset management — Overview and vocabulary
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply. 3.1 application system for collecting, saving, processing, and presenting data by means of a computer. [SOURCE: ISO/IEC/IEEE 24765:2010, 3.119, definition 1] 3.2 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 life. Note 2 to entry: 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, licences, 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:2013 incorporated a slightly different definition of asset, taken from a development version of ISO 55000. This definition is sourced from the published version.[SOURCE: ISO 55000:2014, 3.2.1, modified—Note 4 has been added.] 3.3 asset management coordinated activity of an organization to realize value from assets (3.2) [SOURCE: ISO 55000:2014, 3.3.1, modified — The Notes have been deleted.] 3.4 baseline formally approved version of a configuration item (3.7), regardless of media, formally designated and fixed at a specific time during the configuration item’s life cycle [SOURCE: ISO/IEC/IEEE 24765:2010, 3.240, definition 2] 3.5 bundle grouping of products which is the result of a marketing/licensing strategy to sell entitlements to multiple products as one purchased item Note 1 to entry: A bundle can be referred to as a “suite”, if the products are closely related and typically integrated (such as an office suite containing a spreadsheet, word processor, presentation, and other related items). Note 2 to entry: Bundles can also refer to software titles that are less closely related such as a game, a virus scanner and a utility “bundled” together with a new computer, or to groups of entitlements, such as multiple entitlements for a backup software product. 3.6 computing device functional unit that can perform substantial computations, including numerous arithmetic operations and logic operations with or without human intervention Note 1 to entry: A computing device can consist of a stand-alone unit, or several interconnected units. It can also be a device that provides a specific set of functions, such as a phone or a personal organizer, or more general functions such as a laptop or desktop computer. [SOURCE: ISO/IEC/IEEE 24765:2010, 3.513 (computer), modified — “with or” has been added to the definition.]3.7 configuration item CI component of an infrastructure or an item which is or will be, under control of configuration management Note 1 to entry: Configuration items may vary widely in complexity, size and type, ranging from an entire system including all hardware, software and documentation, to a single module or a minor hardware component. Note 2 to entry: Configuration items are commonly defined as part of service management practice and can vary widely in complexity, size, and type, ranging from an entire system including all hardware, software and documentation, to a single module or a minor hardware component. [SOURCE: ISO/IEC/IEEE 24765:2010, 3.563, definition 3, modified — Note 2 to entry has been added] 3.8 configuration management database CMDB database containing all the relevant details of each configuration item (3.7) and details of the important relationships between them Note 1 to entry: When aligning service management with SAM, it may be convenient for the organization to ensure that CIs cover all software within the scope of SAM, i.e. it may be an advantage for anticipated manifestations of controlled/licensed software usage to be fully mapped to CIs and so accountable through all the service management processes using CIs.