| View | ID | Name | Status | ArchiMate model concept | Definition | Attributes |
|---|---|---|---|---|---|---|
| Legal View Concepts | ABB165 | Legislation Catalogue | archimate:BusinessObject | A Legislation Catalogue is a set of legal documents. | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB9 | Public Policy | archimate:BusinessObject | A Public Policy is the whole of actions under a policy domain taken by a public authority to bring about social change in the medium and long term. It is based on certain values and objectives and is implemented using a variety of methods. It applies on the territory within which the authority is authorised to act. [Source: EuroVoc, http://eurovoc.europa.eu/drupal/?q=request&concepturi=http%3A%2F%2Feurovoc.europa.eu%2F8466&termuri=http%3A%2F%2Feurovoc.europa.eu%2F209598&language=en&view=pt&ifacelang=en ]. | dct:type, dct:publisher, dct:modified, spatial_coverage, | |
| Legal View Concepts | ABB102 | Public Policy Cycle | archimate:BusinessProcess | A Public Policy Cycle is a cycle of stages in the creation and execution of a public policy. Source: Based on the concepts laid out in section 2.2 of http://www.europarl.europa.eu/RegData/etudes/etudes/join/2013/507457/IPOL-IMCO_ET(2013)507457_EN.pdf | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB111 | Public Policy Development Approach | archimate:BusinessObject | A Public Policy Development Approach is the delegation model used to enforce the policy (centralised vs. decentralised). [European Interoperability Strategy] | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB167 | Public Policy Development Enabler | archimate:BusinessObject | A Public Policy Development Enabler is an organisation or thing that make the development and implementation of the Public
Policy possible. [Oxford Dictionary] Source: http://www.oxforddictionaries.com/definition/english/enabler |
dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB112 | Public Policy Development Mandate | archimate:BusinessObject | A Public Policy Development Mandate is the capacity and authority to carry out tasks within a specific policy domain. [European Interoperability Strategy] | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB107 | Public Policy Evaluation | archimate:BusinessProcess | A Public Policy Evaluation is an assessment of how the public policy met its objectives (according to defined criteria). Source: Based on the concepts laid out in http://www.europarl.europa.eu/RegData/etudes/etudes/join/2013/507457/IPOL-IMCO_ET(2013)507457_EN.pdf | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB168 | Public Policy Formulation and Implementation Instrument | archimate:BusinessObject | A Public Policy Formulation and Implementation Instrument is an instrument that support the formulation and implementation of the policy. | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB106 | Public Policy Implementation | archimate:BusinessProcess | A Public Policy Implementation is the process of putting a public policy into effect. [Oxford Dictionary] | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB17 | Binding Instrument | archimate:BusinessObject | A Binding Instrument is a legal instrument that expresses something which is obligatory. Source: Based on the concepts laid out in http://europa.eu/legislation_summaries/glossary/community_legal_instruments_en.htm |
dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB103 | Definition of Public Policy Objectives | archimate:BusinessProcess | A Definition of Public Policy Objectives is a stage where public policy objectives are defined. Source: Based on the concepts laid out in http://www.europarl.europa.eu/RegData/etudes/etudes/join/2013/507457/IPOL-IMCO_ET(2013)507457_EN.pdf | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB116 | Financial Resource | archimate:BusinessObject | A Financial Resource is money in the form of cash, securities, creditors, loan facilities, etc. | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB104 | Formulation of Public Policy Scenarios | archimate:BusinessProcess | A Formulation of Public Policy Scenarios is a stage where a number of public policy options for addressing the problem and achieving the public policy objectives are developed. Source: Based on the concepts laid out in http://www.europarl.europa.eu/RegData/etudes/etudes/join/2013/507457/IPOL-IMCO_ET(2013)507457_EN.pdf | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB105 | Impact Assessment | archimate:BusinessProcess | An Impact assessment is a key tool to ensure that the public policy process is carried out on the basis of transparent, comprehensive and balanced evidence, an Impact assessment is an aid to political decision-making. Source: Based on the concepts laid out in http://ec.europa.eu/smart-regulation/impact/commission_guidelines/docs/iag_2009_en.pdf | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB117 | Implementing Guideline | archimate:BusinessObject | An Implementing Guideline is a set of instructions that provides insight into how to implement a policy. | dct:type, dct:publisher, dct:modified, | |
| Legal View Concepts | ABB164 | Legal Requirement or Constraint | archimate:BusinessObject | A Legal Requirement or Constraint is a legal text that mandates and/or guides the creation of an Interoperable European Solution. | dct:type, dct:publisher, dct:modified, requirement or constraint, | |
| Legal View Concepts | ABB113 | Non-binding Instrument | archimate:BusinessObject | A Non-binding Instrument is a set of recommendations and opinions, as well as rules governing how EU institutions and programmes
work, etc. Source: http://europa.eu/legislation_summaries/glossary/community_legal_instruments_en.htm |
dct:type, dct:modified, dct:title, dct:publisher, spatial_coverage, | |
| Legal View Concepts | ABB166 | Operational Enabler | archimate:BusinessObject | An Operational Enabler is an organisation, person, object or event that makes it possible to implement the policy. [Oxford
Dictionary] Source: http://www.oxforddictionaries.com/definition/english/enabler |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB169 | Business | archimate:BusinessActor | A Business is an organisational entity that provides and/or consumes Public Services. This includes non-governmental organisations and not-for-profit organisations. [European Interoperability Framework] | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB12 | Business Capability | archimate:BusinessFunction | A Business Capability is the expression or the articulation of the capacity, materials and expertise an organization needs in order to perform core functions. Enterprise architects use business capabilities to illustrate the over-arching needs of the business in order to better strategize IT solutions that meet those business needs. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB13 | Business Information | archimate:BusinessObject | Business Information is a piece of business data or a group of pieces of business data with a unique business semantics definition in a specific business context [source: ISO15000-5, UN/CEFACT CCTS]. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB170 | Business Information Exchange | archimate:BusinessInteraction | A Business Information Exchange is an interaction between two or more public administrations, businesses or citizens. Source: Based on UN/CEFACT Modelling Methodology (UMM) http://www.unece.org/cefact/umm/umm_index.html |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB16 | Business Rule | archimate:BusinessObject | A Business Rule is a statement that defines or constrains some aspect of the business. It is intended to assert business
structure, or to control or influence the behaviour of the business. Source: Business Rules Group; http://www.businessrulesgroup.org/defnbrg.shtml |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB8 | Citizen | archimate:BusinessActor | A Citizens is a consumers of Public Services | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB6 | Interoperability Collaboration Agreement | archimate:Contract | An Interoperability Collaboration Agreement is the means through which organisations (public administrations, or businesses) formalises the cooperation with one another. These agreements aim at the development of interoperability solutions, which meets the functional / technical requirements and needs of one another. | dct:type, dct:publisher, dct:modified, interoperability_type, | |
| Organisational View Concepts | ABB118 | Interoperability Provider Agreement | archimate:Contract | An Interoperability Provider Agreement is the means through which the service providers of public services formalise cooperation with one another. These agreements aim to have common way of providing the public service, which implies standardisation across service providers. | dct:type, dct:publisher, dct:modified, interoperability_type, | |
| Organisational View Concepts | ABB161 | Interoperability Service Agreement | archimate:Contract | An Interoperability Service Agreement is the means through which participants of ICT projects formalise cooperation with one another. These agreements aim at leaving each Member State with maximum internal autonomy, minimising the impact on their operational systems. | dct:type, dct:publisher, dct:modified, interoperability_type, | |
| Organisational View Concepts | ABB171 | Organisational Enabler | archimate:BusinessObject | An Organisational Enablers consists of elements which describe the functions, principles, rules, and policies in an organisation.
These enablers act as sources for the business rules of an organisation. |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB18 | Organisational Policy | archimate:BusinessObject | An Organisational Policy defines a set of principles, rules, and guidelines in an organisation. [source: European Interoperability
Framework http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf] |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB207 | Organisational Procedure | archimate:BusinessObject | An Organisational Procedure is a step-by-step description of the tasks required to support and carry out organizational policies. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB14 | Organisational Structure | archimate:BusinessObject | An Organisational Structure is the pattern of the distribution of work, flow of communications and instructions in the organisation
required to fulfil the organisational objectives. The way an organisation is set up: - matrix-organisation? - central/federated model? [Jayantee Saha - 2006 Management and Organizational Behaviour] |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB7 | Organisation | archimate:BusinessActor | An Organisation is an entity that provides and/or consumes Public Services. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB172 | Public Administration | archimate:BusinessActor | A Public Administration is an organisational entity that provides and/or consumes Public Services. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB1 | Public Service | archimate:BusinessService | A Public Service is an economic activity that public authorities identify as being of particular importance to citizens, businesses
and public administrations and that would not be supplied (or would be supplied under different conditions) if there were
no public intervention. Source: Based on DG Competition http://ec.europa.eu/competition/state_aid/overview/public_services_en.html A public service is the capacity to carry out a procedure and exists whether it is used or not. It is a set of deeds and acts performed by or on behalf of a public agency for the benefit of a citizen, a business or another public agency. https://joinup.ec.europa.eu/site/core_public_service/rdfs.html#PublicService |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB124 | Public Service Catalogue | archimate:BusinessObject | A Public Service Catalogue is a repository, with information on all public services. It represents the collection of the offered public services. [ITIL v3] | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB5 | Public Service Consumer | archimate:BusinessRole | A Public Service Consumer is a Public Administration, Business or Citizen consuming public services. [European Interoperability
Framework] Source: Based on EIF 2.0 http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB173 | Public Service Delivery Agent | archimate:BusinessRole | A Public Service Delivery Agent delivers a public service on behalf of a Service Providers. An example of this would be pharmacies that deliver a service 'on the behalf of' the Ministry of Health. In this case the pharmacies would be captured as a Service Delivery Agent whereas the Service Provider would be the Ministry of Health. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB174 | Public Service Provider | archimate:BusinessRole | A Public Service Provider is a Public Administration or Business providing Public Services financed through public resource.
[DG Competition] Source: http://ec.europa.eu/competition/state_aid/overview/public_services_en.html |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB15 | Service Delivery Model | archimate:BusinessInterface | A Service Delivery Model defines how the organisation arranges the delivery of its services to service consumers. This includes: - How will the service be delivered (e.g. multi-channel, SPOCs, only once)? - How will the interaction between the service provider and service consumer take place? - How will certain situations be handled (e.g. incident management)? - How will the support & maintenance look like? [ITIL v3] Source: http://www.itil-officialsite.com/ |
dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB119 | Interoperability Agreement | archimate:Contract | An Interoperability Agreement is the means through which organisations (public administrations, or businesses) formalises
the cooperation with one another. These agreements aim at the development of interoperability solutions, which meets the functional
/ technical requirements and needs of one another. [European Interoperability Framework] The agreement should include purposes and goals, terms and conditions, governance, and the description of the channel(s). The EIRA differentiates the following Interoperability Agreements: - Interoperability Service Agreement (between Public Service Consumers and Public Service Providers; - Interoperability Collaboration Agreement (between Organisations); or - Interoperability Provider Agreement (between Public Service Providers). |
dct:type, dct:publisher, dct:modified, interoperability_type, | |
| Organisational View Concepts | ABB214 | Interoperability Governance | archimate:BusinessObject | Interoperability Governance is an organisational procedures for the governance of interoperability usually under the mandate/approach of a public policy. Examples are the comitology procedures for ISA at European level. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB205 | Interoperability Organisational Authority | archimate:BusinessObject | An Interoperability Organisational Authority is an organisation holding the responsibility for interoperability governance under the mandate/approach of a Public Policy. Examples are ISA at European level and CIO at national level. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB206 | Interoperability Framework | archimate:BusinessObject | An Interoperability Framework is a set of interoperability principles, rules, and guidelines in an organisation. Examples are EIF at European level and National schemas of IOP at national level. | dct:type, dct:publisher, dct:modified, | |
| Organisational View Concepts | ABB208 | Interoperability Strategy | archimate:BusinessObject | An Interoperability Strategy is a long term plan addressing interoperability strategic objectives. Example is the European
Interoperability Strategy at European level. |
dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB30 | Data Policy | archimate:Contract | A data policy is a short statement of management intent and fundamental rules governing the creation, acquisition, integrity,
security, quality, and use of data and information [source: DAMA DM_BOK, http://www.dama.org.]. A data policy can be among others the following: - information security policy; - privacy policy; - licensing and charging policy ; - data quality policy; and - metadata management policy. |
dct:type, dct:publisher, dct:modified, | |
| Interoperability View Concepts | ABB162 | Interoperability Specification | archimate:BusinessObject | An Interoperability Specification is a document containing agreed normative statements for solution building blocks used in an information exchange context. It can refer to existing standards or specifications. | dct:type, dct:publisher, dct:modified, | |
| Interoperability View Concepts | ABB175 | Legal Interoperability Specification | archimate:BusinessObject | A Legal Interoperability Specification defines a necessary attribute that shall be fully met to support legal interoperability in the Public Policy Cycle. | dct:type, dct:publisher, dct:modified, | |
| Interoperability View Concepts | ABB176 | Organisational Interoperability Specification | archimate:BusinessObject | An Organisational Interoperability Specification defines a necessary attribute that shall be fully met to support organisational interoperability. | dct:type, dct:publisher, dct:modified, | |
| Interoperability View Concepts | ABB177 | Semantic Interoperability Specification | archimate:BusinessObject | A Semantic Interoperability Specification defines a necessary attribute that shall be fully met to support semantic interoperability. |
dct:type, dct:publisher, dct:modified, | |
| Interoperability View Concepts | ABB163 | Specification | archimate:BusinessObject | A Specification is a document that states requirements. A specification can be related to activities (e.g. procedure document,
process specification and test specification), or products (e.g. product specification, performance specification and drawing).
[ISO 9000:2005] Source : https://www.iso.org/obp/ui/#iso:std:iso:9000:ed-3:v1:en:term:3.7.3 |
dct:type, dct:publisher, dct:modified, | |
| Interoperability View Concepts | ABB178 | Technical Interoperability Specification | archimate:BusinessObject | A Technical Interoperability Specifications defines a necessary attribute that shall be fully met to support technical interoperability. | dct:type, dct:publisher, dct:modified, | |
| Deprecated | ABB10 | Business Process | deprecated | archimate:BusinessProcess | A business process is a sequence of linked activities that creates value by turning inputs into a more valuable output | ABB_Status, |
| Deprecated | ABB142 | Business Process Model | deprecated | archimate:BusinessObject | A model that defines the business process, by the definition of strict steps of the business processes, precise rules, and the description of the processed data. | ABB_Status, |
| Deprecated | ABB196 | Data Quality Policy | deprecated | archimate:Contract | A Security Policy is a set of statements of management intent and fundamental rules governing the definition, monitoring, and improvement of data quality. [DAMA] Source: http://www.dama.org/ | dct:type, dct:publisher, dct:modified, ABB_Status, |
| Deprecated | ABB160 | Information Security Policy | deprecated | archimate:Contract | A Security Policy is a set of statements of management intent and fundamental rules governing the creation, acquisition, integrity,
security, quality and use of data and information. [DAMA] Source: http://www.dama.org |
dct:type, dct:publisher, dct:modified, ABB_Status, |
| Deprecated | ABB31 | Licensing and Charging Policy | deprecated | archimate:Contract | A Licensing and Charging Policy is a statement of principles and guidelines for licensing and charging data. This may lead to an "open" data policy or a "closed" data policy. [DAMA] Source: http://www.dama.org/ |
dct:type, dct:publisher, dct:modified, ABB_Status, |
| Deprecated | ABB33 | Metadata Management Policy | deprecated | archimate:Contract | Policy governing the creation, control, integration, access and use of metadata. [DAMA] Source: http://www.dama.org/ | dct:type, dct:publisher, dct:modified, ABB_Status, |
| Deprecated | ABB32 | Privacy Policy | deprecated | archimate:Contract | Statements of management intent and fundamental rules governing the creation, acquisition, integrity, security, quality and use of data and information. [DAMA] Source: http://www.dama.org | dct:type, dct:publisher, dct:modified, ABB_Status, |
| Deprecated | ABB11 | Business Transaction | deprecated | archimate:BusinessFunction | Atomic unit of interaction between two or more public administrations, businesses or citizens. | ABB_Status, |
| Semantic View Concepts | ABB179 | Character Encoding Scheme | archimate:DataObject | A Character Encoding Scheme reflects the way a chosen character set is mapped to bytes for manipulation in a computer [W3C]. An example is the UTF-8 standard. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB22 | Data | archimate:DataObject | Data is facts represented as text, numbers, graphics, images, sound, or video. Data is the raw material used to represent information, or from which information can be derived [source: DAMA DM_BOK, http://www.dama.org]. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB20 | Data Entity | archimate:DataObject | A classification of objects found in the real world described by the Noun part of speech – persons, places, things, concepts, and events – of interest to the enterprise [source: DAMA DM_BOK, http://www.dama.org]. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB26 | Data Model | archimate:DataObject | A Data Model includes formal data names, comprehensive data definitions, proper data structures and precise data integrity rules [source: DAMA DM_BOK, http://www.dama.org]. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB29 | Identifier Scheme | archimate:DataObject | An Identifier Schema defines the values of an identifier [source: CEN BII http://spec.cenbii.eu/]. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB180 | Data-level Mapping | archimate:DataObject | A Data-level Mapping is a mapping between specific data elements (or data values) [source: ISO/DIS 25964-2]. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB181 | Master Data | archimate:DataObject | Master Data is the authoritative, most accurate data that is available about key business entities, used to establish the
context for business transactions and transactional data [source: DAMA DM_BOK, http://www.dama.org]. |
dct:type, dct:publisher, dct:modified, skos:altLabel, | |
| Semantic View Concepts | ABB27 | Reference Data | archimate:DataObject | Reference Data is any data used to organise or categorise other data, or for relating data to information both within and
beyond the boundaries of the enterprise. Usually consists of codes and descriptions or definitions [source: DAMA DM_BOK, http://www.dama.org]. Reference data consists typically of a small, discrete set of values that are not updated as part of business transactions but are usually used to impose consistent classification. Reference data normally has a low update frequency. Reference data is relevant across more than one business systems belonging to different organisations and sectors [source: J. Jordan & C. Ellen (2009). Business need, data and business intelligence]. |
dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB183 | Data Standard | archimate:DataObject | A data standard is a structural metadata specification that describes or defines other data [ISO111179]. Structural metadata indicates how compound objects are put together [NISO]. It can consist of among others data models, reference data, and identifier schemas. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB184 | Syntax Encoding Scheme | archimate:DataObject | A Syntax Encoding Scheme indicates that the value is a string formatted in accordance with a formal notation [DCMI Glossary], such as ‘2000-01-01’ as the standard expression of a date. Another example is CSV [Source: http://wiki.dublincore.org/index.php/Glossary/Encoding_Scheme]. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB185 | Transactional Data | archimate:DataObject | Transactional Data is data that covers the business information related to business transactions and information exchanges
[source: based on DAMA DM_BOK, http://www.dama.org]. |
dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB23 | Data Set | archimate:DataObject | A Data Set is a collection of data, published or curated by a single agent, and available for access or download in one or
more formats [source: W3C, http://www.w3.org/TR/vocab-dcat/#class-dataset]. |
dct:type, nature, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB24 | Data Set Catalogue | archimate:DataObject | A Data Set Catalogue is a curated collection of datasets [source: W3C, http://www.w3.org/TR/vocab-dcat/#class-catalog]. |
dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB182 | Representation | archimate:DataObject | A Representation is a physical embodiment or manifestation of data [based on the Functional Requirements for Bibliographic Records]. It is the perceptible form of information carried by a business object [based on ArchiMate]. | dct:type, dct:publisher, dct:modified, representation_technique, | |
| Semantic View Concepts | ABB211 | Data Standard Catalogue | archimate:DataObject | A Data Standard Catalogue is a catalogue of Data Standards. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB212 | Schema-level Mapping | archimate:DataObject | A Schema-level Mapping is a mapping between related classes and properties [source: ISO/DIS 25964-2]. | ||
| Semantic View Concepts | ABB194 | Core Data Model | archimate:DataObject | A context-neutral data model that captures the fundamental characteristics of an entity [Source: Core Vocabularies Handbook, https://joinup.ec.europa.eu/site/core_vocabularies/Core_Vocabularies_user_handbook/ ]. | dct:type, dct:publisher, dct:modified, | |
| Semantic View Concepts | ABB195 | Descriptive Metadata | archimate:DataObject | Descriptive metadata describes a resource for purposes such as discovery and identification. It can include elements such
as title, abstract, author, and keywords. Source: http://www.niso.org/publications/press/UnderstandingMetadata.pdf |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB70 | Access Management Component | archimate:ApplicationComponent | An Access Management Component encapsulates the functionalities to authorize users exposed through the Access Management Service. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB57 | Access Management Service | archimate:ApplicationService | An Access Management Service provides the mechanisms to ensure that only authorized users can access and perform actions on IT resources. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB71 | Audit and Logging Component | archimate:ApplicationComponent | An Audit and Logging Component encapsulates the functionalities for auditing and logging of events. |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB58 | Audit Service | archimate:ApplicationService | An Audit Service provides support for the principle of accountability, that is holding users of a system accountable for their
actions within the system, and detection of policy violations. The audit policy defines the elements of an information system
which need to be traced, for example to assure tracability of actions: what, how, when, where and with what. Inspired by: http://www.opengroup.org/security/das/xdas_int.htm |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB46 | Business Analytics Service | archimate:ApplicationService | A Business Analytics Service enables the storage and manipulation of dimensional data models for the analysis of business trends and projections. [DAMA] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB66 | Business Intelligence Component | archimate:ApplicationComponent | A Business Intelligence Component encapsulates the functionalities exposed through the Business Analytics Service. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB186 | Business Process Management Component | archimate:ApplicationComponent | A Business Process Management Component encapsulates the functionalities for the orchestration/choreography of business processes. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB47 | Business Reporting Service | archimate:ApplicationService | A Business Reporting Service provides detailed reports using unified views of enterprise data. [DAMA] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB44 | Choreography Service | archimate:ApplicationService | The Choreography Service is the interplay among groups of services which, in turn, make up a larger, composite service, or which interact across organisational boundaries in order to obtain and process information. [W3C] Source: http://www.w3.org/TR/ws-cdl-10/ | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB127 | Configuration Management | archimate:BusinessObject | A Configuration management is the means of maintaining Interoperable European Solutions to safeguard the performance of these solution. This includes change management, versioning, etc. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB61 | Data Transformation Component | archimate:ApplicationComponent | A Data Transformation Component encapsulates the data transformation functionalities exposed through the Data Transformation Service. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB40 | Data Transformation Service | archimate:ApplicationService | A Data Transformation Service converts data. This includes the conversion from one data format to another. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB63 | Data Validation Component | archimate:ApplicationComponent | A Data Validation Component encapsulates the data validation functionalities exposed through the Data Validation Service. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB42 | Data Validation Service | archimate:ApplicationService | A Data Validation Service is used to validate data against predefined semantic and syntactic constraints. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB60 | Interoperable European Solution | archimate:ApplicationComponent | An Interoperable European Solution (IES) is a solution, developed by Public Administrations that facilitate the delivery of
electronic Public Services and cross-border exchange of information between Public Administrations (or Citizens) in support
to the implementation and advancement of EU, national or local Public Policies. Source: This IES definition was derived from the Trans-European Systems definition. |
dct:type, dct:publisher, dct:modified, policy area extension, reusability, reusability_bool, actual policy coverage, | |
| Technical View - Application Concepts | ABB59 | Logging Service | deprecated | archimate:ApplicationService | An Logging Service traces all events and user actions impacting a data entity throughout its lifecycle (from its creation to its disposal). It can be used to reproduce a certain state of a data entity at a certain moment in time. | dct:type, ABB_Status, dct:publisher, dct:modified, |
| Technical View - Application Concepts | ABB126 | Operational Procedure | archimate:BusinessObject | An Operational Procedure defines the process of operating a solution, how the procedures are implemented and the rules for operating it. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB45 | Orchestration Service | archimate:ApplicationService | Orchestration identifies a sets of transactions involving use of other services and functionalities, according to business rules embodied in one or more documented business processes, with the ultimate goal of performing or providing some other value-added function or service. The Orchestration Service executes all the required transactions and routes the inputs and outputs of processes according to rules described in a standard language (i.e. BPEL). [European Interoperability Framework] Source: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB37 | Human Interface | archimate:ApplicationInterface | A Human Interface is a specific interface between the human users of an IT system and the programs providing screen or printed results. It is frequently regarded as a dedicated set of programs, separate from those which extract and process data. [DG TAXUD] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB38 | Machine to Machine Interface | archimate:ApplicationInterface | A Machine to Machine Interface is a description of a boundary between a system and other systems, usually including the mechanisms by which information is transferred. [DG TAXUD] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB159 | Service Discovery Service | archimate:ApplicationService | A Service Discovery Service allows the automatic discovery of other services. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB129 | Test Component | archimate:ApplicationComponent | A Test Component encapsulates the functionalities for the testing processes. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB131 | Test Report | archimate:BusinessObject | A Test Report is the means of describing the results coming out of the Test Service, within this document the evaluation is made of the solution (based on the Test Scenario). | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB130 | Test Scenario | archimate:BusinessObject | A Test Scenario defines the different test cases which needs to be performed by the Test Service. Each scenario (actual) outcome is validated against the pre-defined expected outcome. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB128 | Test Service | archimate:ApplicationService | A Test Service enables the execution of the test scenarios by follow a number of sequential steps to validate the performance of a service, the accuracy, etc. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB187 | Application Service | archimate:ApplicationService | An Application Service is an externally visible unit of functionality, provided by one or more application components. It is exposed through well-defined interfaces and is meaningful to the environment. A Application Service exposes the functionality of components to their environment. This functionality is accessed through one or more application interfaces. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Application Concepts | ABB125 | Technical Specification | archimate:BusinessObject | A Technical Specification is a document describing the functional/technical specifications of a solution. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB137 | Administration and Monitoring Service | archimate:ApplicationService | An Administration and Monitoring Service enables the administration and monitoring of services offered by the different components. [SOA Backplane Reference Model of Gartner] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB139 | Administration Component | archimate:ApplicationComponent | An Administration Component encapsulates the functionalities for the administration, monitoring and lifecycle management of services. [SOA Backplane Reference Model of Gartner] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB54 | Audiovisual Service | archimate:ApplicationService | An Audiovisual Service enables the broadcast of audio and video content over the internet or satellite. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB72 | Collaboration Component | archimate:ApplicationComponent | A Collaboration Component encapsulates the functionalities for transmission of text and broadcasting of audio and video content. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB75 | Content Management Component | archimate:ApplicationComponent | A Content Management Component encapsulates the functionalities for the organisation and categorization of information resources. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB51 | Content Management Service | archimate:ApplicationService | A Content Management Service enables the organisation and categorisation of information resources so that they can be stored,
published and reused in multiple contexts. [DAMA] Source: http://www.dama.org/ |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB64 | Data Exchange Component | archimate:ApplicationComponent | A Data Exchange Component encapsulates the functionalities for secure data exchange. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB43 | Data Exchange Service | archimate:ApplicationService | A Data Exchange Service enables the secure exchange of messages, records, forms and other kinds of data between different
ICT systems. This includes data routing, except endpoint discovery. [European Interoperability Framework] Source: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB188 | Digital Service Infrastructure | archimate:ApplicationComponent | A Digital Service Infrastructure is a collection of cross-sectorial infrastructure services and components. They are decoupled
from the business which a specific interoperable solution implements. They can be re-used with no or very minor changes by
other interoperable solutions or in different policy contexts. [CEF] Source: http://ec.europa.eu/digital-agenda/en/connecting-europe-facility |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB136 | Document Management Service | archimate:ApplicationService | A Document Management Service enables the organisation and categorization of electronic documents in order to store, publish
and reuse these documents in multiple contexts. For a differentiation between ERMS and EDMS visit section 10.3 of Moreq:
http://ec.europa.eu/archival-policy/moreq/doc/moreq_en. The definition of a Record Management Service includes a differentiation towards record management and e-archiving. |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB156 | e-Archiving Service | archimate:ApplicationService | An e-Archiving Service enables the permanent or long-term storage of selected (by an authority) electronic documents or information
for preservation purposes. The EIRA differentiates between document management, record management and e-archiving as follows: - Document management is primarily about day-to-day use of electronic documents (create/update/delete/versioning) within the operational environment. - Record management is primarily about ensuring that information (e.g. in form of an electronic document or database record) is available for business and legal purposes (e.g. to prove and track the handling of contracts). If an electronic document or information is becoming a record (an authority declares it as a record) that electronic document or information needs to be handled by the record management service (based on specific business or legal reasons (e.g. contract negotiation)). - e-Archiving is primarily about storing records which have been selected (by an authority) for permanent or long-term preservation due to their enduring research value and as a memory aid. An electronic document or information which a) is managed by the document management service or the record management service and b) is no longer needed for business or legal purposes or day-to-day activities, and c) still has value for research purposes or as a memory aid, the electronic document should be managed by the e-archiving service". |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB157 | e-Archiving Component | archimate:ApplicationComponent | An e-Archiving Component encapsulates the functionalities for electronic archiving of documents. | dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB68 | e-Payment Component | archimate:ApplicationComponent | An e-Payment Component encapsulates the functionalities for execution or electronic payments. | dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB48 | e-Payment Service | archimate:ApplicationService | An e-Payment Service enables the execution of payment transactions where the consent of the payer to execute a payment transaction
is given by means of any telecommunication, digital or IT device. [Directive 2007/64/EC] Source: http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32007L0064:EN:NOT |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB69 | Trust Service Provisioning Component | archimate:ApplicationComponent | A Trust Service Provisioning Component is a component that provides trust services. According to the eIDAS Regulation, a ‘trust service’ means an electronic service normally provided for remuneration which consists of: (a) the creation, verification, and validation of electronic signatures, electronic seals or electronic time stamps, electronic registered delivery services and certificates related to those services, or (b) te creation, verification and validation of certificates for website authentication; or (c) the preservation of electronic signatures, seals or certificates related to those services. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB144 | e-Signature Verification and Validation Service | archimate:ApplicationService | An e-Signature Verification and Validation Service is used for the verification of documents that are signed electronically. According to the eIDAS Regulation, an ‘electronic signature’ means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. According to the eIDAS Regulation, ‘validation’ means the process of verifying and confirming that an electronic signature or a seal is valid. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB55 | e-Signature Creation Service | archimate:ApplicationService | An e-Signature Creation Service is used by a natural person to sign data in electronic form. According to the eIDAS Regulation, an ‘electronic signature’ means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB77 | Forms Management Component | archimate:ApplicationComponent | A Forms Management Component encapsulates the functionalities for the management of forms. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB49 | Forms Management Service | archimate:ApplicationService | A Forms Management Service enables the dynamic creation, distribution and analysis of forms and online surveys. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB158 | Identity Mangement Component | archimate:ApplicationComponent | An Identity Management Component encapsulates the functionalities for the authentication of users. The eIDAS Regulation provides the following definitions: ‘electronic identification’ means the process of using person identification data in electronic form uniquely representing either a natural or legal person, or a natural person representing a legal person; ‘authentication’ means an electronic process that enables the electronic identification of a natural or legal person, or the origin and integrity of data in electronic form to be confirmed; Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB204 | Identity Management Service | archimate:ApplicationService | An Identity Management Service provides functionalities for the authentication of users. The eIDAS Regulation provides the following definitions: ‘electronic identification’ means the process of using person identification data in electronic form uniquely representing either a natural or legal person, or a natural person representing a legal person; ‘authentication’ means an electronic process that enables the electronic identification of a natural or legal person, or the origin and integrity of data in electronic form to be confirmed; Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB138 | Lifecycle Management Service | archimate:ApplicationService | A Lifecycle Management Service supports the governance of services throughout their lifecycle. [SOA Backplane Reference Model of Gartner] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB62 | Machine Translation Component | archimate:ApplicationComponent | A Machine Translation Component encapsulates the machine translation functionalities exposed through the Machine Translation Service. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB41 | Machine Translation Service | archimate:ApplicationService | A Machine Translation Service enables the automatic translation of data in form of plain text from one EU language to another EU language (or to a set of other EU languages). | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB53 | Messaging Service | archimate:ApplicationService | A Messaging Service enables real-time transmission of text over the internet. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB74 | Metadata Management Component | archimate:ApplicationComponent | A Metadata Management Component encapsulates the functionalities for the management of metadata. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB52 | Metadata Management Service | archimate:ApplicationService | A Metadata Management Service enables the creation, storage, categorisation and retrieval of metadata. [DAMA] Source: http://www.dama.org/ |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB141 | Partner Management Component | archimate:ApplicationComponent | A Partner Management Component encapsulates the functionalities for managing the consumers of services. [SOA Backplane Reference Model of Gartner] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB140 | Partner Management Service | archimate:ApplicationService | A Partner Management Service enables the management of the consumers of the services offered by the different components (i.e. the Partners) to ensure scalability. It enables the management of IES' interoperability agreements. [SOA Backplane Reference Model of Gartner] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB76 | Record Management Component | archimate:ApplicationComponent | A Record Management Component encapsulates the functionalities for the classification, storage, archiving, and destruction of electronic records. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB50 | Record Management Service | archimate:ApplicationService | A Records Management Service enables the classification, storage, access, and disposal of the records of an organization from
the time they are captured (e.g. creation of an internal document or reception of an external document) up to their eventual
disposal. Electronic records are document(s) in digital format produced or received by a person or organisation in the course
of business, and retained by that person or organisation. The definition of a Record Management Service includes a differentiation towards record management and e-archiving. Source: Based on the archival policy of the European Commission http://ec.europa.eu/archival-policy/moreq/doc/moreq_en.pdf |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB189 | Service Registration Service | archimate:ApplicationService | A Service Registration Service provides a mechanism to register the system service within a catalogue to be discovered by other services. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB133 | Service Registry Component | archimate:ApplicationComponent | A Service Registry Component encapsulates the service registration functionality. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB146 | Trust Registry Component | archimate:ApplicationComponent | A Trust Registry Component enables the discovery of essential information about e.g. supervised/accredited trust service
providers issuing certificates for electronic signatures, for electronic seals or for website authentication; supervised/accredited
trust services for eSignature, eSeal or TimeStamp creation and validation; supervised/accredited trust services for eSignature
or eSeal preservation; supervised/accredited trust services for electronic registered delivery. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB145 | Trust Registry Service | archimate:ApplicationService | A Trust Registry Service enables the discovery of essential information about e.g. supervised/accredited trust service providers
issuing certificates for electronic signatures, for electronic seals or for website authentication; supervised/accredited
trust services for eSignature, eSeal or TimeStamp creation and validation; supervised/accredited trust services for eSignature
or eSeal preservation; supervised/accredited trust services for electronic registered delivery. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB210 | Configuration and Cartography Service | archimate:ApplicationService | A Configuration and Cartography Service allows the documentation of solution, including its configuration and architecture. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB213 | Configuration and Cartography Service Component | archimate:ApplicationComponent | A Configuration and Cartography Service Component encapsulates the functionalities for documenting the configuration and architecture of solutions. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB215 | Data Publication Service | archimate:ApplicationService | A Data Publication Service makes data available to other services or users. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB209 | Data Publication Component | archimate:ApplicationComponent | A Data Publication Component encapsulates the functionalities for data publication services. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB198 | e-Seal Creation Service | archimate:ApplicationService | An e-Seal Creation Service is used to sign data in electronic form on behalf of a legal person. According to the eIDAS Regulation, an ‘electronic seal’ means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latter’s origin and integrity. The ‘creator of a seal’ is a legal person who creates an electronic seal. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB200 | e-Seal Preservation Service | archimate:ApplicationService | An e-Seal Preservation Service is used for extending the trustworthiness of the qualified electronic signature beyond the
technological validity period. According to the eIDAS Regulation, an ‘electronic seal’ means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latter’s origin and integrity. The ‘creator of a seal’ is a legal person who creates an electronic seal. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB199 | e-Seal Verification and Validation Service | archimate:ApplicationService | An e-Seal Verification and Validation Service is used for the verification of documents that are signed electronically. According to the eIDAS Regulation, an ‘electronic seal’ means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latter’s origin and integrity. The ‘creator of a seal’ is a legal person who creates an electronic seal. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB197 | e-Signature Preservation Service | archimate:ApplicationService | An e-Signature Preservation Service is used for extending the trustworthiness of the qualified electronic signature beyond
the technological validity period. According to the eIDAS Regulation, an ‘electronic signature’ means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB201 | e-Timestamp Creation Service | archimate:ApplicationService | An e-Timestamp Creation Service is used for the verification of timestamps used for establishing evidence that a give piece
of data existed at a given point in time. According to the eIDAS Regulation, ‘electronic time stamp’ means data in electronic form which binds other data in electronic form to a particular time establishing evidence that the latter data existed at that time. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB202 | e-Timestamp Verification and Validation Service | archimate:ApplicationService | An e-Timestamp Verification and Validation Service is used for the verification of timestamps used for establishing evidence
that a give piece of data existed at a given point in time. According to the eIDAS Regulation, ‘electronic time stamp’ means data in electronic form which binds other data in electronic form to a particular time establishing evidence that the latter data existed at that time. Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:title, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB203 | Registered Electronic Delivery Service | archimate:ApplicationService | According to the eIDAS Regulation, an Electronic Registered Delivery Service is a service that makes it possible to transmit
data between third parties by electronic means and provides evidence relating to the handling of the transmitted data, including
proof of sending and receiving the data, and that protects transmitted data against the risk of loss, theft, damage or any
unauthorised alterations; Source: REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. |
dct:type, dct:publisher, dct:modified, | |
| Deprecated | ABB135 | Data Routing Component | deprecated | archimate:ApplicationComponent | A Data Routing Component encapsulates the data routing functionalities exposed through the Data Routing Service. | dct:type, dct:publisher, dct:modified, ABB_Status, |
| Deprecated | ABB134 | Data Routing Service | deprecated | archimate:ApplicationService | A Data Routing Service routes data messages based on the content of the message (header). The messages are forwarded from a starting endpoint to a client endpoint. Standardised protocols can be used, e.g. REST, SOAP, etc. to support the routing. | dct:type, dct:publisher, dct:modified, ABB_Status, |
| Technical View - Infrastructure Concepts | ABB190 | Hosting and Networking Infrastructure Service | archimate:InfrastructureService | A Hosting and Networking Infrastructure Service is a collection of services for hosting Interoperable European Solutions and provides the necessary networks for operating these solutions. | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB191 | Hosting Facility | archimate:Node | A Hosting Facility is usually embodied in a building and the equipment supporting the hosting of Interoperable European Solutions
and their components. [DIGIT C Infrastructure Services Provision] |
dct:type, dct:publisher, dct:modified, secure access, processing, storage, | |
| Technical View - Infrastructure Concepts | ABB151 | Hosting Service | archimate:InfrastructureService | A Hosting Service is a service provided by a hosting provider. [DIGIT C Infrastructure Services Provision] |
dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB92 | Network | archimate:Network | A Network realises the physical communication layer among nodes participating in an Interoperable European Solution. | dct:type, dct:publisher, dct:modified, reusability, reusability_bool, | |
| Technical View - Infrastructure Concepts | ABB150 | Networking Service | archimate:InfrastructureService | A Networking Service is a service provided by a network provider. [DIGIT C Infrastructure Services Provision] | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB192 | Private Hosting Facility | archimate:Node | A Private Hosting Facility is a Hosting Facility which is owned by or dedicated to one organization (e.g. data centre or private cloud). | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB93 | Private Network | archimate:Network | A Private Network is a network that is used for the only purpose of realising the physical communication among Interoperable European Solution (e.g. sTESTA), and cannot be accessed by the public. | dct:type, dct:publisher, dct:modified, reusability, reusability_bool, | |
| Technical View - Infrastructure Concepts | ABB193 | Public Hosting Facility | archimate:Node | A Public Hosting Facility is a Hosting Facility which is owned by a third party and shared between organizations (e.g. cloud services). | dct:type, dct:publisher, dct:modified, | |
| Technical View - Infrastructure Concepts | ABB94 | Public Network | archimate:Network | A Public Network is a network that can be accessed by the public (public administrations, businesses and citizens) without specific authorisations. Interoperable European Solutions can rely on Public Networks (e.g. the Internet) to realise the physical communication between nodes. | dct:type, publisher, dct:modified, |