Difference between revisions of "Glossary V2"

From EGIWiki
Jump to: navigation, search
imported>Syh
(EGI Glossary)
(Replaced content with "Category:Glossary {{glossary}} The EGI Federation Glossary was migrated to a new dedicated space. Please, use http://go.egi.eu/glossary to refer to it.")
(Tag: Replaced)
Line 1: Line 1:
== EGI Glossary ==
+
[[Category:Glossary]] {{glossary}}
  
EGI Glossary - Version 2 - Approved by the [[GCG|EGI Glossary Coordination Group]] resulting from final changes made July 21, 2015
+
The EGI Federation Glossary was migrated to a new dedicated space.  
 
+
Please, use http://go.egi.eu/glossary to refer to it.
*Major changes were the addition or update of IT service management terms from [http://fitsm.itemo.org/fitsm/0 FitSM-0]
 
*Minor changes (e.g. acronyms)
 
 
 
[https://wiki.egi.eu/wiki/Glossary_V3 Version 3 in progress]
 
 
 
=== Why a Common Glossary  ===
 
 
 
The EGI Community is composed by a large number of heterogenous actors who contribute to providing or consuming services for e-Science. Policy makers produce policies and procedures that govern the EGI processes; dissemination experts write articles for communicating the progress and results in using or evolving EGI; end-users write papers on research results achieved through the infrastructure; technology providers report on the advancement of technology components that enable EGI to operate and so on. From many parties, it has been often expressed the need to identify a common set of terms which definition is agreed and shared so to improve the understanding and consistency of documents. The goal of the EGI Glossary is to address this problem by identifying and maintaining a shared set of terms across all the functional areas of EGI in order to enable a consistent understanding and usage within a well-defined scope. The EGI Glossary is maintained by the [[GCG|EGI Glossary Coordination Group]] who collect feedback from the whole EGI community through the EGI policy boards.
 
 
 
=== How to Reference  ===
 
 
 
*EGI Glossary - latest version: [[Glossary]]
 
*EGI Glossary - Version 2: [[Glossary V2]]
 
*A term definition in the latest EGI Glossary: [[Glossary#TERM_NAME]]
 
*A term definition in the EGI Glossary Version 2: [[Glossary V2#TERM_NAME]]
 
 
 
=== Terms and Definitions  ===
 
 
 
*Where a definition of a term includes another term, those related terms are given initial capitals
 
*The form 'See also Term X, Term Y' is used at the end of a definition where an importan related term is not used with the text of the definition itself<br>
 
 
 
<br>
 
 
 
{| width="100%" border="1" cellpadding="3" cellspacing="0" class="wikitable sortable"
 
|+ '''EGI Glossary'''
 
|-
 
! style="width:300px" scope="col" | Term
 
! align="center" scope="col" | Abbr.
 
! scope="col" | Definition
 
|-
 
! scope="row" | <div id="Acceptable_Use_Policy">[[#Acceptable_Use_Policy|Acceptable Use Policy]]</div>
 
| AUP
 
| A set of terms and conditions applicable to the [[#User|Users]] of an [[#IT_Infrastructure|IT Infrastructure]].
 
|-
 
! scope="row" | <div id="Accessibility_of_Information">[[#Accessibility_of_information|Accessibility of information]]</div>
 
|
 
| Property of information being accessible and usable by an authorised party
 
|-
 
! scope="row" | <div id="Accounting_Record">[[#Accounting_Record|Accounting Record]]</div>
 
|
 
| An entry in an accounting database identifying the quantitative usage of [[#Resource|Resources]] by [[#User|Users]].
 
|-
 
! scope="row" | <div id="Activity">[[#Activity|Activity]]</div>
 
|
 
| Set of actions carried out within a [[#Process|Process]].
 
|-
 
! scope="row" | <div id="Appliance">[[#Appliance|Appliance]]</div>
 
|
 
| A predefined collection of software [[#Product|Products]] that are deployed together so that it appears as a single undividable [[#Service|Service]] or application that implements one or more [[#Capability|IT Capabilities]].
 
|-
 
! scope="row" | <div id="Assessment">[[#Assessment|Assessment]]</div>
 
|
 
| Set of actions to evaluate the level of [[#Capability|Capability]] of a [[#Process|Process]] or the overall maturity of a [[#Management_System|Management System]].
 
|-
 
! scope="row" | <div id="Audit">[[#Audit|Audit]]</div>
 
|
 
| Systematic, independent and documented [[#Process|Process]] for obtaining [[#Audit|Audit]] evidence and evaluating it objectively to determine the extent to which the audit criteria are fulfilled. <br>Note 1: Typical forms of audit evidence include documented information, information provided during an audit interview, and information gathered through observation.<br>Note 2: Audit criteria may be taken from or based on requirements from a management system (including policies, processes and procedures), agreements (including service level agreements and underpinning agreements), contracts, standards or legislation.<br>Note 3: An audit may be an internal audit, if it is conducted under the direct responsibility of the organisation or federation that is subject to the audit, or an external audit, if it is conducted by an external party.<br>Note 4: Both internal and external audits should be conducted by skilled and experienced auditors, and auditors should not audit their own work or areas of responsibilities to ensure the impartiality of the results.
 
|-
 
! scope="row" | <div id="Availability">[[#Availability|Availability]]</div>
 
| <br>
 
| Ability of a [[#Service|Service]] or [[#Service_Component|service component]] to fulfil its intended function at a specific time or over a specific period of time.
 
|-
 
! scope="row" | <div id="Business_Model">[[#Business_Model|Business Model]]</div>
 
|
 
| The rationale of how an organisation creates, delivers, and captures [[#Value|Value]]. The [[#Process|Process]] of business model construction is part of business strategy. The term business model is used for a broad range of informal and formal descriptions to represent core aspects of a business, including purpose, offerings, strategies, infrastructure, organizational structures, trading practices, and operational [[#Processes|processes]] and [[#Polices|policies]].
 
|-
 
! scope="row" | <div id="Capability_level">[[#Capability_Level|Capability level]]</div>
 
|
 
| Achieved level of [[#Effectiveness|effectiveness]] of an individual [[#Process|process]] or general aspect of management
 
|-
 
! scope="row" | <div id="Capacity">[[#Capacity|Capacity]]</div>
 
|
 
| The maximum extent to which a certain element of the infrastructure (such as a [[#Configuration_Item|Configuration Item]]) can be used.<br>Note: This might mean the total disk capacity or network bandwidth. It could also be the maximum ability of a system to process requests.
 
|-
 
! scope="row" | <div id="Change">[[#Change|Change]]</div>
 
|
 
| Alteration (such as addition, removal, modification, replacement) of a [[#Configuration_Item|Configuration Item (CI)]]&nbsp;
 
|-
 
! scope="row" | <div id="Certified_Resource_Centre">[[#Certified_Resource_Centre|Certified Resource Centre]]</div>
 
| CRC
 
| A [[#Resource_Centre|Resource Centre]] that conforms to the requirements specified in the [[PROC09|Resource Centre Registration and Certification Procedure]].
 
|-
 
! scope="row" | <div id="Classification">[[#Classification|Classification]]</div>
 
|
 
|
 
Assignment of items to defined groups based on common attributes, relations or other criteria
 
 
 
Note 1: Items that are subject to classification may include documents, records (such as incident records or change records), services, configuration items (CIs), etc. Defined groups may include categories (such as incident categories or change categories) or priority levels.
 
 
 
Note 2: The act of classification often comprises the application of more than one classification scheme. For instance, an incident record might be assigned to a technical incident category such as ‘software related’, ‘network related’, etc., and also to a priority level like ‘low priority’, ‘medium priority’, etc. The assignment of various incidents, service requests, changes and problems to an affected CI is also a classification.
 
 
 
Note 3: Besides the presentation and analysis of relationships, classification is often used as input for controlling the workflow of a process, e.g. by assigning a priority level to an incident.
 
 
 
|-
 
! scope="row" | <div id="Closure">[[#Closure|Closure]]</div>
 
|
 
| Final activity in a workflow of a process to indicate no further action is required for a specific case
 
Note: Cases that are subject to closure may include incidents, problems, service requests or changes. The activity of closure puts the connected record (such as the incident record, problem record, service request record or change record) in its final status, usually called ‘closed’.
 
 
 
|-
 
! scope="row" | <div id="Cloud_Computing">*[[#Cloud_Computing|Cloud Computing]]</div>
 
|
 
| A model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model is composed of five essential characteristics (on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service), three service models (Software as a Service or SaaS, Platform as a Service or PaaS, Infrastructure as a Service or IaaS), and four deployment models (private cloud, community cloud, public cloud, hybrid cloud). (''Source'': [http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf NIST])
 
|-
 
! scope="row" | <div id="Collaboration_Platform">[[#Collaboration_Platform|Collaboration Platform]]</div>
 
|
 
| A [[#Platform|Platform]] deployed on top of an [[#Infrastructure_Platform|Infrastructure Platform]] providing [[#Capability|Capabilities]] useful across multiple (if not all) research communities irrespective of their scientific domain and enabling the collaboration within and across communities.
 
|-
 
! scope="row" | <div id="Community_Platform">[[#Community_Platform|Community Platform]]</div>
 
|
 
| A [[#Platform|Platform]] that provides a set of [[#Service|Services]] customised for the needs of a specific community to enable their [[#User|Users]] to run specific applications.
 
|-
 
! scope="row" | <div id="Competence">*[[#Competence|Competence]]</div>
 
|
 
| A set of expert or technical knowledge, personal skills, and experience that an individual, group or team needs to effectively take on a specific [[#Role|Role]].
 
|-
 
! scope="row" | <div id="Compliance">*[[#Compliance|Compliance]]</div>
 
|
 
| Extent to which requirements are met in some context.
 
|-
 
! scope="row" | <div id="Confidentiality_of_information">*[[#Confidentiality_of_information|Confidentiality of information]]</div>
 
|
 
| Property of information not being made accessible or disclosed to unauthorised entities.
 
|-
 
! scope="row" | <div id="Configuration_Baseline">*[[#Configuration_Baseline|Configuration Baseline]]</div>
 
|
 
| The state of a specified set of [[#Configuration_Item|Configuration Items]] at a given point in time.
 
|-
 
! scope="row" | <div id="Configuration_Item">*[[#Configuration_Item|Configuration Item]]</div>
 
| CI
 
| Element that contributes to the delivery of one or more [[#Service|Services]] or [[#Service_Component|Service Components]], and therefore needs to be controlled.<br>Note: CIs vary widely and can be anything from technical components (computer hardware, network&nbsp;<span style="line-height: 1.5em; font-size: 13.2799997329712px;">components, cables, software) to documents (SLAs, manuals, contracts, license documentation).</span>
 
|-
 
! scope="row" | <div id="Configuration_Management_Database">*[[#Configuration_Management_Database|Configuration management database]]</div>
 
| CMDB
 
| Store for data about [[#Configuration_Item|Configuration Items]] (therefore configuration data).<br>Note: The CMDB likely includes attributes of CIs as well as information on relationships between CIs, service components and services.
 
|-
 
! scope="row" | <div id="Continuity">*[[#Continuity|Continuity]]</div>
 
|
 
| Ability of a [[#Service|Service]] to operate for extended periods of time and to survive, to the best of a provider's ability, unexpected or even potentially disastrous occurrences.
 
|-
 
! scope="row" | <div id="Customer">*[[#Customer|Customer]]</div>
 
|
 
| The organisation or part of an organisation that commissions a [[#Service_Provider|Service Provider]] in order to receive one or more [[#Services|Services]]. A customer usually represents a number of [[#User|Users]].
 
|-
 
! scope="row" | <div id="Document">*[[#Document|Document]]</div>
 
|
 
| Information and its supporting medium.<br>Note: Examples of documents include [[#Policy|Policies]], plans, [[#Process|Process]] descriptions, [[#Procedure|Procedures]], [[#Service_Level_Agreements|SLAs]], [[#Underpinning_Contracts|Contracts]] or [[#Record|Records]] of activities to be preformed.
 
|-
 
! scope="row" | <div id="Effectiveness">*[[#Effectiveness|Effectiveness]]</div>
 
|
 
| Extent to which the goals or expectations connected to a [[#Process|Process]] or [[#Activity|Activity]] are met.
 
|-
 
! scope="row" | <div id="Efficiency">*[[#Efficiency|Efficiency]]</div>
 
|
 
| The degree of ability to accomplish the goal of a [[#Process|Process]] or [[#Activity|Activity]] with a minimum consumption of [[#Resource|Resources]].<br>Note: Resources may be human, technical, informational or financial.
 
|-
 
! scope="row" | <div id="Escalation">*[[#Escalation|Escalation]]</div>
 
|
 
| Change of responsibility for an event (such as an [[#Incident|Incident]] or [[#Problem|Problem]]) and/or [[#Activity|Activity]] to another individual or group.<br>Note: This might be functional escalation (to someone with specific responsibility, competence or access to information / knowledge) or hierarchical escalation (to someone with a higher level of authority).
 
|-
 
! scope="row" | <div id="e-Infrastructure">[[#e-Infrastructure|e-Infrastructure]]</div>
 
|
 
| An [[#IT_Infrastructure|IT Infrastructure]] for instant access to data, remote instruments, "[[#In_Silico|In Silico]]" experimentation, as well as the setup of [[#Virtual_Research_Community|Virtual Research Communities]] and/or [[#Virtual_Organisation|Virtual Organisations]] that is composed by one or more autonomous (maintaining their own [[#Policy|Policies]]).
 
|-
 
! scope="row" | <div id="EGI-Engage">*[[#EGI-Engage|EGI-Engage]]</div>
 
|
 
| A 30-month project, co-funded by the European Commission’s Horizon 2020 Programme (contract number: RI-654142) "Engaging the Research Community towards an Open Science Commons". The project aims to accelerate the implementation of the Open Science Commons by expanding the capabilities of a European backbone of federated services for compute, storage, data, communication, knowledge and expertise, complementing community-specific capabilities.
 
|-
 
! scope="row" | <div id="EGI-InSPIRE">[[#EGI-InSPIRE|EGI-InSPIRE]]</div>
 
|
 
| A four-year project, co-funded by the European Commission’s 7th Framework Programme (contract number: RI-261323), helping to establish a sustainable, reliable [[#e-Infrastructure|e-Infrastructure]] that can support researchers’ needs for large-scale data analysis.
 
|-
 
! scope="row" | <div id="EGI.eu">[[#EGI.eu|EGI.eu]]</div>
 
|
 
| A non-profit organisation based in Amsterdam established to coordinate and manage the infrastructure [[#European_Grid_Infrastructure|(EGI)]] on behalf of its participants: [[#National_Grid_Initiative|National Grid Initiatives (NGIs)]] and [[#European_Intergovernmental_Research_Organisation|European Intergovernmental Research Organisations (EIROs)]].
 
|-
 
! scope="row" | <div id="European_Grid_Infrastructure">[[#European_Grid_Infrastructure|European Grid Infrastructure]]</div>
 
| EGI
 
| A federation of shared computing, storage and data resources from [[#National_Grid_Infrastructure|national]] and [[#European_Intergovernmental_Research_Organisation|intergovernmental]] resource providers that delivers sustainable, integrated and secure distributed computing services to European researchers and their international partners.
 
|-
 
! scope="row" | <div id="European_Intergovernmental_Research_Organisation">[[#European_Intergovernmental_Research_Organisation|European Intergovernmental Research Organisation]]</div>
 
| EIRO
 
| A legal organisation and member of the EIROforum that has extensive expertise in the areas of basic research and the management of large, international infrastructures, facilities and research programmes.
 
|-
 
! scope="row" | <div id="European_Research_Area">[[#European_Research_Area|European Research Area]]</div>
 
| ERA
 
| A unified research area open to the world based on the Internal Market, in which researchers, scientific knowledge and technology circulate freely and through which the Union and its Member States strengthen their scientific and technological bases, their competitiveness and their capacity to collectively address grand challenges.
 
|-
 
! scope="row" | <div id="Federation_Member">*[[#Federation_Member|Federation Member]]</div>
 
|
 
| Individual, organisation or body that works together with other federation members to provide a [[#Service|Service]] in a federated environment.<br>Note: Typically, federation members will not necessarily be bound together by strict, financial, legal or hierarchical agreements as they might be in traditional service provision.
 
|-
 
! scope="row" | <div id="Federator">*[[#Federator|Federator]]</div>
 
|
 
| Body that acts to coordinate a set of [[#Federation_Member|Federation Members]] in some way.<br>Note: The ways and extent in which they do so may vary widely, from a very loose central body to a fully integrated system with strong central control.
 
|-
 
! scope="row" | <div id="Grid">[[#Grid|Grid]]</div>
 
|
 
| [[#IT_Infrastructure|IT Infrastructure]] that is concerned with the integration, virtualisation, and management of [[#Service|Services]] and [[#Resource|Resources]] in a distributed, heterogeneous environment that supports collections of [[#User|Users]] and resources ([[#Virtual_Organisation|Virtual Organisations]]) across traditional administrative, trust and organisational boundaries (real organisations). (''Source: ''OGF GFD-I.181)
 
|-
 
! scope="row" | <div id="High_Performance_Computing">[[#High_Performance_Computing|High Performance Computing]]</div>
 
| HPC
 
| A computing paradigm that focuses on the efficient execution of compute intensive, tightly-coupled tasks. Given the high parallel communication requirements, the tasks are typically executed on low latency interconnects which makes it possible to share data very rapidly between a large numbers of processors working on the same problem. HPC systems are delivered through low latency clusters and supercomputers and are typically optimised to maximise the number of operations per seconds. The typical metrics are FLOPS, tasks/s, I/O rates.
 
|-
 
! scope="row" | <div id="High_Throughput_Computing">[[#High_Throughput_Computing|High Throughput Computing]]</div>
 
| HTC
 
| A computing paradigm that focuses on the efficient execution of a large number of loosely-coupled tasks. Given the minimal parallel communication requirements, the tasks can be executed on clusters or physically distributed resources using grid technologies. HTC systems are typically optimised to maximise the throughput over a long period of time and a typical metric is jobs per month or year.
 
|-
 
! scope="row" | <div id="In_Silico">[[#In_Silico|In Silico]]</div>
 
|
 
| An expression used to mean 'performed on computer or via computer simulation'. (''Source:'' Wikipedia)
 
|-
 
! scope="row" | <div id="Incident">*[[#Incident|Incident]]</div>
 
|
 
| Any event which is not part of the standard operation of a [[#Service|Service]] and which causes or may cause an interruption to, or a reduction in, the [[#Quality_of_Service|quality of that service]]. (''Source:&nbsp;''ISO 20000-1)<br>Unplanned disruption of operation in a service or service component, or degradation of service quality versus the expected or agreed service level or operational level according to [[#Service_Level_Agreements|Service Level Agreements (SLAs)]], [[#Operational_Level_Agreements|Operational Level Agreements (OLAs)]] and [[#Underpinning_Agreements|Underpinning Agreements (UAs)]] with&nbsp;<span style="line-height: 1.5em; font-size: 13.2799997329712px;">suppliers. (FitSM-0:2015)</span>
 
|-
 
! scope="row" | <div id="Information_Security">*[[#Information_Security|Information Security]]</div>
 
|
 
| Preservation of confidentiality, integrity and accessibility of information.
 
|-
 
! scope="row" | <div id="Information_Security_Control">*[[#Information_Security_Control|Information Security Control]]</div>
 
|
 
| A means of controlling or managing one or more risks to [[#Information_Security|Information Security]].
 
|-
 
! scope="row" | <div id="Information_Security_Event">*[[#Information_Security_Event|Information Security Event]]</div>
 
|
 
| An occurrence or previously unknown situation indicating a possible breach of [[#Information_Security|Information Security]].<br>Note: An occurrence or situation is considered a potential breach of information security if it may lead to a negative impact on the confidentiality, integrity and/or accessibility of one or more information assets.
 
|-
 
! scope="row" | <div id="Information_Security_Incident">*[[#Information_Security_Incident|Information Security Incident]]</div>
 
|
 
| Single [[#Information_Security_Event|Information Security Event]] or a series of information security events with a significant probability of having a negative impact on the delivery of [[#Services|Services]] to customers, and therefore on the customers’ business operations.
 
|-
 
! scope="row" | <div id="Infrastructure_Platform">[[#Infrastructure_Platform|Infrastructure Platform]]</div>
 
|
 
| A [[#Platform|Platform]] that enables flexible and efficient provisioning of IT resources irrespective of the [[#User|User’s]] actual use of those [[#Resource|Resources]]. It forms the foundation layer to develop [[#Community_Platform|Community]] and [[#Collaboration_Platform|Collaboration]] Platforms to be built on top of it.
 
|-
 
! scope="row" | <div id="Integrity_of_information">*[[#Integrity_of_information|Integrity of information]]</div>
 
|
 
| Property of information being protected from unauthorised modification, duplication or deletion.
 
|-
 
! scope="row" | <div id="Interoperability">[[#Interoperability|Interoperability]]</div>
 
|
 
| The ability of systems, people and organisations to provide [[#Service|Services]] to and accept services from other systems, people and organisations and to use the services so exchanged to enable them to operate effectively together.
 
|-
 
! scope="row" | <div id="IT_Capability">[[#IT_Capability|IT Capability]]</div>
 
|
 
| See [[#Capability|Capability]].
 
|-
 
! scope="row" | <div id="IT_Infrastructure">[[#IT_Infrastructure|IT Infrastructure]]</div>
 
|
 
| All of the hardware, software, networks, facilities, etc. that are required to develop, test, deliver, monitor, control or support applications and [[#IT_Service|IT Services]]. The term includes all of the information technology but not the associated people, [[#Process|Processes]] and [[#Document|Documentation]]. (''Source'': ITIL 2011)
 
|-
 
! scope="row" | <div id="IT_Service">[[#IT_Service|IT Service]]</div>
 
|
 
| A service provided by an [[#Service_Provider|IT Service Provider]] like a [[#Resource_Centre|Resource Centre]] or a [[#Resource_infrastructure_Provider|Resource infrastructure Provider]]. An IT service is made up of a combination of information technology, people and [[#Process|Processes]]. A user-facing IT service directly supports the business processes of one or more [[#User|Users]] and its [[#Service_Level_Target|Service Level Targets]] should be defined in a [[#Service_Level_Agreement|Service Level Agreement]]. Other IT services, called supporting services, are not directly used by the business but are required by the service provider to deliver user-facing services. (''Source: ''ITIL 2011 adapted)<br>A service that is enabled by the use of information technology (IT) (FitSM-0:2015)
 
|-
 
! scope="row" | <div>*[[#IT_Service_Management|IT Service Management]]</div>
 
| ITSM
 
| The entirety of [[#Activity|Activities]] performed by an IT service provider to plan, deliver, operate and control IT services offered to customers.<br>Note: The activities carried out in the ITSM context should be directed by [[#Policy|Policies]] and structured and organised by [[#Process|Processes]] and supporting [[#Procedures|Procedures]].
 
|-
 
! scope="row" | <div id="Key_Performance_Indicator">*[[#Key_Performance_Indicator|Key Performance Indicator]]</div>
 
| KPI
 
| Metric that is used to track the performance, [[#Effectiveness|Effectiveness]] or [[#Efficiency|Efficiency]] of a [[#Service|Service]] or [[#Process|Process]].<br>Note: KPIs are generally important metrics that will be aligned to critical success factors and important goals. KPIs are therefore a subset of all possible metrics, intended to allow for monitoring and correcting/improving the effectiveness and/or efficiency of a system or [[#Process|Process]].
 
|-
 
! scope="row" | <div id="Known_Error">*[[#Known_Error|Known Error]]</div>
 
|
 
| [[#Problem|Problem]] which has not (yet) been corrected, but for which there is a documented workaround or temporary fix to prevent (excessive) negative impact on services.
 
|-
 
! scope="row" | <div id="Management_System">*[[#Management_System|Management System]]</div>
 
|
 
| Entirety of policies, processes, procedures and related resources and capabilities aiming at effectively performing management tasks in a given context and for a given subject.<br>Note 1: A management system is generally intangible. It is based on the idea of a systematic, structured and process-oriented way of managing.<br>Note 2: While documentation (such as process definitions, procedures and records) and tools (such as workflow support and monitoring tools) can be parts of a management system, management system considerations are not limited to the questions of documentation and tool support.<br>Note 3: In the context of (IT) service management and the FitSM standard series, the idea of a service management system (SMS) is a central concept, where the context of the management system is the organisational context of the service provider, and the subject is to plan, deliver, operate and control (IT) services.
 
|-
 
! scope="row" | <div id="Maturity">*[[#Maturity|Maturity]]</div>
 
|
 
| The overall ability of a [[#Service_Provider|Service Provider]] to manage their [[#Service|Services]], made up by the combination of their [[#Capability|Capabilities]] in different specific areas.
 
|-
 
! scope="row" | <div id="Memorandum_of_Understanding">[[#Memorandum_of_Understanding|Memorandum of Understanding]]</div>
 
| MoU
 
| An agreement that clarifies the relationships, responsibilities and communication channels between two or more parties that may share [[#Service|Services]], clients, and [[#Resource|Resources]]. The MoU is used when both parties do not want to pursue a Contract that is legally binding (generally). Formal contracts can be intimidating therefore MoUs are the better option for some communities. However, it can also be used to regulate the relationship between parties.
 
|-
 
! scope="row" | <div id="National_Grid_Infrastructure">[[#National_Grid_Infrastructure|National Grid Infrastructure]]</div>
 
| NGI
 
| The national federation of shared computing, storage and data resources that delivers sustainable, integrated and secure distributed computing services to the national research communities and their international collaborators. The federation is coordinated by a [[#NGI_Coordinating_Body|National Coordinating Body]] providing a single point of contact at the national level and has official membership in the EGI Council through an [[#NGI_Legal_Representative|NGI legal representative]].
 
|-
 
! scope="row" | <div id="NGI_Coordinating_Body">[[#NGI_Coordinating_Body|NGI Coordinating Body]]</div>
 
|
 
| An organisation that has the exclusive responsibility for strategic decisions and overall management of a [[#National_Grid_Infrastructure|National Grid Infrastructure]]. The organisation can perform or delegate the [[#Role|Role]] of [[#NGI_Legal_Representative|NGI legal representative]].
 
|-
 
! scope="row" | <div id="NGI_Legal_Representative">[[#NGI_Legal_Representative|NGI Legal Representative]]</div>
 
|
 
| The legal organisation that has the exclusive mandate delegated through the [[#NGI_Coordinating_Body|National Coordinating Body]] to legally represent an [[#National_Grid_Infrastructure|NGI]] at the national and international level and serves as the NGI representative member in the EGI Council. The NGI Legal Representative may also perform the function of the [[#NGI_Coordinating_Body|National Coordinating Body]].
 
|-
 
! scope="row" | <div id="Nonconformity">*[[#Nonconformity|Nonconformity]]</div>
 
|
 
| A case or situation where a requirement is not fulfilled.<br>Note: This may also be referred to as noncompliance.
 
|-
 
! scope="row" | <div id="Open_ICT_Ecosystem">[[#Open_ICT_Ecosystem|Open ICT Ecosystem]]</div>
 
|
 
| An ICT ecosystem is open when it is capable of incorporating and sustaining [[#Interoperability|Interoperability]], collaborative development and transparency, while increasing capacities to create flexible, service-oriented ICT applications that can be taken apart and recombined to meet changing needs more efficiently and effectively.
 
|-
 
! scope="row" | <div id="Open_Science">[[#Open_Science|Open Science]]</div>
 
|
 
| The umbrella term of the movement to make scientific research, data and dissemination accessible to all levels of an inquiring society, amateur or professional. It encompasses practices such as publishing open research, campaigning for open access, encouraging scientists to practice open notebook science, and generally making it easier to publish and communicate scientific knowledge. (''Source:'' Wikipedia)
 
|-
 
! scope="row" | <div id="Open_Standard">[[#Open_Standard|Open Standard]]</div>
 
|
 
| A standard is open if meets the following criteria: All stakeholders have the same possibility of contributing to the development of the specification and public review is part of the decision-making process; The specification is available for everybody to study; Intellectual Property Rights related to the specification are licensed on FRAND (Fair, Reasonable, and Non-Discriminatory) or royalty-free terms in a way that allows implementation in both proprietary and open source software.
 
|-
 
! scope="row" | <div id="Operational_Level_Agreement">*[[#Operational_Level_Agreement|Operational Level Agreement]]</div>
 
| OLA
 
| An agreement between an [[#Service_Provider|IT Service Provider]] and another part of the same organisation. An OLA supports the IT Service Provider’s delivery of [[#IT_Service|IT Services]] to [[#Users|Users]]. The OLA defines the goods or [[#Service|Services]] to be provided and the responsibilities of both parties.(EGI V1)<br>Documented agreement between a [[#Service_Provider|IT Service Provider]] or [[#Federation_Member|Federation Member]] and another part of the service provider’s organisation or the Federation to provide a [[#Service_Component|Service Component]] or subsidiary service needed to allow provision of services to [[#Customer|Customers]].(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Operational_Target">*[[#Operational_Target|Operational Target]]</div>
 
|
 
| Reference/target [[#Value|Values]] for parameters that are used to measure the performance of a [[#Service_Component|Service Component]], and that are listed in an [[#Operational_Level_Agreement|Operational Level Agreement]] or [[#Underpinning_Agreement|Underpinning Agreement]] related to this service component.<br>Note: typical operational targets might include [[#Availability|Availability]] or resolution time for [[#Incident|Incidents]], though many hard and soft targets can be considered.
 
|-
 
! scope="row" | <div id="Operations_Centre">[[#Operations_Centre|Operations Centre]]</div>
 
|
 
| A centre offering operations services on behalf of one or more [[#Resource_Infrastructure_Provider|Resource Infrastructure Providers]].
 
|-
 
! scope="row" | <div id="Package">[[#Package|Package]]</div>
 
|
 
| A structured software unit suitable for automated installation on a computer. A Package may specify dependencies on other packages, so that either a specific version of that package, or a minimum version of that package may satisfy that dependency.
 
|-
 
! scope="row" | <div id="Platform">[[#Platform|Platform]]</div>
 
|
 
| An IT system composed by hardware and/or software components providing a compatibility layer that enables upper-level platforms or user applications to run.
 
|-
 
! scope="row" | <div id="Platform_Integrator">[[#Platform_Integrator|Platform Integrator]]</div>
 
|
 
| A [[#Service_Provider|Service Provider]] that brings together software components from different [[#Technology_Provider|Technology Providers]] or use external services (e.g. from the [[#Collaboration_Platform|Collaboration Platform]]) to meet the needs of a particular consuming research community.
 
|-
 
! scope="row" | <div id="Platform_Operator">[[#Platform_Operator|Platform Operator]]</div>
 
|
 
| A [[#Service_Provider|Service Provider]] that ensures the [[#Service|Services]] deployed as part of an [[#IT_Infrastructure|Infrastructure]] or [[#Community_Platform|Community Platform]] are operating effectively on the distributed resources for their consuming community.
 
|-
 
! scope="row" | <div id="Policy">*[[#Policy|Policy]]</div>
 
|
 
| Clear, formal and mandatory statement and position of general nature adopted by the IT Infrastructure governance bodies.(EGI V1)<br>Documented set of intentions, expectations, goals, rules and requirements, often formally expressed by [[#Top_Management|Top Management]] representatives in an organisation or federation.<br>Note: Policies are then realised in [[#Process|Processes]], which are in turn made up of [[#Activities|Activities]] that people carry out according to [[#Procedure|Procedures]].(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Policy_Development_Process">[[#Policy_Development_Process|Policy Development Process]]</div>
 
| PDP
 
| The process for the review, approval and revision of [[#Policy|Policies]] and [[#Procedure|Procedures]].
 
|-
 
! scope="row" | <div id="Post_Implementation_Review">*[[#Post_Implementation_Review|Post implementation review]]</div>
 
|
 
| Review after the implementation of a change that determines if the change was successful.<br>Note: Depending on the specific type and complexity of the change, the post implementation review may vary widely in its depth.
 
|-
 
! scope="row" | <div id="Priority">*[[#Priority|Priority]]</div>
 
|
 
| Relative importance of a target, object or activity.<br>Note: Often [[#Incident|Incidents]], [[#Service_Requests|Service Requests]], [[#Problem|Problems]] and [[#Change|Changes]] are given a priority. In the case of incidents and problems, priority is usually based on the specific impact and urgency of the situation.
 
|-
 
! scope="row" | <div id="Problem">*[[#Problem|Problem]]</div>
 
|
 
| Unknown underlying cause of one or more [[#Incident|Incidents]]. (''Source:'' ISO 20000-1)<br>The underlying cause of one or more [[#Incident|Incidents]]&nbsp;that requires further investigation to prevent incidents from recurring or reduce the impact on [[#Services|Services]].(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Procedure">*[[#Procedure|Procedure]]</div>
 
|
 
| Step by step written and approved specification of how to complete a specific task or [[#Process|Process]].(EGI V1)<br>Specified set of steps or instructions to be carried out by an individual or team to perform one or more activities of a [[#Process|Process]].(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Process">*[[#Process|Process]]</div>
 
|
 
| A structured set of [[#Activity|Activities]] designed to accomplish a specific objective. A [[#Process|Process]] takes one or more defined inputs and turns them into defined outputs. It may include any of the [[#Role|Roles]], responsibilities, tools and management controls required to reliably deliver the outputs. A [[#Process|Process]] may define [[#Policy|Policies]], [[#Standard|Standards]], guidelines, activities and work instructions if they are needed. (''Source:'' ITIL 2011)<br>Structured set of [[#Activity|Activities]], with clearly defined responsibilities, that bring about a specific objectives or set of results from a set of defined inputs.<br>Note: Generally, a [[#Process|Process]] is a logical subdivision of a larger set of activities used to provide or manage services, if the process is part of the [[#Service_Management_System|Service Management System]]. (FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Product">[[#Product|Product]]</div>
 
|
 
| A marketed entity (here: software component) that may provide a [[#Service|Service]] of its own, or may be re-used as an internal component in another product, or [[#Appliance|appliance]]. A Product may consist of one or more deployable [[#Package|packages]].
 
|-
 
! scope="row" | <div id="Quality_of_Service">[[#Quality_of_Service|Quality of Service]]</div>
 
| QoS
 
| The collective effect of service performance that determine the degree of satisfaction of a [[#User|User]] of the [[#Service|Service]]. Note that the quality of service is characterised by the combined aspects of service support performance, service operability performance, service integrity and other factors specific to each service. (''Source'':&nbsp;TMF)
 
|-
 
! scope="row" | <div id="Record">*[[#Record|Record]]</div>
 
|
 
| Documentation of an event or the results of performing a [[#Process|Process]] or [[#Activity|Activity]].
 
|-
 
! scope="row" | <div id="Release">*[[#Release|Release]]</div>
 
|
 
| Set of one or more changes to [[#Configuration_Item|Configuration Items]] that are grouped together and deployed as a logical unit.
 
|-
 
! scope="row" | <div id="Repository">[[#Repository|Repository]]</div>
 
|
 
| A storage location from which software packages may be retrieved and installed on a computer. (''Source:'' Wikipedia)
 
|-
 
! scope="row" | <div id="Resource">[[#Resource|Resource]]</div>
 
|
 
| A physical or virtual entity that is consumed from an [[#e-Infrastructure|e-Infrastructure]] through [[#IT_Service|IT Services]].
 
|-
 
! scope="row" | <div id="Resource_Centre">[[#Resource_Centre|Resource Centre]]</div>
 
| RC
 
| The smallest resource administration domain in an [[#e-Infrastructure|e-Infrastructure]]. It can be either localised or geographically distributed. It provides a minimum set of local or remote [[#IT_Service|IT Services]] compliant to well-defined [[#IT_Capability|IT Capabilities]] necessary to make resources accessible to [[#User|Users]]. Access is granted by exposing common interfaces to [[#User|Users]].
 
|-
 
! scope="row" | <div id="Resource_Centre_Administrator">[[#Resource_Centre_Administrator|Resource Centre Administrator]]</div>
 
|
 
| An individual who is responsible for installing, operating, maintaining and supporting one or more [[#Resource|Resources]] or [[#IT_Service|IT Services]] in a [[#Resource_Centre|Resource Centre]].
 
|-
 
! scope="row" | <div id="Resource_Centre_Operations_Manager">[[#Resource_Centre_Operations_Manager|Resource Centre Operations Manager]]</div>
 
|
 
| An individual who leads the [[#Resource_Centre|Resource Centre]] operations, and is the official technical contact person in the connected organisation. He/she is locally supported by a team of [[#Resource_Centre_Administrator|Resource Centre Administrators]].
 
|-
 
! scope="row" | <div id="Resource_Infrastructure">[[#Resource_Infrastructure|Resource Infrastructure]]</div>
 
| RI
 
| A federation of [[#Resource_Centre|Resource Centres]].
 
|-
 
! scope="row" | <div id="Resource_Infrastructure_Provider">[[#Resource_Infrastructure_Provider|Resource infrastructure Provider]]</div>
 
| RP
 
| The legal organisation responsible for any matter that concerns the respective [[#Resource_Infrastructure|Resource Infrastructure]]. It provides, manages and operates (directly or indirectly) all the operational services required to an agreed level of quality as required by the [[#Resource_Centre|Resource Centres]] and their user community. It holds the responsibility of integrating these operational services into [[#European_Grid_Infrastructure|EGI]] in order to enable uniform resource access and sharing for the benefit of their [[#User|Users]]. The Resource infrastructure Provider liaises locally with the [[#Resource_Centre_Operations_Manager|Resource Centre Operations Managers]], and represents the [[#Resource_Centre|Resource Centres]] at an international level. Examples of a Resource infrastructure Provider are the [[#European_Intergovernmental_Research_Organisation|European Intergovernmental Research Organisations(EIRO)]] and the [[#National_Grid_Initiative|National Grid Initiatives (NGIs)]].
 
|-
 
! scope="row" | <div id="Research_Collaboration">[[#Research_Collaboration|Research Collaboration]]</div>
 
|
 
| A group of scientists or researchers from different universities, institutes or other organisations working together for a common goal.
 
|-
 
! scope="row" | <div id="Request_for_Change">*[[#Request_for_Change|Request for Change]]</div>
 
|
 
| Documented proposal for a [[#Change|Change]] to be made to one or more [[#Configuration_Item|Configuration Items]].
 
|-
 
! scope="row" | <div id="Risk">*[[#Risk|Risk]]</div>
 
|
 
| Possible negative occurrence that would have a negative impact on the [[#Service_Provider|Service Provider's]] ability to deliver agreed [[#Service|Services]] to customers, or that would decrease the value generated through some service.<br>Note: Risk is made up of the probability of the threat entailed, the vulnerability to that threat of&nbsp;<span style="line-height: 1.5em; font-size: 13.2799997329712px;">some asset, and the impact the threat would have, if it occurred.</span>
 
|-
 
! scope="row" | <div id="Role">*[[#Role|Role]]</div>
 
|
 
| Set of responsibilities, connected behaviours or actions collected into a logical unit that can be assigned to an individual, team or group.<br>Note: An individual may have multiple roles.
 
|-
 
! scope="row" | <div id="Science_Gateway">[[#Science_Gateway|Science Gateway]]</div>
 
|
 
| A community-specific set of tools, applications, and data collections that are integrated together via a web portal or a desktop application, providing access to [[#Resource|Resources]] and [[#Service|Services]].
 
|-
 
! scope="row" | <div id="Service">*[[#Service|Service]]</div>
 
|
 
| A means of delivering [[#Value|Value]] to [[#User|Users]] by facilitating outcomes they want to achieve without the ownership of specific costs and [[#Risk|Risks]]. (''Source'': ITIL 2011, adapted)<br>A way to provide value to a [[#User|User]]/[[#Customer|Customer]] through bringing about results that they want to achieve.<br>Note 1: Services usually provide value when taken on their own – unlike the specific service components they are composed of.<br>Note 2: In the context of the FitSM standard series, when referring to services, usually IT services are meant.(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Service_Acceptance_Criteria">*[[#Service_Acceptance_Criteria|Service Acceptance Criteria]]</div>
 
| SAC
 
| Criteria that must be fulfilled by the time a new or changed service is deployed and made available to customers.<br> Note: SAC are defined when a new or changed service is designed, and they may be updated or refined during the development or transition process. They may cover functional and non-functional aspects of the specific service to be deployed. SAC are part of the service design and transition package.
 
|-
 
! scope="row" | <div id="Service_Catalogue">*[[#Service_catalogue|Service catalogue]]</div>
 
|
 
| A database or structured document with information about all live [[#Service|IT services]], including those available for deployment. The Service Catalogue is part of the [[#Service_Portfolio|Service Portfolio]] and contains information about two types of IT service: user-facing services that are visible to the business; and supporting services required by the [[#Service_Provider|Service Provider]] to deliver user-facing services. (''Source'': ITIL 2011)<br>[[#User|User]]/[[#Customer|Customer]] facing list of all live [[#Service|Services]] offered along with relevant information about these services.<br>Note: The service catalogue can be regarded as a filtered version of and customers' view on the service portfolio.(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Service_Component">*[[#Service_component|Service component]]</div>
 
|
 
| Logical part of a [[#Service|Service]] that provides a function enabling or enhancing a service.<br>Note 1: A service is usually composed of several service components.<br>Note 2: A service component is usually built from one or more configuration items (CIs).<br>Note 3: Although a service component underlies one or more services, it usually does not create value for a customer alone and is therefore not a service by itself.
 
|-
 
! scope="row" | <div id="Service_Design_and_Transition_Package">*[[#Service_Design_and_Transition_Package|Service Design and Transition Package]]</div>
 
| SDTP
 
| Entirety of plans for the design and transition of a specific new or changed service.<br>Note: A service design and transition package should be produced for every new or changed service. It may consist of a number of documented plans and other relevant information, available in different formats, including a list of requirements and [[#Service_Acceptance_Criteria|Service Acceptance Criteria]] (SAC), a project plan, communication and training plans, technical plans and specifications, resource plans,&nbsp;<span style="line-height: 1.5em; font-size: 13.2799997329712px;">development and deployment schedules/timetables etc.</span>
 
|-
 
! scope="row" | <div id="Service_Level_Agreement">*[[#Service_Level_Agreement|Service Level Agreement]]</div>
 
| SLA
 
| An agreement between a [[#Service_Provider|Service Provider]] and a [[#Customer|Customer]]. The SLA describes the [[#Service|IT Service]], documents [[#Service_Level_Target|Service Level Targets]] and specifies the responsibilities of the Service Provider and the customer. A single SLA may cover multiple [[#IT_Service|IT Services]] or multiple customers/clients.(EGI V1)<br>Documented agreement between a [[#Customer|Customer]] and [[#Service_Provider|Service Provider]] that specifies the [[#Service|Service]] to be provided and the [[#Service_Target|Service Targets]] that define how it will be provided.(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Service_Level_Management">[[#Service_Level_Management|Service Level Management]]</div>
 
| SLM
 
| The [[#Process|Process]] responsible for negotiating achievable [[#Service_Level_Agreement|Service Level Agreements]] and ensuring that these are met. It is responsible for ensuring that all IT service management processes, [[#Operational_Level_Agreement|Operational Level Agreements]] and [[#Underpinning_Contract|Underpinning Contracts]] are appropriate for the agreed [[#Service_Level_Target|Service Level Targets]]. Service Level Management monitors and reports on service levels, holds regular service reviews with customers/clients, and identifies required improvements. (''Source'': ITIL 2011)
 
|-
 
! scope="row" | <div id="Service_Level_Target">[[#Service_Level_Target|Service Level Target]]</div>
 
| SLT
 
| A commitment that is documented in a [[#Service_Level_Agreement|Service Level Agreement]]. Service Level Targets are based on service level requirements, and are needed to ensure that the [[#IT_Service|IT Service]] is able to meet business or organisation objectives. They should be smart and are usually based on key performance indicators. (''Source'': ITIL 2011)
 
|-
 
! scope="row" | <div id="Service_Management">*[[#Service_Management|Service Management]]</div>
 
|
 
| The entirety of activities performed by a service provider to plan, deliver, operate and control services offered to customers.<br>Note 1: The activities carried out in the service management context should be directed by policies and structured and organised by processes and supporting procedures.<br>Note 2: In the context of the FitSM standard series, when referring to service management, usually IT service management is meant.
 
&lt;/span&gt;
 
 
 
|-
 
! scope="row" | <div id="Service_Management_Plan">*[[#Service_Management_Plan|Service Management Plan]]</div>
 
|
 
| Overall plan for implementing and operating a [[#Service_Management_System|Service Management System]] (SMS).
 
|-
 
! scope="row" | <div id="Service_Management_System">*[[#Service_Management_System|Service Management System]]</div>
 
| SMS
 
| Overall management system that controls and supports service management of [[#Service|services]] within an organisation or federation.<br>Note: The SMS can be regarded as the entirety of interconnected policies, processes, procedures, roles, agreements, plans, related resources and other elements needed and used by a service provider to effectively manage the delivery of services to customers. See also: [[#Management_system|Management system]]
 
|-
 
! scope="row" | <div id="Service_Portfolio">*[[#Service_Portfolio|Service Portfolio]]</div>
 
|
 
| The complete set of [[#Service|Services]] that is managed by a [[#Service_Provider|Service Provider]]. The Service Portfolio is used to manage the entire lifecycle of all services, and includes three categories: service pipeline (proposed or in development), service catalogue (live or available for deployment), and retired services. (''Source'': ITIL 2011)<br>Internal list that details all the services offered by the service provider, including those in preparation, live and discontinued.<br>Note: The service portfolio includes meta-information about services such as their value proposition, target customer base, service descriptions, technical specifications, cost and price, risks to the provider, service level packages offered etc..(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Service_Provider">*[[#Service_Provider|Service Provider]]</div>
 
|
 
| An organisation supplying [[#Service|Services]] to one or more internal or external [[#User|Users]]. Service provider is often used as an abbreviation for IT Service Provider. (''Source:'' ITIL 2011 adapted)<br>Organisation or federation or part of an organisation or federation that manages and delivers a service or services to customers.(FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Service_Report">*[[#Service_Report|Service Report]]</div>
 
|
 
| Report that details the performance of a service versus the [[#Service_Target|Service Targets]] detailed in [[#Service_Level_Agreement|Service Level Agreements]] - often based on [[#Key_Performance_Indicators|Key Performance Indicators]] (KPIs).
 
|-
 
! scope="row" | <div id="Service_Request">*[[#Service_Request|Service Request]]</div>
 
|
 
| Request for information, advice, access to a service or a pre-approved change.<br>Note: Service requests are often handled by the same process and tools as incidents.
 
|-
 
! scope="row" | <div id="Service_Target">*[[#Service_Target|Service Target]]</div>
 
|
 
| Reference/target values for parameters that are used to measure the performance of a [[#Service|service]], and that are listed in a [[#Service_Level_Agreement&#124;Service Level Agreement related to this service.<br>Note: typical service targets might include [[#Availability|Availability]] or resolution time for [[#Incidents|Incidents]], though many hard and soft targets can be considered.
 
|-
 
! scope="row" | <div id="Site">[[#Site|Site]]</div>
 
|
 
| See [[#Resource_Centre|Resource Centre]].
 
|-
 
! scope="row" | <div id="Solution">*[[#Solution|Solution]]</div>
 
|
 
| A combination of [[#product|products]], [[#service|services]], and intellectual property focused on solving a problem (opportunity) that creates and/or drives [[#value|value]] (measurable) and can be significantly standardised. The solutions components can be from either the provider and one or more partners, and the solutions implementer can be the provider, the partner, the customer itself, or a combination of the three. (source: [http://solutionsinsights.com/what-is-the-definition-of-a-solution]).
 
|-
 
! scope="row" | <div id="Supplier">*[[#Supplier|Supplier]]</div>
 
|
 
| External organisation that provides a (supporting) [[#Service|Service]] or [[#Service_Component|Service Components]] to the [[#Service_Provider|Service Provider]], which they need to operate their [[#Process|Processes]] and provide services to their customers/users.
 
|-
 
! scope="row" | <div id="Standard">[[#Standard|Standard]]</div>
 
|
 
| A document, established by consensus and approved by a [[#Standard_Organisation_Body|Standards Organisation]], which provides, for common and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the achievement of the optimum degree of order in a given context. Compliance is not compulsory.
 
|-
 
! scope="row" | <div id="Standard_Organization_Body">[[#Standard_Organisation_Body|Standard Organisation Body]]</div>
 
| SDO
 
| A chartered organisation tasked with producing [[#Standard|Standards]] and specifications, according to specific and strictly defined requirements, procedures and rules. Standards developing organisations include recognised standardisation bodies such as&nbsp;: 1) international standardisation committees such as the International Organisation for Standardisation (ISO), the three European Standard Organisations: the European Committee for Standardisation (CEN), the European Committee for Electrotechnical Standardisation (CENELEC) or the European Telecommunications Standards Institute (ETSI), national standardisation organisations such as ANSI; 2) fora and consortia initiatives for standardisation such as the Open Grid Forum (OGF) or the Organisation for the Advancement of Structured Information Standards (OASIS).
 
|-
 
! scope="row" | <div id="Techology_Provider">[[#Techology_Provider|Techology Provider]]</div>
 
| TP
 
| Delivers the software, services and/or support required by any client or customer. Technology Providers can be community-specific as organisations or projects that develop or deliver software for specific user communities or customisation for specific requirements. They can also be generic as open-source software collaborations or commercial software providers that deliver technology spanning multiple user communities or domains for general infrastructure purposes.
 
|-
 
! scope="row" | <div id="Top_Management">*[[#Top_Management|Top Management]]</div>
 
|
 
| Senior management within the [[#Service_Provider|Service Provider]] organisation or federation who set [[#Policy|Policies]] and exercise overall control of the organisation or federation and their [[#Service_Management_System|Service Management System]] (SMS).
 
|-
 
! scope="row" | <div id="UMD_Capability">[[#UMD_Capability|UMD Capability]]</div>
 
|
 
| An [[#IT_Capability|IT Capability]] defined in the [https://documents.egi.eu/document/272 UMD Roadmap].
 
|-
 
! scope="row" | <div id="Underpinning_Agreement">*[[#Underpinning_Agreement|Underpinning Agreement]]</div>
 
| UA
 
| Documented agreement between a [[#Service_Provider|Service Provider]] and an [[#Supplier|external supplier]] that specifies the underpinning service(s) or service component(s) to be provided by the supplier, and the service targets that define how it will be provided.<br>Note 1: A UA can be seen as a service level agreement (SLA) with an external supplier where the service provider is in the customer role.<br>Note 2: A UA may be referred to as an underpinning contract (UC) in other ITSM frameworks. (FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Underpinning_Contract">[[#Underpinning_Contract|Underpinning Contract]]</div>
 
| UC
 
| A contract between an [[#Service_Provider|IT service provider]] and an [[#Supplier|external supplier]]. The [[#Supplier|external supplier]] provides goods or services that support delivery of an [[#Service|IT Service]] to a customer/client. The Underpinning Contract defines targets and responsibilities that are required to meet agreed service level targets in one or more [[#Service_Level_Agreement|Service Level Agreements]]. (''Source:'' ITIL 2011).<br>See: [[#Underpinning_Agreement|Underpinning Agreement]] (UA) (FitSM-0:2015)
 
|-
 
! scope="row" | <div id="Unified_Middleware_Distribution">[[#Unified_Middleware_Distribution|Unified Middleware Distribution]]</div>
 
| UMD
 
| The integrated set of software components contributed by [[#Technology_Provider|Technology Providers]] and packaged for deployment as production-quality services in [[#European_Grid_Infrastructure|EGI]].
 
|-
 
! scope="row" | <div id="User">[[#User|User]]</div>
 
|
 
| Individual that uses a [[#Service|Service]] on day-to-day basis. (Adapted from FitSM-0:2016)
 
|-
 
! scope="row" | <div id="Value">*[[#Value|Value]]</div>
 
|
 
| The benefit to a [[#Customer|Customer]] and their [[#User|Users]] delivered by a [[#Service|Service]].<br>Note: Value should be considered as a composition of the utility (fitness for purpose) and warranty (fitness for use, covering sufficient availability/continuity, capacity/performance and information security) connected to a service.
 
|-
 
! scope="row" | <div id="Value_Proposition">[[#Value_Proposition|Value Proposition]]</div>
 
|
 
| A promise of [[#Value|Value]] to be delivered and a belief from the customer/client of value that will be experienced. A value proposition can apply to an entire organisation, or parts thereof, or client accounts, or [[#Products|Products]] or [[#Service|Services]].
 
|-
 
! scope="row" | <div id="Virtual_Machine_Image">*[[#Virtual_Machine_Image|Virtual Machine Image]]</div>
 
| VMI
 
| A representation of the file system of a virtual machine, usually including a pre-configured operating system (OS) environment and a set of pre-installed applications.
 
|-
 
! scope="row" | <div id="Virtual_Organisation">[[#Virtual_Organisation|Virtual Organisation]]</div>
 
| VO
 
| A group of people (e.g. scientists, researchers) with common interests and requirements, who need to work collaboratively and/or share resources (e.g. data, software, expertise, CPU, storage space) regardless of geographical location. They join a VO in order to access resources to meet these needs, after agreeing to a set of rules and [[#Policy|Policies]] that govern their access and security rights (to users, resources and data).
 
|-
 
! scope="row" | <div id="Virtual_Organisation_Manager">[[#Virtual_Organisation_Manager|Virtual Organisation Manager]]</div>
 
|
 
| An individual responsible for the membership registry of a [[#Virtual_Organisation|VO]] including its accuracy and integrity.
 
|-
 
! scope="row" | <div id="Virtual_Research_Community">[[#Virtual_Research_Community|Virtual Research Community]]</div>
 
| VRC
 
| A group of large-scale research collaborations, or a number of separate [[#Virtual_Organisation|VOs]] grouped according to research domain or computational technique. The group shares information and experience in achieving their goals through the usage of an [[#e-Infrastructure|e-Infrastructure]] (e.g., best practices, applications, training material).
 
|-
 
! scope="row" | <div id="Virtual_Research_Environment">*[[#Virtual_Research_Environment|Virtual Research Environment]]</div>
 
| VRE
 
| Domain specific environments or combination of environments that provide the researcher with easy access to the services deployed to enable their data analysis activities, whether through command line interfaces or higher-level generic tools that simplify the data analysis process.
 
|-
 
! scope="row" | <div id="Virtual_Team">*[[#Virtual_Team|Virtual Team]]</div>
 
| VT
 
| A group of individuals spread across different organisations that are brought together for typically small scale projects, which cut across existing organisational structures.
 
|-
 
! scope="row" | <div id="Workflow">[[#Workflow|Workflow]]</div>
 
|
 
| A series of computational or data manipulation steps in order to use IT resources.
 
|-
 
! scope="row" | <div id="Workflow_System">[[#Workflow_System|Workflow System]]</div>
 
|
 
| A software system that enables scientific communities to compose and execute a series of computational or data manipulation steps, or a workflow, in a scientific application on IT resources.
 
|}
 
 
 
<br> '''''*New terms added or modified'''''<br>
 
 
 
=== Copyright  ===
 
 
 
This work by EGI.eu is licensed under Creative Commons Attribution 4.0 International License<br>This work is based on FitSM-0:2015, which was released under a Creative Commons 4.0 Attribution License (CC BY 4.0). It is part of the FitSM Standard family for lightweight IT service management, freely available at [http://www.fitsm.eu www.fitsm.eu].
 
 
 
[[Category:Glossary]]
 

Revision as of 10:39, 14 December 2020

Glossary of Terms List of Acronyms : A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Y - Z


The EGI Federation Glossary was migrated to a new dedicated space. Please, use http://go.egi.eu/glossary to refer to it.